How one shared correction reached two products through three agents

Return to Meet AI eduarda

On October 24, 2026, a check of our design catalog found that the shared theme painted a fill on panes that were focused by code, not by a person. One agent corrected the shared theme and the web UI package and published them. A second agent adopted the release in Journeys and on this site. A third, signed in as a reviewer, accepted the Journeys release and found a separate defect, which the second agent fixed and deployed. I gave the direction at two points and did not open a repository.

Record prepared October 31, 2026 from the retained Issues, commits, workflow runs and served versions.

I asked for UI that compounds: one shared source, so hundreds of future products benefit from each improvement with the least friction. When the Journeys build failed on a check that hashed files inside the shared package, I said to remove guards if needed and keep zero defects.

The publisher corrected the focus fill in the shared theme, then corrected the web UI package after a check in a second product showed its fallback painting what the theme had declined. It published theme 0.10.118, web UI 0.0.535 and internals 0.8.338 with their receipts, and recorded the catalog check that accepted them.

The adoption agent moved the version pins in Journeys and here, and let each product’s normal checks and deployment run. Journeys failed first: its build compared eight files inside the installed shared package with hashes recorded for the previous release, so every shared header release would have failed it until someone re-pinned the hashes by hand. The agent removed that check instead of re-pinning it, and saved the rule in our design knowledge: a product adopts shared UI by moving the version it pins, and never re-verifies the shared owner’s work inside its own build. Journeys deployed as 0.0.2791 and this site deployed with the same release.

The review agent, signed in, checked Journeys at desktop and phone widths in light and dark. It accepted the release and found an unrelated defect: resizing an untouched New Socra across the phone breakpoint reported it as open in another tab, and going back left a stale row. The adoption agent traced both causes, fixed them with regression tests, and deployed 0.0.2792. The reviewer’s acceptance of that fix is recorded in its Issue.

Three agents with different roles carried one correction from a catalog finding to two deployed products, with each handoff in an Issue I can read. The work also removed a per-product check that would have taxed every future shared release. It does not measure time or cost saved, and the final acceptance of the repair is the reviewer’s to record.