Synthesis Implementation Integrity

Verify that the implementation satisfies the user's outcome through its actual consumers. Tests establish only the behavior they exercise; inspect the changed data paths, deployment assumptions and required boundaries that those tests do not cover. Find and repair concrete gaps, then make an acceptance decision.

Binding rules

1. Verify the outcome through its actual consumers. Tests establish only the behavior they exercise; inspect the changed data paths, deployment assumptions and boundaries they do not cover.
2. Follow verification custody: an isolated copy by default; shared-checkout checks restore only their own authenticated changes, preserving concurrent edits.
3. Missing required evidence is unresolved, never N/A. Record a genuinely inapplicable pass with its reason; explicit repository and user gates still run.
4. A skip is not a pass. Read what was skipped; when a security, data-integrity or irreversibility claim rests on it, run the skipped test.
5. Trace every new data element through every layer, and verify the Nth implementation in a series with first-item diligence.
6. A bare TODO or "for now" does not ship. If it is not acceptable as permanent code, it is not acceptable to ship; an intentional scope boundary is documented.
7. Verification has an endpoint. When the required evidence is complete, return the verdict and advance; reopen accepted work only for a specific unresolved criterion or counterexample.
8. For autopilot task contracts, use the software and data/document methods. A disconnected or fixed-answer check is a substantive defect.
9. Releases need executable acceptance (PR CI on the exact head), extracted values and boundary authority, as the three sections below set out. A verifier is evidence; it never grants approval.