Before remediation
Execution permit: issued
Decision PASS
C3 CONTROL VERIFICATION RECORDPublic sample · Not certification
Declared control condition
Approval is required for a PASS decision.
This delivery view shows what was checked, what was observed, the bounded scope, display freshness, and the public evidence route so a recipient can inspect the same record.
Limited to the recorded target version and conditions
What was confirmed
Confirmed that no execution permit is issued when approval is missing
This result is limited to the recorded target version, declared control condition, and checked witness set.
This is a public sample. It does not indicate customer adoption, product certification, or system-wide safety.
Verify ID
C3-CAV-2026-0002
- Published
- 2026-08-17
- Review recommended
- Legacy display policy
- Display expires
- 2026-11-15
- Target version
- 912ad7c5e100…
Issuance lineage
This Verify ID reuses the same underlying verification evidence as C3-CAV-2026-0001, but it is a separate issuance unit created to pass through the current receipt chain from the beginning. It does not imply that the legacy Verify ID had contemporaneous receipts.
mode
NEW_VERIFY_ID_REISSUE_FROM_LEGACY_RECORD
source Verify ID
C3-CAV-2026-0001
evidence reused
true
legacy receipt backfill
false
OBSERVATION AND REMEDIATION
Check the control change using the same case.
This record uses the approval-empty case. Before and after remediation are shown separately.
After remediation
Execution permit: not issued
Decision HOLD
Reason: EAG_APPROVAL_MISSING
Same-case rerun: recorded. Issuing or withholding a permit is separate from observing whether an external effect actually occurred. This record does not infer the external effect from permit state alone.
BOUNDED SCOPE AND UNOBSERVED SPACE
Use the checked condition as a decision input without generalizing beyond it.
Recorded scope
1 checked case
approval-empty
This is not a coverage percentage or safety score.
Boundary / operating envelope
Not inferred by this record
One before/after case does not establish a boundary across the condition space or a supported operating envelope.
Unobserved space
Cases not listed here
Other authority states, orders, targets, contents, retries, and recovery conditions are not generalized from this record. Unobserved does not mean unsafe.
How later gap-check work can build a broader operating picture
Baseline → change one condition → rerun → observe → compare → choose the next condition. Repeated observations can support a bounded map for a declared control and evidence class.
- Control preserved
PRESERVED - Control preservation was observed under the specified condition. This is not universal safety.
- Counterexample observed
COUNTEREXAMPLE_OBSERVED - An observation contrary to the declared control. It is not a system-wide danger judgment.
- Undefined
UNDEFINED - Requirements or comparator criteria are insufficient. Do not fill this into either safe or unsafe.
- Unobserved
UNOBSERVED - This evidence class did not observe the condition.
- Candidate
CANDIDATE - A follow-up candidate not yet established as a formal counterexample or boundary.
These labels explain the later method. This public sample does not add a multi-condition replay, boundary map, or independent boundary re-observation to the underlying evidence.
Keep the verification fact separate from display freshness.
The verification fact stays attached to its fixed target version. The external display state can separately move to review recommended, expired, superseded, recheck required, withdrawn, or unavailable according to the status record.
01
Fixed target
Result is tied to the target version, condition, and recorded cases.
02
Review timing
The status record determines whether review is recommended for this Verify ID.
03
Display expiry
Expiry affects current external display, not the existence of the historical evidence.
- Current display status
- FIXED_TARGET_ONLY
- Published
- 2026-08-17
- Review recommended
- Not set in this display policy
- Display expires
- 2026-11-15T23:59:59+09:00
A material change to the target, control, evidence, or relevant path can require rechecking before these dates. The site does not claim automatic monitoring of those changes.
The recipient can recheck the published materials.
The browser can check public JSON integrity and the evidence-to-result correspondence. It does not rerun the target system or perform an independent boundary search.
PUBLISHED RECORD INTEGRITY
Check whether the published record changed
Recalculate the SHA-256 fingerprint of the published verification record in your browser and compare it with the value bound to this page.
This confirms whether the published record bytes changed. The right-hand check compares the test result with the evidence bundle.
BYOV — BRING YOUR OWN VERIFICATION
Check the evidence-to-result binding
An AI provider can give this page to a customer or auditor, who can then compare the published evidence with the published test result in the browser. The same procedure can be repeated against the same public materials.
This button checks the relationship between the published evidence and test result. It does not re-run the original system and it is not third-party certification.
Evidence and claim boundary
Supported by this record
- • This record references, under a new Verify ID, the existing verification evidence in which the declared approval-empty counterexample 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.
- • This Verify ID is a separate issuance unit created to pass through the current receipt chain; it is not a receipt backfill for the legacy Verify ID.
Not established by this record
- • That an Issuance Receipt or Publication Receipt existed when C3-CAV-2026-0001 was originally issued.
- • That issuing this new Verify ID reran the underlying verification experiment.
- • 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.
Issuer: C3 Social Design Center
Verification record bound to a fixed target version, declared condition, and published evidence. This English page is an explanatory representation; Japanese remains authoritative.