Dream the v5. Build the MVP. Never lose the thread.
Northstar is a methodology and toolkit for starting new products by building the marketing site and docs first — at full fidelity, in the cheapest medium — then building per version with permanent traceability from claim to code.
Why start with the marketing site?
Copy and HTML/CSS cost pennies; app code is expensive and churns. So Northstar starts where iteration is cheapest: you describe the product you can see in your head — not the MVP, the v5 — and it materializes as marketing pages, reference docs, and live screen mockups you can react to immediately.
Decisions are content, not chat scroll
Every choice made while dreaming is filed as a decision record with a resolve-by tier. Unresolved decisions aren’t failures — they’re queued against the version that must resolve them, and a version cannot enter build while one of its blocking decisions is open.
Traceability that survives refactors
Code carries permanent ID tags as ground truth; the site gets a generated reverse index. A trace linter runs in CI from day one, so the graph linking marketing claims to docs, decisions, screens, tests, and PRs never rots into the 80%-accurate kind that’s worse than none.
What exists today
Northstar is being built with its own methodology — this site is the dogfood.
The ID graph, trace linter, manifest generator, live screenshots, three
switchable theme presets, the version lens (?v=mvp — try it), and the
generated roadmap are running now; annotations and time travel
are next on the decision-gated roadmap.
FEAT-0001Vision-first product sites
Render the product you can see in your head as a marketing site, docs site, and live screens — before writing a line of app code.
resolvedFEAT-0002The ID graph
Features, decisions, and architecture notes get permanent greppable IDs with typed edges — the index an AI maintainer would otherwise rebuild every session.
resolvedFEAT-0003Trace linter
A CI linter that fails the build the moment the traceability graph rots — because 80%-accurate traceability is worse than none.
resolvedFEAT-0004Implementation manifest
Code carries ID tags as ground truth; markdown gets a generated reverse index. Never hand-maintain both directions.
resolvedFEAT-0005Live screenshots
Screens are real HTML/CSS components in a browser-chrome frame — not images. Change a design token and every screenshot changes with it.
resolvedFEAT-0006Theme presets & fork-on-change
Two or three borrowed skins, switchable from the toolbar. Design is a costume, not a commitment.
resolvedFEAT-0007Version slider & generated roadmap
Drag from MVP to v5 and watch the same site re-filter live. The roadmap is a generated page, not a promise.
resolvedFEAT-0008Annotations
Click any element on your own dreamed product and leave a comment. Claude works the queue; threads resolve like Figma comments — on the real site.
proposedFEAT-0009Time travel & compare
Every checkpoint is an immutable deployed snapshot. Put "now" next to "three sessions ago" and watch the idea evolve.
proposedFEAT-0010GitHub round trip
Branches, commits, and PRs carry feature IDs; merges flip status, stamp the manifest, and write the changelog. Drift is caught at the moment of change.
proposed