Three repos. Seven agents. 4.5 hours.
Read the numbers again: seven AI sessions across two providers restructured three interlocking repositories in one afternoon — and a separate lane signed off on the result. That is roughly a week of a well-coordinated team’s work, compressed into the time between lunch and dinner, with an audit trail.
The mission
A structural reorganization across three foundational repositories of the Sociail platform — the kind of cross-cutting change that usually blocks a team for a week, because every repo touches the others and nothing can move alone.
The fleet
Seven agent sessions — two Claude, five Codex — coordinated on the cait substrate: work split into bounded lanes per repository and concern, handoffs delivered fail-closed between them, and a separate CEO lane holding independent validation — the implementing lanes never graded their own work. Wall-clock from start to validated finish: about 4.5 hours.
| CLAIM | DETAIL | EVIDENCE |
|---|---|---|
| Fleet mix | 2 × Claude, 5 × Codex sessions, coordinated as one program of work | ● attested |
| Scope | Structural reorg across three foundational repositories (private) | ● attested |
| Wall-clock | ~4.5 hours, start to validated finish | ● attested |
| Validation | Independent acceptance by a separate lane (CEO@macstudio), not the implementers | ● verified |
| Substrate | icodex v0.3.0-rc.43-era coordination: handoffs, inbox, cross-mac summaries, receipts | ● verified |
The shape of the work
Why this one matters
- Cross-cutting is the hard case. Parallel agents are easy when work is independent. Three repos that must change together is where uncoordinated fleets produce merge disasters — and where governance (one writer per boundary, bounded handoffs, explicit acceptance) is the difference between 4.5 hours and a lost week.
- Mixed providers, one program. Claude and Codex lanes worked the same goal under the same contracts — the unification claim, exercised for real.
- Implementation ≠ acceptance. A dedicated validation lane signed off. That separation is the receipts culture at team scale — and the pattern the advisory brain will automate checks for.
The validation receipt
Retrieved from the CEO lane’s session summary over the workstation mesh, 2026-08-14 23:08 UTC:
project state: FOUNDATION_GREEN_ACCELERATED_DEVELOPMENT_RELEASED
LocalDev + nine repositories clean on dev@origin/dev · one checkout each, zero stashes
setup dry-run · first execute · byte-stable repeat · doctor: zero failures
binding mode 0600 · revision 1 · sha-256 1b51072c…
The DOCS lane, observed the same evening, had already moved to post-release guardrails — “stop agents recreating legacy topology… prove the clean foundation under ordinary development pressure” — the reorg not just done, but holding.
Honest limits
The fleet mix, wall-clock, and three-repo scope are operator-confirmed (2026-08-14; the estate-wide validation covered LocalDev + nine repositories); the outcome and validation are now receipt-verified — the validation record above was retrieved directly from the studio and its marker flipped, exactly as this page promised it would be. The scheduling was human: an operator authored the lane split and the handoffs. Making that faster and safer — measured acceptance seams, isolated workcells, bounded coordination — is precisely the roadmap.