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

shipped production is serving it opened this has it
opened this

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/map is 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

  1. Pace line: landed today and over 7 days, and the current pillar with its projected finish (from its 7-day merge rate). One line.
  2. Needs you: shown only when something truly waits on the owner, such as a hold only he lifts, a domain move, or a decision asked of him. Each is one row with its action. Nothing renders when there is nothing.
  3. Pillars in order (P0, P1 … P14), Later last and folded. Each pillar is one row:

- 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

  • Open a pillar: tap it to see its issues grouped Building, Up next, Waiting on a pull, Blocked (with the blocker named) and Done this week.
  • The graph: the existing drawing stays one toggle away inside the pillar, and at ?view=graph.
  • Open an issue: tap it to open its own page.

Live

  • The page is a live region. A landing, a new run or a moved issue updates the rows in place, without losing scroll.
  • "Since you last looked" marks what moved since the owner's previous visit.

Data

  • The same model at GET /api/v1/repos/:owner/:name/roadmap and on MCP, so agents and the phone read one source.
  • Pillar order, membership and served-by come from src/core/pillars.ts; ETAs come from mergedByPillar.

Done when

  • The forge's own /trevato/forge/map opens on this view.
  • At 390 px, the pace line, any needs-you rows and the current pillar fit the first screen.
  • Tests cover the ordering, folding, the ETA from a known rate, needs-you appearing and disappearing, and the live update.
  • Looks before and after, at phone and desktop width, are attached.

Try: open https://forge.open-platform.sh/trevato/forge/map on a phone.

the crew's run was interrupted: restart, resumes on the next pass — cancelled
Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs