How it runs

1. Progressive business interview
2. Generating Business Map
3. Building Bow-Tie Funnel
4. Scoring 24 Digital Assets
5. Creating Implementation Plan

Why it matters

• 26× faster
• Gets smarter each session
• No re-interviewing

What it needs

• client-id — Client folder name under
• business-type — Business archetype for inference patterns (auto-detected if omitted)
• profile — Company or client profile — identity and stage.
• icp — ICP — target customer the strategy is for.
• offerings — Offerings catalogue — what is being strategised.
• marketing-context — Positioning, narrative, and competitive frame.
• process — Process name to expand (e.g. 'Lead Gen', 'Onboarding', 'Fulfillment')
• process-note — Path to the `type: process` source note (client or company scope)
• orientation — Layout direction (default horizontal, unchanged behavior). horizontal = lanes are rows, steps flow left→right. vertical = lanes are columns with a top label, steps flow top→bottom — use for LONG processes (e.g. 16 steps) that run off the right edge horizontally; the canvas gets tall (expected). Two-way arrow binding holds identically in both. Vertical writes a distinct {process-id}-swimlane-vertical.excalidraw.md so it never clobbers the horizontal diagram.
• no-archive — Skip archiving an existing diagram before regeneration (default false — archive first)
• no-bands — Suppress stage bands (default false). When steps carry a `stage:` field and orientation is vertical, consecutive same-stage steps are grouped into labelled full-width bands behind the lanes; --no-bands renders the plain sequence. Bands are vertical-only — horizontal ignores stage regardless.
• business-type — One of the 15 archetype slugs (auto-detected from baseline if a session exists)
• scope — 'company' (default — this vault's own business) or a client-id for a client-scoped registry

What you get

• (Action Roadmap page)
• (client scope, horizontal) or (company scope, horizontal); vertical orientation appends -vertical before the extension ({process-id}-swimlane-vertical.excalidraw.md)
• (company scope) or (client scope)
• (new page)
• Each swimlane migrated into a structured `type: process` note — the source of truth (drawio-only baselines liberated into queryable data)
• Excalidraw swimlane rendered from the process note — derived view, not the source of truth; prior version archived to diagrams/_archive/. Horizontal and vertical are separate files that can coexist for the same process.
• Optional swimlane render of the process note
• Optional visual export rendered from the process notes — not the source of truth
• Registry with domain tables + Value-Chain Mapping section, same contract as the company registry (parsed by list_value_chains.py and consumed by owner-priority-system kpi_refresh.py/kpi_verify.py)
• Source-of-truth process note with steps[], owners, state, and opportunity flags
• Structured `type: process` note(s) — the source of truth (steps, owners, state, flags)
• continued_baseline (drawio)
• roadmap_page (drawio-page)
• scan_summary (markdown)
• session_state (yaml)

Ask it like this

• Run a business baseline on my operations" · "Map my business and identify bottlenecks" · "Create a bow-tie funnel for my SaaS product" · "Give me an Excalidraw swimlane I can drag around