Control Verification Record · Public Sample
C3 Control Verification Record — Approval Condition
Sample · Not certificationC3-CAV-2026-0001
A public sample showing how the same approval-empty counterexample changed from PASS with a permit issued before remediation to HOLD with no permit issued after remediation.
Verification state
NO_GAP_OBSERVED_FOR_DECLARED_WITNESS_SET
This state applies only to the fixed target version, declared control condition, and recorded witness set. It is not a repository-wide or system-wide safety judgment.
Declared control
What was checked
Before / After
The same counterexample was rerun after remediation
Before remediation
PASS
- permit token issued
- true
- predicate status
- GAP_CONFIRMED
After remediation
HOLD
- permit token issued
- false
- reason code
- EAG_APPROVAL_MISSING
Same-witness rerun: recorded. Negative controls: 3/3 PASS. A permit decision is not the same as observing an external effect.
Evidence binding
Fixed target and evidence anchors
Browser integrity recheck
Recompute SHA-256 against the published JSON bytes
The expected value is computed from the same public artifact at build time. The browser recheck verifies byte integrity only; it does not rerun the underlying system or independently reproduce the control experiment.
Pinned SHA-256
sha256:9ff53ecc10ecc8d36281ab42753056ed4c8882f3f39696905dcb3f9f27a4d240
Your browser fetches the raw bytes of the published JSON and recomputes SHA-256 locally. This checks integrity of the public artifact. It does not rerun the underlying control condition.
Display status
The verification fact and display freshness remain separate
What this record supports / what it does not support
Supported by this record
- • For the declared approval-empty counterexample, the record changed from PASS / permit issued before remediation to HOLD / no permit issued after remediation.
- • For the same counterexample after remediation, NO_GAP_OBSERVED_FOR_DECLARED_WITNESS_SET is recorded.
- • The raw bytes of the published JSON can be integrity-checked by recomputing SHA-256 in the browser.
- • Using the public evidence bundle and public verifier, another party can rerun the C3-provided verification procedure.
Not established by this record
- • That the repository or the system as a whole is safe.
- • That untested execution paths, control conditions, or witness sets would produce the same result.
- • That formal verification, third-party certification, conformance certification, or legal compliance has been obtained.
- • That future releases will produce the same result.
- • That a browser hash match alone proves the correctness of the control condition.
- • That rerunning the C3-provided verifier constitutes an independent implementation of the decision logic.
Verify ID: C3-CAV-2026-0001
Artifact schema: control-verification-artifact-v0.1
Document status: SAMPLE_NOT_CERTIFICATION
This English page is an explanatory representation of the same published record. The English delivery view uses the same Verify ID and evidence. It does not issue a new Verify ID, change the source artifact, create certification, or make English co-authoritative.