Pre-Flight Maps: Work Charts & Workflow Builder
These five maps prove the thinking for the visual orchestration layer spanning the Workflow Engine and WorkChart processes.
- Outcome Map — What does success look like?
- Value Stream Map — Where does time die?
- Dependency Map — What must happen first?
- Capability Map — What can we actually do?
- Agent & Instrument Diagram — How do agents orchestrate?
Key Discovery
The backend WorkChart capability and the Workflow Engine are ~80% complete, but structurally inaccessible without the Workflow Builder instrument. The core bottleneck is engineering delay. The visual interface resolves this by mapping 1:1 with engine components, shifting the paradigm from static Notion documentation into self-executing AI logic pipelines.
Context
- PRD Index — Work Charts & Workflow Builder
- Prompt Deck — 5-card pitch
- Spec — Engineering depth
Questions
What is the most important visual missing from the workflow and process mgt picture set — and why does it matter?
- Which relationship between elements in this diagram is most underspecified — and what would happen if it were wrong?
- If this picture were shown to a new engineer on day one, what would they misunderstand — and how should the picture be changed?
- What assumption does this visual make that should be made explicit in the spec?