Gold-State Parity™/write-path acceptance gate
Tests contribute evidence. A protected expectation and deterministic write-path gate govern acceptance: the application reproduces the expected state, or the change stops.
01 / The mechanism
A trusted, fixed, versioned gold state supplies the scenario inputs and the expected persisted result. The application sees the question, never the answer key. It must construct the contract-defined state through its own supported write path. The implementation and its tests may supply evidence; neither controls the answer key or the verdict.
Gold supplies both projections, but X receives only the input projection. X independently produces actual state, which is compared with Gold’s expected-state projection under the declared parity contract.
Independent, fixed, and versioned.
Declared business inputs only.
A supported screen or boundary.
Records and durable side effects.
Every in-scope element classified.
The test store begins from a declared baseline and is never seeded with gold. Every in-scope element is compared exactly, mapped, verified by rule, or excluded with a documented separate gate. Anything unclassified fails.
02 / Gate architecture
Full-interface verification does not scale. The gate separates proof of the translation from validation of the write path, then binds both to an acceptance decision that neither lane can award itself.
Version 1.0 of the paper calls this lane “Proof.” A deliberately selected set of scenarios runs through the actual interface. No shortcut or test-only back door. The Prove lane records the instruction shapes produced by supported user actions and verifies the translation from screen to application.
Selected real-interface traces
The full in-scope corpus runs through the application’s normal boundary, using only instruction shapes already demonstrated at the interface. A case matching no proven shape fails rather than being inferred.
Full in-scope corpus
03 / Failure evidence
The gate does not report that something broke. It identifies the scenario, record, field, expected value, and actual value. The artifact below shows the required verdict shape, not a claimed production incident.
A single compared-field disagreement is not a warning. The change does not pass until the failed scenario is rerun and the stored result satisfies the same versioned oracle.
04 / Claim boundary
A gate that claimed everything would be worth nothing. The acceptance claim is explicit about both its evidence and its edge.
05 / Engagements
The specification is open. The engagements below are the ways the mechanism is assessed, implemented, and identified in practice.
A written finding on whether your write path is actually gated or only observed, measured against the twelve published gate conditions and naming what would have to change.
Standing a Gold-State Parity™ gate up in a production-adjacent environment against the published rules: gold state, both lanes, comparison closure, and a fail-closed verdict. Diagnose-repair-rerun is a separate optional layer; the gate itself never repairs.
A licence to use the Gold-State Parity™ mark for a gate we built or assessed together, subject to continuing conditions. The mark remains a mark of origin, not a certification badge awarded at a distance.
06 / Inquiries
For an assessment, an implementation, or a direct question about the specification, write to Melvin Fahnestock.