Receipt scanner

Inspect the receipt, scanner, and manifest.

The sample path is the boarding credential desk for ZLAR. It shows a bounded routed action, the rule and authority question, the receipt, the scanner checks, the manifest files, and the side-door limits that stay outside the claim.

Inspect the receipt Run the scanner Download the manifest
boarding credential sample
passengerrouted MCP tool call sample
checkpointsigned policy and bounded authority fields
scannerhashes, manifest, coverage, and non-claims
side doorsrouted/intercepted surfaces only
What the receipt says

A receipt settles the boarding boundary.

In ZLAR, the boarding ticket is the receipt: a verifiable record that this action crossed this checkpoint under this policy and authority. The sample receipt points to a bounded evidence bundle. It records the passenger action, the checkpoint rule, the boarding decision, the scanner path, and the coverage report that says what ZLAR saw and what it did not see.

For developers and auditors, the technical artifact name is Proof Pack v0. For a first visitor, the important thing is simpler: a log records what happened; a receipt records what counted as authorized effect.

Scanner lane
Receipt

One governed boarding decision.

Scanner

Downloaded files match.

Manifest

Scope and limits are named.

Side doors

Privacy and claim scans pass.

Proof questions

Read the receipt as a boarding credential.

The receipt scanner should answer the plain questions before the technical appendix asks anyone to read release archaeology.

Passenger

What action tried to board?

The bounded sample action, not a claim over all agent behavior.

Checkpoint

Which checkpoint did it cross?

The routed surface where policy can decide before effect.

Policy

What rule applied?

The signed rule and authority question for this route.

Receipt

What receipt was produced?

The verifiable artifact showing what counted as authorized effect.

Scanner

What verifies it?

The local verifier, hashes, manifest, and coverage checks.

Side doors

What remains outside?

Unrouted paths and stronger claims that this sample does not prove.

Scanner command

Verify the boarding credential in Terminal.

These commands download the public sample manifest, check the SHA-256 sidecar, and run the local scanner for this bounded sample. 

mkdir zlar-proof-pack-v0-scratch
cd zlar-proof-pack-v0-scratch
mkdir -p evidence

curl -fsSLO https://zlar.ai/demo/proof-pack/README.md
curl -fsSLO https://zlar.ai/release.json
curl -fsSLO https://zlar.ai/demo/proof-pack/proof-pack-manifest.json
curl -fsSLO https://zlar.ai/demo/proof-pack/SHA256SUMS
curl -fsSLO https://zlar.ai/demo/proof-pack/verify-proof-pack.mjs
curl -fsSLo evidence/governed-profile-coverage-report.json \
  https://zlar.ai/demo/proof-pack/evidence/governed-profile-coverage-report.json
curl -fsSLo evidence/governed-profile-coverage-report.txt \
  https://zlar.ai/demo/proof-pack/evidence/governed-profile-coverage-report.txt

shasum -a 256 -c SHA256SUMS
node verify-proof-pack.mjs

Sample disclosure

  • This sample uses fake/scratch artifacts only.
  • It verifies hashes, manifest, coverage boundaries, and privacy/claim checks for a sample path.
  • It is not production deployment evidence.
  • It is not external non-Vincent verifier attestation.
Manifest files

Download the sample manifest directly.

These links download the same public sample files used by the scanner commands.

README Release Metadata Manifest SHA256SUMS Verifier Coverage JSON Coverage TXT
Scanner result

A clean scan ends in PASS.

The output should show every downloaded file as OK, followed by PASS lines for the manifest, claim ceiling, coverage type, hashes, non-claims, privacy flags, and text scans. 

release.json: OK
README.md: OK
proof-pack-manifest.json: OK
evidence/governed-profile-coverage-report.json: OK
evidence/governed-profile-coverage-report.txt: OK
verify-proof-pack.mjs: OK
PASS proof-pack manifest type
PASS manifest claim ceiling
PASS coverage report type
PASS coverage claim ceiling
PASS release metadata safe claim ceiling
PASS manifest release version matches release metadata
PASS manifest release URL matches release metadata
PASS manifest release metadata timestamp matches release metadata
PASS hashes match manifest entries
PASS non-claims present
PASS privacy flags are false
PASS privacy and claim text scan
PASS scratch proof pack verified

Scanner appendix: current scope

Receipt scanner summary: the public sample is fake/scratch evidence for one bounded routed action path. It shows the receipt, manifest, verifier checks, coverage map, and explicit non-claims.

Public release metadata and proof-pack detail live in Public Proof Desk. Current core source access is private; source review is by request.

  • ZLAR governs routed/intercepted action surfaces only.
  • Safe Codex wording: "ZLAR can govern Codex CLI-invoked MCP tool calls when those MCP servers are routed through ZLAR."
  • Unrouted shell/filesystem/browser/app/network/model-reasoning/final-text surfaces are not claimed as governed by this proof path.
  • /contest is not implemented.
  • A private-by-default non-Vincent verifier request has been sent; no public external attestation is claimed in this repo, and any private reply or later result remains bounded by verifier relationship, disclosure permission, and exact evidence returned.