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

Reviewer Fast Path

reviewer-fast-path.md

Boundary

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

Open raw file

Reviewer Fast Path

This is the shortest high-signal route for a judge, auditor, technical reviewer, or curious operator.

The goal is simple: in under two minutes, the reviewer should understand that PrivateDAO is not a pile of disconnected experiments. It is one product where governance, confidential operations, telemetry, and trust reinforce each other.

Two-Minute Review

  • https://privatedao.org/start/
  • This shows the wallet-first governance path as a normal-user product entry, not only a protocol demo.
  1. Open the live product shell:
  • https://privatedao.org/security/
  • This shows how privacy and confidential treasury motion are expressed as usable workflows, not only cryptographic vocabulary.
  1. Open the confidential operations surface:
  • https://privatedao.org/services/
  • This shows governed treasury motion, payout planning, route context, and execution framing inside one operating lane.
  1. Open the services surface:
  • https://privatedao.org/trust/
  • This shows the review posture: hardening, evidence, custody truth, and launch discipline.
  1. Open the trust surface:
  • https://privatedao.org/judge/
  • This shows the shortest reviewer-facing path into proposal lifecycle, Devnet signatures, and the agentic micropayment rail.
  1. Open the judge route:
  • https://privatedao.org/proof/?judge=1
  • This shows that the product is paired with reviewer-readable evidence rather than unsupported claims.
  1. Open the proof surface:

Why this route works

This path compresses the whole thesis into one readable sequence:

  • start proves the governance product is real
  • security proves privacy is part of the workflow
  • services proves treasury and payment motion are operational, not decorative
  • trust proves the team cares about reviewability and launch discipline
  • judge proves that captured Devnet execution is easy to inspect
  • proof proves the claims are tied to evidence

Five-Minute Review

If the reviewer wants to go deeper:

  • https://privatedao.org/analytics/
  • docs/reviewer-telemetry-packet.generated.md
  1. telemetry and infrastructure:
  • https://privatedao.org/custody/
  • docs/treasury-reviewer-packet.generated.md
  • docs/canonical-custody-proof.generated.md
  1. treasury and custody:
  • https://privatedao.org/story/
  • docs/submission-dossier.md
  1. product and story context:
  • docs/mainnet-blockers.md
  • docs/technical-verification-status-2026.md
  1. launch truth:

Verification Commands

If the reviewer wants one command:

npm run verify:all

If the reviewer wants the breakdown:

  • docs/verification-gates.md

Canonical live anchors

  • Program ID: EP9xE8MJZ6FfyEwLqns6HDdUZBknEa7WGYs1Jzsecuva
  • verification wallet: 4Mm5YTRbJuyA8NcWM85wTnx6ZQMXNph2DSnzCCKLhsMD
  • live product: https://privatedao.org/
  • docs viewer: https://privatedao.org/documents/

Public boundary

This fast path is product-facing and review-facing.

It explains:

  • what exists
  • why it matters
  • how to inspect it quickly

It does not expose private sponsor tactics, internal submission handling, or confidential operating notes.