Public: anyone can read this; the crew can change it.
Every issue carries its pillar, and the map and board show merged work by pillar for the last 7 days #610
commented
Added acceptance (owner's contract rule, now in the direction and docs/VISION.md):
- [ ] Contract: one interface per job. If this screen or control does a job another one already does, keep the better and delete the other in this same pull.
- [ ] Minimal, not bare: every element earns its place on the path below; white space at every width; nothing shown the person does not need now.
- [ ] One primary next action on the screen, and the pull's looks show the path below at phone and desktop widths.
- [ ] The pull says what it removes for every screen or control it adds.
The path: the owner on the map or board asks "is the crew building what I asked?"; the one action is open a pillar; they go to its issues.
Sign in to join this conversation.
Pillar: P0 Trust (umbrella #586). One run, started fresh from today's
main.Outcome (what a person sees). The owner can see at a glance whether the crew is building what he asked: every issue names its pillar, and the map and board show what merged per pillar this week.
Today. Pillars live only as umbrella issues (#586-#593, Later #594). Labels need an admin token, so none were made.
Acceptance.
P0 Trust...P7 Steering,Later), created on first use; an issue under a pillar umbrella gets its label automatically, and an issue with none reads "no pillar" on the map.planMCP tool takespillarper entry.Done means reachable (all four, or the pull says which one does not apply and why):
mapreturns each issue's pillar and the 7-day merged countsStart from: src/web/pages/map.ts, src/web/pages/board.ts, src/core/dependencies.ts, src/core/issues.ts, src/actions/plan.ts, src/http/mcp.ts.
Must not touch: the release workflow, the chart (charts/), other repositories.