01 · PROBLEM
Verify in <60 s what was tested, on which exact merge SHA, under which policy, by whom (a trusted runner, not the agent).
02 · HYPOTHESIS
Runner signs a receipt {source SHA, base SHA, merged SHA, test policy version, results, environment digest} stored as git note; UI and CLI `verify` check signature and recompute merged SHA.
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: provenance wanted as compact decisions not transcripts (E-C153 vs E-C154/E-C155); "deliver code you have proven to work" (E-C239); kernel "unverified reports" / Assisted-by (E-C214); Codex X3.website/projects.json
04 · NEXT FALSIFICATION TEST
Not yet scheduled. Smallest demo on record: agent claims green; receipt shows tests ran on stale base; platform rejects; after rerun receipt verifies.
StatusParked; the narrowed publication-receipt idea waits on a kill test
We would drop or park it ifIf a reviewer cannot detect a tampered or stale receipt in <60 s in a blind test, kill.