Commit graph

1 commit

Author SHA1 Message Date
senke
5b2f230544 docs(roadmap): add v1.0 → v2.0.0-public launch roadmap (6 weeks)
Some checks failed
Veza CI / Rust (Stream Server) (push) Successful in 4m12s
Security Scan / Secret Scanning (gitleaks) (push) Successful in 41s
E2E Playwright / e2e (full) (push) Failing after 14m25s
Veza CI / Backend (Go) (push) Failing after 14m43s
Veza CI / Frontend (Web) (push) Successful in 26m12s
Veza CI / Notify on failure (push) Successful in 4s
Living operational document tracking the path from v1.0.8 to public
launch as a SoundCloud-alternative. Compresses the original 24-week
plan to 6 weeks by explicit scope-control:

  - §2 Scope contract: IN/OUT/COMPRESSED matrix (what ships, what
    defers post-launch v1.1+, what's MVP-but-shippable)
  - §1 External actions EX-1 to EX-12 (legal, pentest, DMCA agent,
    DNS, TLS, CDN, OAuth secrets, Stripe live, transactional email,
    status page, coturn) with cycle estimates
  - §4 Day-by-day sprint breakdown for 6 weeks (W1 v1.0.9 + Ansible,
    W2 Postgres HA + obs, W3 storage HA + signature features,
    W4 PWA + HLS + faceted search + load test, W5 pentest + game day
    + canary + status page, W6 GO/NO-GO + soft launch + go-live)
  - §6 Risk register (R-1 to R-10) with mitigations
  - §7 Defended scope (refused additions during the 6 weeks)
  - §8 37 absolute Production-Ready criteria

Daily updates expected: tick acceptance criteria as they land, commit
each update with `docs: roadmap launch — <jour X> done`.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-26 23:50:07 +02:00