Proof · cross-system

One spec. Two repositories. One verdict.

The expensive failure lives between repositories: a producer renames a payload key, the consumer reads the old one, and both test suites stay green. This recording shows the shape that catches it — one cross run that plans once, works per repository, then judges the boundary with a contract check before anything ships.

Click to pause. Each repository keeps its own sub-run and verdict; the cross gates judge the delivery as one system.

What to watch for

One profile is projected into global planning plus per-repository sub-pipelines — no glue scripts.
The contract check reads both sides of the boundary, where single-repo sessions never look.
Cross final acceptance blocks the whole set: a green repo cannot ship around a red boundary.

Cross-project mode (docs)Cross-project projection, the design (docs)Next proof: signal, not prose