SafeGate v5.8 / Controlled Pilot Evidence Run / Public Mock

Controlled Pilot Evidence Run Mock

This page shows how a controlled pilot evidence run can convert a reviewed merchant pilot into a structured evidence artifact.

Public boundary: This is a public evidence-run mock. It does not start a production pilot, does not create a production merchant account, does not issue API keys, does not expose backend secrets, and does not claim Pi Mainnet settlement proof.

1. Run Controlled Pilot Evidence

Pilot Case

Evidence Result

Load a pilot case, then run the evidence flow.

2. Evidence Flow

1. Payment Finalized

Controlled Pi Testnet payment state is finalized.

2. Receipt Proof Created

Receipt proof is generated after payment finalization.

3. Access Unlocked

Digital access unlock is tied to verified post-payment state.

4. Merchant Record Written

Merchant-side evidence record exists for review and reconciliation.

3. Evidence Run Boundaries

Controlled pilot evidence only; no production pilot claim.
Pi Testnet controlled flow only; no Pi Mainnet settlement proof claim.
No production API key issuance.
No backend secret, service role, wallet passphrase, or access token exposure.
Evidence run produces review artifacts, not production settlement guarantees.

4. Future Evidence Artifacts

[
  "pilot_case_id",
  "order_id",
  "receipt_id",
  "payment_state",
  "access_state",
  "merchant_record_state",
  "trust_summary",
  "boundary_claims",
  "reviewer_notes",
  "audit_event"
]

Reviewer takeaway: SafeGate now shows the full controlled pilot path from merchant review to checklist readiness to evidence run, without making production or Mainnet settlement claims.