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

PrivateDAO Reform Backlog Index 2026

reform-backlog-index-2026.md

Boundary

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

Open raw file

PrivateDAO Reform Backlog Index 2026

This index converts the reform plan into four execution backlogs inside the repo.

Use it when deciding the next tranche of work across:

  • protocol safety and modularity
  • runtime, infrastructure, and monitoring
  • product UX and mobile operator flow
  • funding, grants, and submission posture

Canonical external planning note:

  • public hosted asset listed above

Backlog set

  • docs/reform-backlog-protocol-2026.md
  • docs/reform-backlog-runtime-infra-2026.md
  • docs/reform-backlog-product-ux-2026.md
  • docs/reform-backlog-funding-2026.md

How to use

For each tranche:

  1. choose exactly one backlog as primary ownership
  2. pick one Now item and one Next item at most
  3. verify repo truth before changing narrative or claims
  4. implement the smallest real closure
  5. rebuild evidence or packets only if the underlying truth changed

Current highest-value order

  1. runtime and infrastructure closure
  2. protocol safety and modularity
  3. product UX and mobile operator flow
  4. funding and submission packaging

Truth boundary

PrivateDAO has real Devnet evidence for wallet-first governance and reviewer-facing proof.

PrivateDAO does not yet have:

  • external audit completion
  • custody and multisig closure for production funds
  • complete real-device matrix closure
  • live monitoring delivery transcripts
  • source-verifiable settlement receipt closure
  • final mainnet cutover

No backlog item should be marked complete in public-facing materials as if these blockers were already closed unless the evidence exists.