Root docs
Repository viewer
Legacy docs parity surface
Back to repository viewer
Repository document
Pilot Program
pilot-program.md
Boundary
This route preserves legacy markdown access inside the Next.js surface. The raw repository file remains authoritative.
Open raw filePilot Program
PrivateDAO is best introduced through a structured pilot, not an open-ended integration.
Pilot profile
Ideal pilot organizations:
- DAOs with treasury approvals
- grant committees
- crypto-native funds
- gaming guilds
- enterprise-style internal operations teams
Pilot structure
Phase 1 — discovery
- identify one real governance flow
- choose one treasury action type
- decide whether confidentiality is required
Phase 2 — simulation
- run the Production Simulation DAO flow on Devnet
- capture evidence
- train the operator
Phase 3 — controlled deployment
- define authority and signer model
- define monitoring expectations
- define launch blockers
Pilot success criteria
- operator can complete DAO creation and treasury funding
- operator can submit and pass a proposal
- operator can execute treasury safely
- evidence packet is understandable to a non-builder stakeholder
Pilot exit conditions
- proceed to stronger security and launch readiness
- continue on Devnet for another cycle
- or stop before mainnet if the operating fit is not yet strong enough