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.

northstar.dev/toolbar/decisions
Decision queueGate 3 blocked: 1 open decision tiered mvp
DEC-0003Checkpoint granularity defaultmvpopen
DEC-0001Product name — "Northstar" is a placeholderv1open
DEC-0002Three preset themes: Ledger, Foundry, Gazettemvpresolved
The decision queue: every choice filed with a resolve-by tier. A version can't enter build while a blocking decision is open.

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-0001

Vision-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.

resolved
FEAT-0002

The ID graph

Features, decisions, and architecture notes get permanent greppable IDs with typed edges — the index an AI maintainer would otherwise rebuild every session.

resolved
FEAT-0003

Trace linter

A CI linter that fails the build the moment the traceability graph rots — because 80%-accurate traceability is worse than none.

resolved
FEAT-0004

Implementation manifest

Code carries ID tags as ground truth; markdown gets a generated reverse index. Never hand-maintain both directions.

resolved
FEAT-0005

Live screenshots

Screens are real HTML/CSS components in a browser-chrome frame — not images. Change a design token and every screenshot changes with it.

resolved
FEAT-0006

Theme presets & fork-on-change

Two or three borrowed skins, switchable from the toolbar. Design is a costume, not a commitment.

resolved
FEAT-0007

Version 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.

resolved
FEAT-0008

Annotations

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.

proposed
FEAT-0009

Time travel & compare

Every checkpoint is an immutable deployed snapshot. Put "now" next to "three sessions ago" and watch the idea evolve.

proposed
FEAT-0010

GitHub 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