PrivateD△O
Search or ask AI
Strategy
Curated in-app view
Raw file remains authoritative
Back to documents
Document route

Competition Execution Playbook

Development playbook for keeping product, demo, docs, proof, and UX aligned with the active competition targets.

Boundary

Execution guidance only; it does not by itself upgrade the repo beyond what is actually implemented.

Audience: Founders, operators, product leads, reviewers

Open raw file

Competition Execution Playbook

This playbook keeps PrivateDAO aligned with the active Frontier and Superteam tracks without drifting into inaccurate claims or random feature work.

It is complementary to `frontier-competition-readiness-2026.md`:

  • `frontier-competition-readiness-2026.md` answers: which tracks matter most and why
  • `competition-execution-playbook.md` answers: how development should stay aligned with those tracks

It should now also be read with:

  • `colosseum-frontier-2026-operating-brief.md`

because the April 2026 Frontier cycle changed the operating baseline around:

  • product impact
  • signer and governance security
  • migration discipline
  • runtime and incident posture

Non-negotiable constraints

  • Do not weaken the protocol story to chase a trend.
  • Do not touch the contracts or protocol layout unless explicitly required.
  • Do not overstate audit, custody, or mainnet readiness.
  • Do not claim encrypted AI, partner integrations, or operational support that is not already real.
  • Do not frame PrivateDAO as "audit-complete therefore safe"; after Drift, operating posture must remain visible.

Always preserve these foundations

  • `ZK`
  • `REFHE`
  • `MagicBlock`
  • `Fast RPC`
  • `Governance Hardening V3`
  • `Settlement Hardening V3`
  • `Live proof`
  • `Live proof V3`
  • `Mainnet blockers`

These are not optional decorations. They are the differentiation layer.

Product-level priorities

1. Privacy-first strength

Push hardest where PrivateDAO is naturally strongest:

  • private voting
  • reviewer-visible proof
  • confidential operations
  • additive hardening
  • explicit trust boundaries

2. RPC and infrastructure strength

Keep investing in:

  • hosted reads
  • diagnostics
  • runtime evidence
  • API-facing surfaces
  • operator and buyer packaging

2b. Operating-security strength

Keep reinforcing:

  • signer posture
  • timelock visibility
  • explicit launch blockers
  • wallet runtime honesty
  • durable-nonce-aware security framing
  • STRIDE-style operational maturity

3. Consumer and wallet strength

Keep improving:

  • wallet onboarding
  • route clarity
  • mobile and Android affordances
  • simpler first-run decisions

4. Competition clarity

Each surface should answer one of these quickly:

  • what is PrivateDAO?
  • why is it hard to copy?
  • what is already live?
  • what still needs external completion?
  • why does this fit the target track?

Required surface consistency

If the product story changes, consider whether the same change must appear in:

  • Next.js route structure
  • `/story`
  • `/start`
  • `/tracks`
  • `/tracks/[slug]`
  • `/services`
  • `/command-center`
  • `/security`
  • curated documents
  • README
  • demo and deck materials

Default implementation bias

When multiple improvements are possible, prefer this order:

  • better live UX
  • cleaner operational routing
  • stronger wallet-first experience
  • stronger operating-security readability
  • stronger reviewer readability
  • stronger track-specific positioning
  • only then add new speculative corridors

Track-specific emphasis

Privacy Track

Lead with:

  • `PrivateDAO Core`
  • `Gaming DAO Corridor`
  • `ZK Capability Matrix`
  • `Cryptographic Confidence Engine`

RPC credits track

Lead with:

  • `Read API + RPC`
  • diagnostics
  • hosted read surfaces

Consumer Apps

Lead with:

  • cleaner navigation
  • clearer onboarding
  • `/start`
  • command center
  • wallet-first interaction

Eitherway / live dApp

Lead with:

  • real wallet UX
  • live operational flow
  • infrastructure partner corridor
  • story video, `/start`, and wallet-first track workspace

Colosseum Frontier main judging posture

Lead with:

  • product impact
  • startup-grade polish
  • visible operating discipline
  • proof and trust continuity
  • security posture that survives the post-Drift environment

Ranger / 100xDevs

Lead with:

  • integrated product coherence
  • polished operational shell
  • evidence-backed readiness

Validation

For competition-facing frontend work, finish with:

cd /home/x-pact/PrivateDAO/apps/web
npm run lint
npm run build

cd /home/x-pact/PrivateDAO
npm run web:bundle:root
npm run web:publish:root
npm run web:verify:live:root
npm run verify:submission-registry
npm run verify:test-wallet-live-proof:v3

If the work touched reviewer or proof surfaces, also verify the relevant docs and generated artifacts remain consistent.