Roadmap and release gates

Raidz progresses by evidence and safety gates, not by treating roadmap copy as shipped product.

Current phase

The product has a live pre-launch web/runtime foundation and substantial local domain/contract scaffolding. It remains before funded marketplace operation and token launch. The portfolio record classifies it as an active candidate/queued challenger; the public deployment does not itself change that evidence status.

Delivery sequence

1. Brand, public application, navigation, and truthful status.
2. Consented identity linking and creator profile.
3. Explainable Score V0 and shareable cards.
4. Recruit and validate an initial creator cohort.
5. Persistent mission marketplace and project workflows.
6. Reconciled, reviewed escrow and verifier system.
7. Real sponsored campaigns with measurable settlement.
8. Pons readiness and gated $RAIDZ launch.
9. Direct creator bookings.
10. Consented attribution and performance market.
11. Evidence-trained AI campaign assistance.
12. Scale only after repeat and unit-economics signals agree.

Required gates

Audience readiness

Use verified opt-ins, completed onboarding, demos, contributions, activation, return participation, and sponsor intent. Followers and impressions are secondary. Do not buy or fabricate engagement.

Marketplace readiness

Persistent campaigns, project verification, policy versioning, clear terms, creator eligibility, evidence handling, support, accounting reconciliation, and a complete non-value pilot must work.

Contract readiness

Schema reconciliation, expanded tests/invariants, independent review, role custody, pause/recovery, deployment verification, and monitoring must close before funds.

Token/Pons readiness

All live Pons configuration and launch checks must be current in the execution session. Product and audience readiness, legal/market-integrity review, signer safety, public address publication, and receipt verification must also pass.

Scale readiness

Several independent signals should accelerate together: verified campaign value, repeat projects, repeat creators, low disputes, reliable verification, qualified outcomes, contribution margin, and manageable support load.

Stop or pivot signals

Repeated failure to recruit credible supply, lack of sponsor willingness to fund, poor repeat use, unverifiable outcomes, unsafe compliance burden, negative unit economics, unresolved contract risk, or support requirements beyond capacity should reduce allocation or trigger a pivot. Token activity cannot repair weak product demand.

The detailed plan-by-plan record is ROADMAP_STATUS.md.