Zk
Repository viewer
Legacy docs parity surface
Back to repository viewer
Repository document

ZK External Closure Package

zk/external-closure.generated.md

Boundary

This route preserves legacy markdown access inside the Next.js surface. The raw repository file remains authoritative.

Open raw file

ZK External Closure Package

Status

  • Project: PrivateDAO
  • Path: zk_enforced_external_closure
  • Status: pending-external-execution
  • Generated At: 2026-05-26T03:06:42.612Z
  • Pending Blocking Count: 3

Runtime Capture Summary

  • Runtime status: pending-zk-enforced-capture
  • Capture targets: 0/5
  • Mode activation successes: 0
  • Finalize successes: 0
  • Diagnostics captures: 0
  • Pending targets: Phantom, Solflare, Backpack, Glow, Android Native / Mobile

Stages

  • ZK-Enforced Runtime Captures: capture-required
  • owner: operators
  • blocking: yes
  • Record real wallet runs for enable-mode and finalize.
  • Do not mark complete until Devnet explorer signatures exist for successful captures.
  • External Audit Handoff: ready-for-external-review
  • owner: core-team
  • blocking: yes
  • The repository now includes an audit handoff package and explicit zk_enforced scope.
  • External findings and closure still need to happen outside the repository.
  • Canonical Verifier Boundary Freeze: decision-pending
  • owner: core-team
  • blocking: yes
  • Freeze whether receipt boundary or verifier-program boundary becomes canonical.
  • Do not claim final dominance until the written decision is signed off.

Required Docs

  • docs/zk/external-closure.json
  • docs/zk/enforced-runtime-evidence.md
  • docs/zk/enforced-runtime.generated.md
  • docs/zk/enforced-operator-flow.md
  • docs/zk-external-audit-scope.md
  • docs/canonical-verifier-boundary-decision.md
  • docs/audit-handoff.md

Commands

  • npm run build:zk-enforced-runtime
  • npm run verify:zk-enforced-runtime
  • npm run capture:zk-enforced-runtime -- <target> --template-only
  • npm run record:zk-enforced-runtime -- <capture-json-path>
  • npm run build:zk-external-closure
  • npm run verify:zk-external-closure

Notes

  • This package closes the remaining external path into one machine-readable tracker.
  • It does not invent captures, audit findings, or a frozen verifier decision before they exist.