Site Execution Route Inventory - 2026-05-27

This inventory is the current ordering map for the PrivateDAO public site. It exists to reduce duplicate surfaces, preserve historical links, and keep new work focused on missing execution paths rather than rebuilding routes that already exist.

Operating Principle

PrivateDAO is a wallet-first private governance product for organizations and communities on Solana. The correct public path is:

1. Review governance or treasury context.
2. Run intelligence before signing.
3. Prepare encrypted intent, claim, payroll, settlement, or route preview.
4. Sign from the user wallet.
5. Verify with explorer, API receipt, Supabase timeline, or proof page.

Normal users should not need code or a terminal for the public product path. Integrations are not allowed to stand as empty product claims: each visible provider lane must either execute on Solana Testnet, prepare a wallet-signable Testnet operation, expose a live API receipt, or point to a proof document that explains the current boundary.

Product Corridors

The public site should collapse into four main corridors instead of presenting every provider as a separate product:

1. Private on-chain governance: /govern/, /execute/, /proof/, PDAO governance-token context, proposal, commit, reveal, treasury execution, and explorer/API verification.
2. Private money movement: encrypted payments, confidential payroll, PUSD/AUDD billing, Jupiter treasury routing, MagicBlock receipts, Umbra/Cloak settlement, and REFHE/Ika preparation.
3. Communities, competitions, and GamingDAO: reward pools, tournaments, community operations, and Colosseum reviewer flows that reuse the same governance and private treasury rails.
4. Intelligence before signing: QVAC, GoldRush/Covalent, SNS, Zerion, QuickNode, provider status, and policy context before any wallet approval.

Current Route Inventory

• Source app routes: 112
• Service source routes: 33
• Legacy/preserved bridge routes currently identified: 14
• Static pages generated by the current Next export: 605

The 605 generated pages include curated documents, viewer routes, track pages, and compatibility routes. That count should not be treated as 605 separate product concepts.

Canonical Service Routes

Preserved Bridges

These routes should remain as bridge pages, not duplicate product surfaces:

• /inttelignce/ -> /intelligence/
• /inteligence/ -> /intelligence/
• /intelignce/ -> /intelligence/
• /services/ika/ -> /services/encrypt-ika-operations/
• /services/encrypt-ika/ -> /services/encrypt-ika-operations/
• /services/palmusd/ -> /services/pusd-stablecoin/
• /services/palm-usd/ -> /services/pusd-stablecoin/
• /services/pusd/ -> /services/pusd-stablecoin/
• /services/torque/ -> /services/torque-growth-loop/
• /services/zerion/ -> /services/zerion-agent-policy/
• /services/goldrush/ -> /services/goldrush-decision-intelligence/
• /services/quicknode/ -> /services/runtime-infrastructure/
• /services/magicblock/ -> /services/magicblock-private-payments/
• /services/devnet-billing-rehearsal/ -> /services/testnet-billing-rehearsal/

Live Backend Evidence Checked

The following live surfaces were checked on 2026-05-27 without exposing secrets:

• https://api.privatedao.org/api/v1/readiness returned ok=true with Supabase-backed visitor and execution counters.
• https://api.privatedao.org/api/v1/provider-integrations/status returned ok=true on Testnet for provider status.
• https://api.privatedao.org/api/v1/qvac/runtime-proof returned ok=true.
• https://api.privatedao.org/api/v1/ika/solana-prealpha/final-approval returned the recorded Solana approval signature.
• https://api.privatedao.org/api/v1/quicknode/stream/stats returned ok=true for solana-testnet.

Supabase REST table counts checked through local configuration:

• visitor_sessions: 1429
• governance_receipts: 17
• operation_receipts: 14
• cloak_delivery_state: 19
• operation_execution_events: 10
• visitor_transactions: 63
• freshness_pings: 300
• onboarding_requests: 3

De-Duplication Rule

Before adding a new public route:

1. Check whether an existing canonical route already executes the action.
2. If the existing route is complete, add a bridge or link to it.
3. If the existing route is incomplete, complete that route instead of creating a new one.
4. If a historical URL is already public, preserve it with LegacyRouteRedirect.
5. Every canonical route must expose at least one of: wallet action, API endpoint, explorer proof, Supabase receipt path, or live verification page.

Current Missing Work To Evaluate Before Building

• Keep /services/devnet-billing-rehearsal/ as a bridge to /services/testnet-billing-rehearsal/.
• Audit generated viewer/document routes for stale wording, not duplicate product concepts.
• Keep /services/umbra-private-payments/ as a compatibility export of /services/umbra-confidential-payout/.
• Continue tightening /judge/ and /proof/ so their summaries always match the strongest live backend proof.