Synthetic example · Recorded results

What this example proves.

The demonstration presents an existing recorded local acceptance run of package GZ-KAP-001. It does not start a live engine run or process visitor documents. The browser checks the sample's SHA-256 before displaying results.

Recorded source

Two local reports, proof/proof-report-run-1.json and proof/proof-report-run-2.json, report passing status. The second records a byte-identical governed rerun. Their handover hashes match the archived object gate-zero-local/handovers/GZ-KAP-WS/0001/0001/handover.json. This is historical local-run evidence, not a new production qualification.

Original handover SHA-256:
3c3888c92a7e4db8e12e1313203cc3045380d13812c60c8490000cff34f4928a

Shared governed-run digest:
56870caf021893ae511de109d9f89037370894a367c72fc58f651f1a4a1a9b05

The downloadable copy adds a final newline for text-file packaging. Its original-source hash is checked after removing trailing whitespace. It is not advertised as a byte-identical downloaded file. The example uses a fixed synthetic clock; January 2026 dates are fixture values, not claims about deployment dates.

Findings, without inflated claims

• Missing evidence: finding FND-000003 and the missing match for GZ-COMP-M-9000.
• Ambiguous identifier: finding FND-000002; two records declare GZ-COMP-X-7000. Their file hashes differ. This does not establish duplicate file content.
• Searchability failure: finding FND-000001. The reviewer required replacement evidence and the recorded response closed the finding. It is not an unreadable-page finding.

The handover preserves all three findings and their recorded human decisions. The landing page's plain-English next steps are presentation summaries, not new engine results or an alteration to the recorded handover.

Sample handover

Nine document entries, their hashes and identifiers, matching results, findings, reviewer decisions and response evidence. Document bytes are not bundled. The example's invalid inputs and local backup database are not published.

Boundaries

This demonstration does not prove regulatory compliance, technical adequacy, regulator acceptance, customer readiness or a successful live customer replay. A free replay request opens an enquiry email only. Do not send submission documents until scope, authorization and secure transfer have been agreed.