External Exposure Proof Bundle — First Run
- Run ID
- external-exposure-20260427T140210Z
- Workflow
- external-exposure-proof-run-v1
- Target
- witnessops.com
- Verifier result
- valid
- ZIP SHA-256
- a96cd612c98e6a9875c8f1930a7a2e38d6ac32b6c34fdf04f09461ba9d4b9f4c
Verify
Use this page to see what a published receipt can show now, what it cannot show, and what to inspect next.
This verifier checks receipt JSON in receipt-first v1 mode. It does not currently accept proof-bundle uploads, and it does not claim to prove the full runtime story.
If a check passes, read the trust limits before relying on the result. If it fails, read the named breach or failure before trusting any claim built on top of it.
The sample buttons below load verifier fixtures: public sample receipts used to show clean pass, named failure, and fail-closed behavior. They are not live customer artifacts.
The public verifier checks supported receipt JSON in receipt-first mode: schema, stage, signature fields, timestamp references, and receipt-level consistency checks.
It does not prove that every action was correct, that every decision was right, or that you now know the full story of an incident.
This public surface runs in receipt-first v1 mode. Proof-bundle uploads and unsupported receipt classes fail closed.
Browser input is sent to /api/verify for receipt-level checks in receipt-first v1 mode. Make sure that matches your handling rules before you submit a production artifact.
Expected outcome: valid for a known-good receipt.
This shows the verifier can reproduce a clean receipt pass path.
Expected outcome: invalid or input rejected with a named breach or failure.
This shows that failure is visible and explained, not hidden.
Expected outcome: a receipt-scoped result with clear trust limits.
This applies the same rules to your real artifact.
The required checks for the declared receipt scope passed. On /verify v1, this is receipt-scoped and does not prove artifact-byte revalidation or bundle completeness.
One or more proof-bearing receipt checks failed.
The receipt may be coherent, but a required outside trust condition could not be established locally.
Each downloadable ZIP is presented for offline verification with its included receipt, signer registry, source artifacts, and verifier-facing instructions. These bundles prove bounded WitnessOps-owned statements only. They are not live customer proof artifacts unless explicitly labeled otherwise. The public receipt console below remains receipt-first v1.
Paste receipt JSON, upload a `.json` file, or load a deterministic fixture.
/verify v1 accepts receipt JSON only. Bundles, mixed payloads, and unsupported receipt classes fail closed.
> paste a receipt JSON document or load a fixtureUse the docs below to inspect receipt structure, verification scope, and trust limits in more detail.