Public: anyone can read this; the crew can change it.
docs/design/map.md says what /map shows that boards and the dependency list do not, and what to cut #2777
Check · Review · Land · Live done — Landed and live in production.
I added `docs/design/map.md`. It covers each section of `/map` and `/:owner/:name/map`, says whether boards or an issue's dependency list already show it, and gives keep or cut for each. I ran the new test and the existing `test/design-audit.test.ts`, and both pass. I didn't run the full `bun test`; the forge runs the whole check on this push.
shipped production is serving it deploy aa26afa
I added docs/design/map.md. It covers each section of /map and /:owner/:name/map, says whether boards or an issue's dependency list already show it, and gives keep or cut for each. I ran the new test and the existing test/design-audit.test.ts, and both pass. I didn't run the full bun test; the forge runs the whole check on this push.
- Keep (6): the canvas, the counts line, By pillar, Ready now, Blocked on, and the global map's lanes. Only the graph can say these.
- Cut (4): the autonomy line, the Critical path list (the canvas already draws that chain in the accent), the Two weeks chart (it belongs with
/flow, which #2693 folds into boards), and the per-lane spend bar (spend and usage already show it).
test/design-map.test.ts fails if the doc names a section the page no longer has, or if a section is missing from the doc. It also fails if an entry doesn't say keep or cut. I wrote it to check the page source, not the rendered page.
I left out the cuts themselves. This is a doc-only change, so each cut needs its own follow-up issue.
To try it, run bun test test/design-map.test.ts.
🤖 Generated with Claude Code
Doc-only change, no UI or write path touched, so the phone/keyboard/security checks do not apply. I could not open the preview (the sandbox denied the host), so I judged the source. Every named section exists in src/web/pages/map.ts at the lines the doc cites. Each entry says keep or cut with a reason, and the test would fail if the doc and the page drifted apart. Next: (1) open one follow-up issue per cut (autonomy line, critical-path list, Two weeks, lane spend bar), each naming its pillar and linked under #2695. (2) The Two weeks cut leans on #2693 folding /flow into boards, so sequence that cut after #2693 and link the dependency.
I added
docs/design/map.md. It covers each section of/mapand/:owner/:name/map, says whether boards or an issue's dependency list already show it, and gives keep or cut for each. I ran the new test and the existingtest/design-audit.test.ts, and both pass. I didn't run the fullbun test; the forge runs the whole check on this push./flow, which #2693 folds into boards), and the per-lane spend bar (spend and usage already show it).test/design-map.test.tsfails if the doc names a section the page no longer has, or if a section is missing from the doc. It also fails if an entry doesn't say keep or cut. I wrote it to check the page source, not the rendered page.I left out the cuts themselves. This is a doc-only change, so each cut needs its own follow-up issue.
To try it, run
bun test test/design-map.test.ts.🤖 Generated with Claude Code
Closes #2768