The Blueprint Preview Map
On this page
The Blueprint Preview Map
An interactive diagram of everything your spec will build and how it connects — features, roles, pages, and data as one graph. · Recommended
The bottom half of the Prepare page is the Blueprint Preview Map. It's the fastest way to sanity-check your blueprint before you hand off: if a page isn't wired to any data, or a role can't reach the pages it needs, you see it here as a missing edge instead of discovering it mid-build. The map is read-only and available on Starter and above — it's derived entirely from your existing spec with no LLM call, so viewing it never consumes generations.
A confidence banner above the map keeps expectations honest: while your schema, links, or permissions are still incomplete, it labels the map as a preview of what will be built, not final code.
What's on the map
Four toggleable layers, each with its own colour:
| Layer | Colour | Shows |
|---|---|---|
| Features | Indigo | Your features, connected to the pages that deliver them. |
| Roles | Violet | Personas/roles, connected to the pages they can access. |
| Pages | Sky | Every page in the spec. |
| Data / Entities | Emerald | Schema entities — each node lists up to five columns, with a "+more" indicator beyond that. |
Between them, five kinds of edges: feature groups page, role can access page, page reads/writes data, data relationships (foreign keys), and navigation between pages.
Navigating
- Layer toggles — hide layers you're not thinking about (turn off Roles while reviewing the data model).
- Search box — jump to any node by name.
- Single-feature filter — narrow the map to one feature and everything it touches.
- Layout toggle — switch between horizontal and vertical flow.
- Mini-map — orient yourself on large graphs.
The detail panel
Click any node and a detail panel opens on the right:
- Plain-English summary of what the node is and does (LLM-narrated on Pro+, see below).
- Coverage health — how well this node is backed by acceptance criteria.
- Connected neighbours — everything one hop away, clickable.
- Acceptance-criteria tree (pages) — the criteria that will drive this page's implementation, including the empty/error/loading UI states bound during Prepare's spec-coverage step.
- Impact preview (pages, features, roles) — see below.
Coverage lens
Toggle the Coverage lens to overlay health rings on every node: green (fully covered by acceptance criteria), amber (partial), red (no coverage). It's the visual companion to the checks that run during Prepare for Development — a red ring here is the same gap the coverage preflight would flag.
Impact preview
For pages, features, and roles, the detail panel includes an impact preview: a deterministic walk of the foreign-key graph (no LLM) that answers "if this changes, what else is affected?" It lists the affected entities, distinguishes child records from dependent ones, and flags how hard the impact is. Use it before deciding to cut or rework something late in the spec.
Narration and the guided tour (Pro+)
On Pro and above, the map can explain itself:
- Narrate — generates a plain-English summary for each node (cached, so it's a one-time generation per spec state) plus a set of tour steps.
- Take the tour — steps you through the map node by node with a tour bar at the bottom of the screen (Back / Next), in a sensible reading order. Good for onboarding a teammate — or yourself, returning to a project after a few weeks.
💡 Tip: The narration is cached against the current spec state, so viewing the tour repeatedly is free — it only regenerates when your spec changes.
⚡ Power-user hints
- Use it as a review checklist. Turn on the Coverage lens, filter to one feature, and walk its pages — red rings are your to-do list before handoff.
- Impact preview before you cut. Late-stage scope changes are risky; the FK walk tells you the blast radius deterministically.
↔ The traditional way
An architect draws an ERD in one tool, a sitemap in another, and a roles matrix in a third — three artefacts that drift apart the moment the spec changes. The Blueprint Preview Map is all of them as one live graph, generated from the spec, so it's always current and it shows the connections between them (which role reaches which page reads which table) that separate diagrams never capture.
What's next
- Confirm you're ready → 10.1 Prepare for Development
- Where the entity nodes come from → 7.1 Generating schema
- Where the page nodes come from → 6.1 Generating pages
- Hand off to your coding agent → 11.1 Handoff overview