How did we arrive at this proposal — and how do we track that value is delivered?
| Map | Question | Key Finding |
|---|---|---|
| Outcome Map | What does success look like? | 7 binary measures. Platform serves all instances. Self-referential: it orchestrates its own engineering. |
| Value Stream Map | Where does time die? | 4.3% flow efficiency — 130min work in 1-4 days. Dispatch wait and context recovery are #1 and #2 bottlenecks. |
| Dependency Map | What must happen first? | 1 hard dep (auth), 8 soft. All P1 gaps have soft deps only — start immediately. 4.5 day critical path. |
| Capability Map | What can we actually do? | 33 capabilities: 48% at zero, 15% ad-hoc, 36% built. 79% Core. Heavy build ratio — expected for a platform. |
| A&ID | How do agents orchestrate? | 6 agents, 8 instruments, 5 loops, 3 channels. 7-phase activation, each transfers a bottleneck from human to platform. |
Templates: docs/pictures/templates/
The Bridge
Pictures sit between sales and engineering. The prompt deck sells the vision. These five maps prove the thinking is sound.
| Prompt Deck (sells) | Pictures (explains) |
|---|---|
| "One platform, every agent" | Outcome: 7 binary measures, one platform serving all instances |
| "Ten minutes lost each session" | Value Stream: 4.3% flow efficiency, 130min in 1-4 days |
| "Everything built, nothing unified" | Capability: 33 capabilities, 48% at zero, 36% built |
| "CLI today, protocol tomorrow" | Dependency: 1 hard dep, 8 soft, 4.5 day critical path |
| "Agents coordinate by merging code" | A&ID: 6 agents, 8 instruments, 5 loops, 3 channels |
Context
- Agent Platform PRD — Decision surface
- Prompt Deck — Sales: five cards, scannable
- Pictures Templates — Empty patterns to fill