Pre-Flight Maps
Classification: Platform. Required maps: Outcome, Dependency.
Outcome Map
What observable state changes prove this PRD succeeded?
| Outcome | Measure | Baseline | Target | Timeline |
|---|---|---|---|---|
| North Stars queryable | Count of Active PRDs with Queryable: Yes | 0/7 | 7/7 | 30 days |
| Full cycles completed | PRDs completing pain → proof → marketing in one month | 0 | ≥1/month | 60 days |
| Return signal wired | PRDs with actual_metric_value in frontmatter | 0 | ≥1 | 45 days |
| Morning reports generated | Sessions producing structured experiment logs | 0 | ≥1/week | 30 days |
Dependency Map
What must exist before each feature can work?
metric-definer ──────────────────────────────┐
│ │
▼ ▼
measure-north-star.ts engineering-handoff Gate 8
│ (fails if Queryable: No)
▼
outcome-validator (reads scalar)
│
▼
proof-to-story upgrade ──► score-prds upgrade
│ │
▼ ▼
session-experiment-logger (proven demand compounds)
│
▼
loop-orchestrator (chains all of the above)
| Feature | Depends On | Blocking |
|---|---|---|
| LOOP-001 metric-definer | Nothing | LOOP-002, Gate 8 upgrade |
| LOOP-002 measure-north-star.ts | LOOP-001 metric definitions | LOOP-005 |
| LOOP-003 proof-to-story upgrade | Nothing | score-prds upgrade |
| LOOP-004 session-experiment-logger | Comms CLI | LOOP-005 |
| LOOP-005 loop-orchestrator | LOOP-001, LOOP-002, LOOP-003, LOOP-004 | First loop execution |
Context
- PRD Index — Autoresearch Loop
- Prompt Deck — 5-card pitch
- Spec — Engineering depth
Questions
What's the minimum viable loop — the smallest set of wires that produces one full cycle?
- Can LOOP-001 + LOOP-003 deliver value without the full orchestrator (LOOP-005)?
- Is the Sales CRM metric (
won_deals / total_deals > 0.30) the right first target, or should we start with a simpler metric?