01 · PROBLEM
Catch zero-conflict semantic breakages before landing.
02 · HYPOTHESIS
When an agent changes an exported symbol, the platform extracts the contract (signature + existing tests/call sites) and runs sibling agents' new call sites against it in the runner; violations notify both agents.
03 · EVIDENCE SO FAR
LATESTNot tested. The agents gathered reports of the pain behind this idea and scored it on paper only; no experiment has been run on it. Cited pain: E-A001, E-X004, Codex fixture; E-C106 (modularity is not enough).website/projects.json
04 · NEXT FALSIFICATION TEST
Not yet scheduled. Smallest demo on record: TypeScript repo, A changes behavior of `greet()`, B adds caller; sentinel flags it pre-landing.
StatusParked; compared against running the full test suite on the merged state
We would drop or park it ifIf a plain "run full test suite on merged state" (A01/A03) catches every case the sentinel catches on 10 fixtures, it adds no value; kill.