Skip to content

site: rewrite the public /roadmap page against the real open milestones #9182

Description

@JSONbored

Context

The public roadmap page (apps/loopover-ui/src/routes/roadmap.tsx) is frozen at LAST_UPDATED = "2026-06-01" and still presents six phases referencing issues #233#238 ("MCP doctor clarity", "command-copy flows") — a snapshot of the project from before the autonomous review agent, the AMS miner, the certified guarantee, Rent-a-Loop, and the bare-metal plane existed as public work. It is linked from the site nav and from external pinned material; anyone clicking through sees a much smaller project than the one that exists, directly contradicting the homepage.

Requirements

  1. Rewrite ROADMAP_ITEMS (and column hints) against the real open milestones: Miner Wave 5 — Rent-a-Loop, Hosted Bare-Metal Execution Plane, ORB Cloud Readiness (Epic: ORB Cloud Readiness #4877) and the hosted chat platforms (both epics), PostHog Consolidation where it's public-relevant, and the shipped-recently story (certified close guarantee, decision replay, salvageability, federated intelligence).
  2. Every item must reference a real, open, public issue or milestone — no invented phases, no stale numbers.
  3. Public-safety review of every line: no pricing/amounts, no competitor names, no private-planning content, no wallet/trust-score/reward specifics. Rail-agnostic revenue framing at most ("settled on-chain via Bittensor or by conventional billing").
  4. Update LAST_UPDATED/LAST_UPDATED_LABEL and keep the page's existing update discipline.
  5. Keep the page's existing component structure and design tokens; this is a content rewrite, not a redesign.

Deliverables

  • Updated roadmap.tsx content merged to main.
  • The page's OG description already matches the new positioning (landed with the hero PR); confirm page copy and meta agree.

Acceptance criteria

Out of scope

Redesigning the roadmap page layout; adding a changelog surface (the /changelog route already exists).

Metadata

Metadata

Assignees

Labels

maintainer-onlyOwner-only work — yields no Gittensor points.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions