Reference · Vision
Vision
Know why you're building this - and what to say no to - without re-reading the deck. The wedge, the cost-fusion moat, the four SKUs, and the positioning that every roadmap row traces back to. Lives at docs/strategy/strategic-vision.md; this tab is the readable view.
See it in motion
Where to find it
- Desktop:
http://localhost:4000/, then Reference (drawer) → Vision in the sidebar. - Hosted:
repoops.ai/team/reference(browse it from the Reference drawer) - Keyboard: ⌘ K, then type “Vision”.
- On disk:
docs/strategy/strategic-vision.md
What it does for you
The moat in a paragraph, not a deck.The doc names one moat, the cost-fusion intersection of knowledge, PRs, telemetry, and cost, unified so 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.Test every
docs/roadmap.md row against a pillar. 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 renders the markdown directly, so a saved edit shows up on the next load, with no build step.
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.