Publish sanitized Policy-to-Proof trust record

[matt-dean-git]

Summary

• Reframes /verify-evidence-pack as the public trust page: “Don’t trust us—verify it yourself.”
• Makes the trust distinction explicit: embedded-key valid=true is self-consistency only; buyer proof requires trusted_issuer_valid=true against separately fetched or pinned JWKS.
• Publishes a compact, identifier-free Policy-to-Proof staging closure record with source and public-record SHA-256 fingerprints.
• Documents current limits: platform-secret-managed keys, no KMS/HSM or external assessment claim, no external archive anchoring/WORM claim, bearer-by-ID Evidence URLs, and no settlement/upstream/compliance inference.
• Extends the proof-spine guard to pin the trust copy, hashes, containment result, and non-claims.

Exact candidate

• Base: ea490b34cdb4b53c336c180c61014db34eaceb8c
• Head: 93ab87221a7dd38ea80ed4a6c3c2f7aab3eaf825
• Source sanitized manifest SHA-256: 62d00ac4bff91e56fea8f5e8e42ceb0bb46461c46ba5d5a8c9645047baba4f5a
• Public record SHA-256: 162f523d054feb99c2d65fadad7ecb3aa2d5127f1748160ca97424b73215eb7c

Containment evidence

Two historical staging Evidence bearer URLs were retrievable before containment. Their exact archive entries were removed from satgate-mcp-saas-staging, the process-local cache was cleared by an authorized staging restart, and both URLs now return indistinguishable HTTP 404 responses. No production system was touched.

Verification

• npm ci: PASS; zero vulnerabilities
• npm run test:proof-spine: PASS
• npm run test:well-known: PASS
• npm run test:receipt-schema: PASS
• npm run test:fable-burn-down: PASS
• focused ESLint: PASS
• production build: PASS; 124 static pages
• changed-file secret scan: PASS
• git diff --check: PASS
• Pre-existing production sample Pack: public fetch PASS; strict verifier valid=true and trusted_issuer_valid=true against separately fetched production JWKS; verifier no_secret_leakage=true; independent PII scan found zero paths. The only authorization-named field is a safe redaction marker.

npm run test:buyer-narrative fails on five stale required strings already absent on exact base ea490b34…; the same command and failures reproduce unchanged on base. This PR does not touch those files.

Boundaries

• Sanitized staging evidence only.
• No raw Pack, receipt, Evidence-access, payment, bearer, cookie, or continuation identifiers are published in the new record.
• No production promotion or broader release claim.
• The public JSON is a bounded closure record, not independent proof of the underlying runtime observations.
• No billing settlement, upstream truth, external archive anchoring, regulator-grade custody, KMS/HSM custody, or broad readiness claim.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
satgate	Ready	Preview, Comment	Jul 18, 2026 9:13pm