35.6. Acceptance🔗

• D12 — Acceptance as a gate. Acceptance is a gate against the specification the model document proves — run, as proof-by-execution, rather than asserted. This is the load-bearing link between the two documents: without it, everything the model proved stops at the model's own boundary.

• D13 — A paired A/B in the executable. Performance claims are a paired A/B in the deployed executable. A microbenchmark ranks; it does not predict. An isolated win of a factor of two and a half can be zero in the binary that ships, and the only measurement that settles the question is the one taken in the executable whose behavior is being claimed.

• D14 — What each green signal covered. The rubric that costs the least and is skipped the most: each green signal must name which of the changed lines it actually compiled or ran. A pipeline that passes without compiling the changed path is evidence about the paths it did compile and about nothing else, and quoting it as though it covered the change is how two defects survive three green signals.