What this screen does
Backlog reads everything the locked specification defines and shows it as items with links: every role, journey and branch path, every functional requirement, every screen, every table, every generated test, and every coverage gap the journeys generator reported. Click any item and its card shows what it links to; every link opens the next card, so you can walk from a persona to a screen to a table to the test that proves it. Reading the graph, following links and confirming what is right cost nothing, and so do the edits and decisions you type onto a card. Credits are spent only where a model runs: Ask, and an Apply that carries change requests — one Refine pass.
Typical workflow
- Open Backlog from the Specification page. The Explorer on the left lists every item; click one and its card fills the screen. Click a card inside a view and it opens beside the view instead — switch that to a popup with the Panel / Popup control; your choice is remembered.
- Use Traceability first: each requirement with the journeys that exercise it, the screens and tables it touches and the tests that prove it. Amber cells are gaps.
- Read Queries for the questions worth asking a spec: requirements no journey exercises, screens no journey reaches, tables no screen maintains, journeys with no error path.
- Review journey by journey on the Board: Confirm what is right, Request change where it is not, Ask the project agent about anything. A change request joins the project's change set and is applied with it (see below).
- Backlog shows the same journeys as epics, stories and tasks with acceptance criteria. Markdown exports it for your tracker.
- When a preview is deployed, cards show the demo sign-in for their role so you can walk the journey as that person.
Proposing changes
Everything you want changed goes into the project's change set — one per specification version, shared by everyone. On any card, Propose edit changes a field yourself (applied exactly as typed, no AI), Request change describes what should change in words, Record a decision writes down what was decided. Cards with a proposal move to Proposed on the Board. The change-set badge in the toolbar opens the list: everyone sees every proposal, each author can remove their own, and the owner and approvers can remove anyone's.
Apply is the one step that creates the next specification version: edits are written to the spec and the journeys document, change requests run a single Refine pass (charged to the project's credits), decisions are recorded and shipped with the bundle documents, and History names every proposer. Edits, decisions and Apply itself cost nothing.
On plans with change-set review, the owner names approvers on the Members page. Editors and approvers propose and can Submit for review; the owner and approvers apply. Without it, the owner applies the draft directly.
Examples & tips
- Personas is the role-by-role summary; the role card behind it carries the full lists.
- A confirmation is on content: when a later refine rewrites a journey, its card comes back marked "confirmed earlier, changed since".
- History compares any earlier journeys document with the current one, by journey.
- The Flat view is the User Journeys document as a page, for reading top to bottom. Free plans see this view only.
- Use the role chips in the toolbar to filter every view to one role.