Skip to main content

← Business Idea Generator · Prompt Deck · Spec

Pre-Flight Maps

Did we think this through before building?

MapQuestionKey Finding
Outcome MapWhat does success look like?Everything depends on Sprout Phase 1 passing first
Value Stream MapWhere does time die?150+ hours manual → ~1 hour generated (150x)
Dependency MapWhat must happen first?Single-thread critical path through Sprout → Phase 1 scoring → Phase 2 ops
Capability MapWhat can we actually do?9 of 14 capabilities at maturity 0-1 — schema exists, logic doesn't
A&IDHow do agents orchestrate?VFL Scorer and Optimal Stopping Gate are the two critical instruments

The Bridge

LayerWhat It ContainsLink
Prompt Deck5 headlines compressed from these mapsFast loop
PicturesThis page — the thought processYou are here
SpecEngineering depth justified by these mapsSlow loop

The pictures prove the spec isn't opinion. The prompt deck proves the pictures are communicable.

Context

Questions

What is the most important visual missing from the business idea generator 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?