site(roadmap): rewrite public /roadmap against real open milestones#9253
Conversation
…9182) Replace the stale snapshot (frozen 2026-06-01, six phases referencing the closed v1 epics #233-#238) with the real, open, public epics: Rent-a-Loop (#4778), ORB cloud readiness (#4877), the hosted maintainer and miner chat platforms (#9183, #9184), the hosted bare-metal execution plane (#8534), and PostHog observability consolidation (#8286). Adds a recently-shipped callout and points the "see more" link at the live GitHub milestones list instead of the closed #127 roadmap issue. Every reference was verified open/public via `gh issue view` before being cited. No pricing, competitor names, or private-planning detail.
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
loopover-ui | a99ed9f | Commit Preview URL Branch Preview URL |
Jul 27 2026, 10:03 AM |
Bundle ReportChanges will increase total bundle size by 85 bytes (0.0%) ⬆️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: loopover-uiAssets Changed:
|
|
Warning ⏸️ LoopOver review result - manual review recommendedReview updated: 2026-07-27 10:15:30 UTC
Review summary Nits — 5 non-blocking
Concerns raised — review before merging
📋 Copy for AI agents — paste into your coding agentDecision drivers
Context & advisory signals — never blocks the verdict
Linked issue satisfactionNot yet addressed Review context
Contributor next steps
Signal definitions
🧪 Chat with LoopOverAsk LoopOver a question about this PR directly in a comment — grounded only in the same cached, public-safe facts shown above, never a new claim.
Full command reference: https://loopover.ai/docs/loopover-commands 🧪 Experimental — new and may change. Visual previewClick any thumbnail to open the full-size screenshot. Before = production · After = this PR's preview deploy. Scroll preview
A short scroll-through clip (desktop) — click either thumbnail to open the full animation. Evidence for scroll-linked behavior a single screenshot can't show. 🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed 💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →. Checked by LoopOver, a quiet PR intelligence layer for OSS maintainers.
|






Summary
The public
/roadmappage was frozen at a 2026-06-01 snapshot presenting sixphases tied to the closed v1 roadmap epics (#233–#238) — "MCP doctor
clarity", "command-copy flows" — a picture of the project from before the
autonomous review agent, the AMS miner, the certified guarantee,
Rent-a-Loop, or the bare-metal plane existed as public work. The page is
linked from site nav and external pinned material, so this directly
contradicted the homepage's actual positioning.
This is a content-only rewrite of
ROADMAP_ITEMS/COLUMNSagainst real,open, public epics — no redesign, no structural change.
What changed
ROADMAP_ITEMSnow cites six real, open, public GitHub issues (verifiedindividually with
gh issue viewbefore being referenced):issue roadmap: Gittensory ecosystem adoption v1 #127 are gone. The "see more" link now points at the live GitHub
milestones list instead.
decision replay, salvageability, federated fleet intelligence) — framed
narratively, no issue numbers invented for it.
LAST_UPDATED/LAST_UPDATED_LABELbumped to today.BUILT_TITLES/LINK_MAPcleared: none of the new forward-looking epicshave a live in-app surface yet (unlike the old phases, which linked to
/app/miner,/app/maintainer, etc.).roadmap.test.tsx's assertions to match the new content: guardsthat roadmap(phase 0): stabilize while shipping #233–roadmap(phase 5): ecosystem distribution #238 never render, that every card links to its real issue,
that the three columns render, and that the outbound link targets the
live milestones list rather than the closed roadmap: Gittensory ecosystem adoption v1 #127 issue.
Public-safety review
No pricing/dollar amounts, no competitor names, no private-planning
content, no wallet/hotkey/trust-score/reward specifics. Revenue framing
stays rail-agnostic ("settled on-chain via Bittensor or by conventional
billing").
Validation
npm --workspace @loopover/ui run format:check— cleannpm --workspace @loopover/ui run lint— 0 errors (pre-existingreact-refresh/only-export-componentswarnings across every route file,unrelated to this change)
npm run ui:typecheck— cleannpm --workspace @loopover/ui run test— 90 files / 639 tests passedgit diff --check— cleanHEADis flush withorigin/mainbefore pushing (no rebaseneeded)
Closes #9182