Conformance Plan
Conformance Plan
Section titled “Conformance Plan”The normative specifications define Synchro behavior.
Conformance inputs define expected behavior. Production output does not define expected behavior.
Conformance Inputs
Section titled “Conformance Inputs”conformance/ contains authored requirements, vectors, scenarios, faults, artifact inventory, and the support matrix.
The support matrix is the sole machine-readable platform declaration.
Shared scenarios use contract-derived expected results. Applicable implementations consume those scenarios without copied expectations.
Proof Architecture
Section titled “Proof Architecture”Each behavior has one authoritative proof home.
- Contract tests consume specifications and authored vectors.
- Unit tests prove deterministic local behavior.
- Real integration tests use the extension, adapter, and PostgreSQL.
- Scenario tests execute authored semantic flows.
- Package smoke tests verify installation and lifecycle boundaries.
- Adversarial tests use critical faults and negative controls.
- Seeded stateful tests check independent invariants and record replay seeds.
Use real dependencies for happy-path integration and scenario flows.
Use mocks only for failures that real dependencies cannot safely trigger.
Proof Rules
Section titled “Proof Rules”Each production defect requires a permanent minimized scenario.
Critical faults must preserve the contract state that the test observes.
Expected values must come from the normative contract or an independent invariant.
Field presence and implementation-derived fixtures do not prove semantics.
Required gates run their declared Make selection and use structured results.
A missing, failed, skipped, or zero-test result fails the gate.
A result stream cannot show an omitted nonempty subset. Each required Make gate therefore rejects a changed test selector.
A diagnostic run with PARTIAL=1 can select a subset. It is not required-gate evidence.
Package smoke installs the packaged artifact. It verifies connect, push, pull, process termination, and resume.
This document defines durable proof architecture. It does not define release operations.
Use Testing Evidence for evidence policy and Testing Evidence Overview for evidence records. Use the Support Policy for maintained environment requirements.
Use RELEASE.md as the sole release procedure.