Follow an initiative's journey
Selecting a row on the Flow board opens its journey: not a summary of the work, but the lineage, assembled from real links. This page follows Offline maps for saved trips, which is at building.
The header
Section titled “The header”The title, the project it belongs to, the meeting it was tracked from, and the stage it has reached. Both links are live: the meeting link is how you get from a shipped feature back to the conversation that asked for it.
The rail
Section titled “The rail”Six stations, in order, each one either done, current, or upcoming. A station that is not upcoming shows what is actually behind it:
| Station | What it lists |
|---|---|
| captured | The objectives from the meeting, and the counts of requirements, decisions, risks, and open questions, with a link into the meeting |
| planned | What was accepted from the meeting’s drafts |
| building | Each task with its status, linked to its workspace, and how many runs it has had |
| verifying | The checks that scored the work, passed and failed |
| shipped | Reached when every task that was not cancelled is done |
| marketing | Assets published from this work, with their channel |
Where lineage genuinely does not exist, the station says so rather than guessing. verifying on an initiative nothing has scored reads “No checks have run against this work yet”, which is a true statement about the work and not a rendering failure.
Waiting on, and unattributed
Section titled “Waiting on, and unattributed”Under the header, two lines worth reading:
Waiting on repeats the blockers from the board, in full. On the offline-maps journey that is the blocking question still open from the check-in.
Shared with this meeting, not yet attributed appears when a meeting produced items, tasks, or drafts that no initiative has claimed. They are counted openly rather than quietly assigned to the nearest thread, so the trail stays honest about what it does and does not cover.
The proposed next step
Section titled “The proposed next step”A journey that is between stations proposes the single most useful handoff, with the reason it is proposing it:
| Stage | What it proposes |
|---|---|
| captured | Draft a plan from the captured intent |
| planned | Dispatch the plan to a build agent |
| shipped, nothing verified | Verify the shipped work against its acceptance criteria |
| shipped and verified | Create launch content to market the shipped work |
Propose this step does not perform it. It raises the step as an approval, so the decision stays yours, and re-proposing an already-proposed step says so rather than queuing a second copy. Stages with work under way (building, verifying) and finished ones (marketing) propose nothing, because the useful move there is to wait.
Gate receipts
Section titled “Gate receipts”At the foot of the journey, every gate decision that has been taken on it: what was proposed, which stage it moved from and to, who decided it, and whether it was approved or denied.
That is the audit trail in the place you would look for it. An initiative that advanced can be asked who let it.
Next steps
Section titled “Next steps”- Work the approvals queue: where a proposed step is decided.
- Read the Flow board: every journey at once.
- Runs and attempts: what the building station is counting.