Tab · Product
Vision
Know why you're building this — and what to say no to — without re-reading the deck. The four pillars, the moats, and the positioning that every roadmap row inherits from. Lives at docs/strategy/strategic-vision.md; this tab is the readable view.
See it in motion
Where to find it
- Localhost:
/strategic-vision.html?repo=<id> - On disk:
docs/strategy/strategic-vision.md - Keyboard: ⌘ K then
vision - Sidebar: Product → Vision
What it does for you
One paragraph per pillar, not a deck.Brain · Telemetry · Ledger · Routing — each gets a one-liner that explains what the moat is and why a competitor can't copy it in a weekend. Read it in two minutes, defend the roadmap in five.
Tells you what to say no to.Every “why we won't build that” lives next to its pillar. New feature request lands? Check the vision before opening the issue — most asks dissolve against an explicit no.
Roadmap rows trace back to a pillar.Every
docs/roadmap.md item names which pillar it serves. If a row doesn't fit, the vision is wrong or the row is. Either is useful to know early.Configure
Nothing — hand-edit the markdown when positioning changes. The tab auto-rebuilds; the HTML twin is auto-synced by npm run sync-brain.
Use it well
Read Vision at the start of any planning window; re-read it before opening a new feature PR. When the answer to “should we build X?” is unclear, the vision is the tiebreaker. If you keep losing the tiebreaker the same way, the vision needs editing — not the roadmap.