How Journeys and Cortex build on the same design

Return to Meet AI eduarda

While my agents worked on Cortex, they corrected a shared avatar component whose initials overflowed, published the fix and carried it into both Cortex and Journeys, checking each. I supplied the direction; agents did the implementation, review and release.

Record prepared October 21, 2026 from my account and the retained delivery records for the correction below.

I built Cortex’s UI/UX with my agents, using what we had standardized for Journeys. Mike built Cortex’s API, backend and MCP, which lets agents work with Cortex through their tools.

My work is the experience people use to find and edit knowledge, follow Dependencies and work through Issues. The shared design gives those experiences their controls, navigation and layouts. Mike’s maintained service knowledge helps my agents use the backend while building that interface.

You can open Cortex with your account and inspect the shared components at socra.design. Meet AI eduarda explains how I delegate the work.

Initials were overflowing the small avatar circles in Cortex’s assignee chips. The shared avatar was using text sizes intended for a larger presentation, even inside a small chip.

My agents corrected that behavior in the shared component and checked readable fallback initials, image failures and larger text preferences. They published the component, updated Cortex and checked the signed-in production interface: the initials stayed contained and centered.

Journeys then adopted the correction. Its agents removed a local typography and color recipe so the shared component could own those details. They checked the deployed interface at wide and compact sizes, and checked initials and broken-image fallback in the local fixture.

Journeys supplied the foundation for Cortex’s UI. Work on Cortex improved a shared component that Journeys could then use. Each adoption required its own work and checks.

The design knowledge preserves how an avatar should behave and why. The shared component implements that behavior. Issues track the correction and the work needed to bring it into each product. An agent working on the next interface can retrieve the decision and use the corrected component.

We have carried other shared changes across products too. The October 20 shared-design record preserves a separate selection-styling change adopted by Cortex, Admin, Cloud Console, Workspace and the design catalog, alongside earlier Tasks work.

The retained records include the shared component release, successful Cortex and Journeys deployments, and the checks described above. Agents implemented, reviewed and released the correction. These are delivery records from the work, not a claim that every current screen was retested on October 21.

This record demonstrates shared implementation and checked adoption in both products. It does not measure saved human time, a falling cost per feature or an exponential improvement rate.