ATTENTION, WITH PROOF.Raidz roadmap status
The master plan is preserved verbatim in RAIDZ_MASTER_PROJECT_PLAN_2026-09.md. This file reports execution without changing its priorities.
| Plan item | Current state | Evidence / next boundary |
|---|---|---|
| 1. Rotate Telegram credentials | Protected credential active | The supplied token is installed through a protected file mount; @RaidzFun_bot is running and is an administrator of @Raidz_fun. Independent rotation provenance remains outside this repository. |
| 2. Lock brand and ticker | Working identity implemented | Brand system and UI use RAIDZ / $RAIDZ; professional name/ticker/handle/domain clearance remains open. |
| 3. Website and onboarding | Production foundation live | Next.js website, application shell, shared global navigation, token page index, provider controls, and creator-oriented score education are deployed. |
| 4. X + Telegram + wallet identity | Production runtime active | Reown, X OAuth and Telegram configuration are loaded through protected mounts. Telegram bot/channel status and X authorization configuration are verified; user-consent flows were not exercised, and X API reads currently expose a PAYG 402 boundary. |
| 5. Raidz Score V0 | Implemented and explained publicly | Exact initial weights, 0–1000 tiers, campaign-history influence, buyer interpretation, improvement paths, explanations, and tests are deployed. |
| 6. Shareable creator cards | Implemented as UI component | Export renderer and authenticated profile data remain. |
| 7. Recruit first 100 creators | Not started | Requires working onboarding, verified channels, consent, support, and recruitment cohort. |
| 8. Mission marketplace | Local interface/API foundation | No fixture is represented as funded. Persistent campaign CRUD and auth remain. |
| 9. Escrow and verifier contracts | Scaffolded | Foundry source/test suite, fuzz/invariant expansion and independent review required. |
| 10. Pons state/indexing | Architecture/schema scaffolded | Resolve and pin official factory/ABI/event set from live docs and chain. |
| 11. Initial funded campaigns | Not started | Requires real sponsors, terms, funds, contract review, and verifier operations. |
| 12–16. Access, launch, utility, graduation | Gated | Follow PONS_READINESS_GATE.md; no token or launch receipt exists. |
| 17. Direct KOL marketplace | UI foundation | Authenticated listings, bookings, escrow, reviews, and jurisdiction rules remain. |
| 18. Attribution/conversion | Schema foundation | Consent, link service, deduplication, retention and chain attribution remain. |
| 19. AI campaign automation | Planned | Requires historical marketplace evidence and human-review/claim controls. |
| 20. Scale | Not applicable yet | Requires authentic creator/project/settlement and retention evidence. |