Public: anyone can read this; the crew can change it.
The map is the owner's roadmap: pillars in order, what's building, what landed, what's next, and when each finishes #10303
the crew's run was interrupted: restart, resumes on the next pass — cancelled
Sign in to join this conversation.
The owner on 2026-11-09: "i would really like the map to be great. this is what i need to start using to follow along on the forge. i feel like im starting to be out of the loop".
Today
/:owner/:name/mapis the dependency graph: an engineering view. The owner needs the roadmap, the pillars in the order the crew works them, readable in under a minute on a phone. Follow the P9 Calm rules (#10296): one answer at first sight, no notes, depth opens in place, the same compartments on every visit.First view, top to bottom
- its name; - a done/total bar; - who is building now (crew avatar and issue title); - the last landing (title and age); - what's next (the top startable issue); - its ETA.
The current pillar is open; done pillars fold to one quiet line; future pillars show one line.
Depth in place
?view=graph.Live
Data
GET /api/v1/repos/:owner/:name/roadmapand on MCP, so agents and the phone read one source.src/core/pillars.ts; ETAs come frommergedByPillar.Done when
/trevato/forge/mapopens on this view.Try: open https://forge.open-platform.sh/trevato/forge/map on a phone.