Verification flow
01
Open the sample JSON
Open the fixed sample JSON to inspect the deliverable shape and the public scope.
02
Verify integrity
Recompute SHA-256 on the page and confirm it matches the included values.
03
Check public verification
Use the public minimal verification to confirm whether the result is MATCH or UNDETERMINED.
Scope
What you can confirm
- Integrity check match (PASS/FAIL)
- Public verification result (MATCH/UNDETERMINED)
What this page does not provide
- Signatures, issuer proof, or identifying who tampered
- Detailed verification results (after eligibility check)
- Compute performance, cost, or schedule estimation/comparison
Computed (Fixed)
Fixed demo cases computed with the current implementation (5 cases)
case set: 5 cases (caseId is not disclosed to prevent reverse engineering)
C0-CASE-01C0-CASE-02C0-CASE-03C0-CASE-04C0-CASE-05
The sample on this page (caseId: -) is a fixed public example for experiencing the acceptance flow of the 5-field public pack. You can inspect accepted_input_json as the public body, while readouts and contract-fixed supplements are not part of the pack body.
Note: You can confirm MATCH with the fixed sample.
Public verification is a minimal check: MATCH vs UNDETERMINED. UNDETERMINED does not constitute evidence of tampering; it may include not-yet-anchored, environment differences, or mismatches. Use the audit guide for the full acceptance structure.
If the fixed sample becomes UNDETERMINED, it may be due to 429 (busy) or temporary propagation delay. Please retry later.
See the authenticated run UI (for contracted users) for details.
Metadata
- caseId
- -
- Public reference
- -
- fixed_at
- -
- Verification digest
- -
- Pack hash
- -
Use `evidenceHash` as the first verification digest and `pack_sha256` as the tamper digest for the 5-field public pack itself.
Quick checks
- Verification digest included-
- pack_sha256 recomputation match-
Public verification is a minimal check: anything other than MATCH is treated as UNDETERMINED. Details are available after eligibility confirmation (for contracted users). UNDETERMINED does not constitute evidence of tampering; it may include not-yet-anchored, environment differences, or mismatches.
This page covers only the fixed sample and the minimal check. Use the audit guide for the auditor-facing reading order, including central-ledger verification, the Submission Bundle, and VERIFY_OFFLINE_1PAGE.md. Go to audit guide
If UNDETERMINED (what to do)
- Public verification may not be updated yet
- Mismatch due to environment/condition differences
- For a definitive decision, use detailed verification after eligibility confirmation (for contracted users).
Accepted input body
-
In the fixed public example, `accepted_input_json` shows what was accepted as input. Per-case readouts and contract-fixed supplements are not part of this public pack body.