Flow view mockup

A flow is the path through an app's pages, top to bottom, drawn from the links between them. Each step shows what it touches. Real data: onboarding a Conductor project. P-1360

← back to where you came from · the flow remembers it (a Focus, a feature, a page)

Onboarding for Conductor projects

show on each step: features & behaviours classes thoughts tickets

Thoughts › Focus: flows

Entry 1 · the Focus brain. A Brain | Flow switch on the brain pane. Flow replaces the brain in place: same Focus, same notes on the right. Picking a flow is remembered with the Focus, so it opens on the flow next time. Tap a step: its page opens on the right (Notes one tap away; + note on this page starts a thought tagged with it), and + to Focus adds the step as a member.

Focus: flows

flow:

tap a step to see its page here

razie-158 a flow is a diagram: the flow of elements and associated things…
razie-159 flow navigation: enter from different spots, remember where from…
Step: tap a step on the left

Features › onboard

Entry 2 · a feature's page. A Flows section lists every flow that passes through a page carrying one of this feature's behaviours. Its steps that do are highlighted. Open → goes to the flow and remembers this feature, so ← back returns here.

onboard · Onboarding a project

^onboard-11The last step makes the dashboard home
^onboard-12Setup is the home until the dashboard step
^onboard-13Will other people work here?
^onboard-14…16Start your agents: one link per role, Copy, New link, live dot

Flows

Open → Onboarding for Conductor projects · 10 steps · 3 touch this feature
Open → Onboarding for Pro projects · not drawn in this mockup
Landing→Pro landing→…→Ready to prototype→Start your agents→Dashboard

Open points for the review

  1. Name clash. /flows is already the rule engine's flow list (a Toolbox tile). My pick: call these Journeys at /journeys. Or keep Flows and rename the engine page Runs.
  2. Where a flow starts and ends. Since a flow comes from page links, someone names its first and last page, and d2 walks the links between them. My pick: a flow is a line in the feature's Spec section, flow: Onboarding for Conductor = App:Landing → Page:DashboardMaster, so it has no topic of its own.
  3. Which links count. Links in a page's body, buttons and home-button blocks count. Help, Toolbox and the menu don't count, or every page would link to every page. Side pages (doors A and B, Plan) show beside the step they return to.
  4. Behaviours per step. A step shows a behaviour when its page's topic names the code (^ui-doors-1) or the Spec line names the page. Classes come from the Spec section's domain.
  5. Thoughts and tickets per step. These are open thoughts and not-done tickets that link the page or one of its behaviour codes. Parked tickets show greyed.
  6. More entry points, later. A page topic (In flows), a ticket (its step in the flow) and the Dashboard (a Flows tile).