Dependency Map

What must exist before the generator can prove the platform?

Dependency Graph

[Schema Migration 0048] ════ [Generator Templates] ════ [Safe Nx Runner]
         ✅                          ✅                        ✅
                    ↓
              [RUN GENERATOR]  ← Phase 1, Step 1.6 (BLOCKED)
                    ↓
              [ACCEPTANCE TEST]
                    ↓
         ──── [Domain Tables] ──── [Feature Scaffold]
                Phase 2                 Phase 2
                    ↓
         ──── [Real A2A Execute] ──── [Access Control]
                Phase 3                 Phase 3
                    ↓
              [SECOND SPROUT]
                Phase 4 (Platform Proof)

Legend: ════ hard (cannot proceed), ──── soft (can mock)

Dependencies by Phase

Phase 1 — Generator + First Sprout

Dependency	Type	Status	Owner	Blocker?
Schema migration 0048	Hard	Done	Engineering	No
Generator templates	Hard	Done	Engineering	No
Safe Nx runner	Hard	Done	Engineering	No
Acceptance test script	Hard	Done	Engineering	No
Codex environment	Soft	Blocked (crash)	Infrastructure	Yes — resume manually

Phase 2 — Domain Entities

Dependency	Type	Status	Owner	Blocker?
Phase 1 complete	Hard	Blocked	—	Yes
Domain table definitions (spots, reports, catches)	Hard	Not started	Engineering	No — design decision only
Feature scaffold generator	Soft	Exists	Engineering	No — but untested with ventureId

Phase 3 — Execution Layer

Dependency	Type	Status	Owner	Blocker?
Phase 2 complete	Hard	Blocked	—	Yes
A2A execute implementation	Hard	Stub only	Engineering	Yes
Venture access control design	Soft	Not started	Nav + Engineering	No

Phase 4 — Platform Proof

Dependency	Type	Status	Owner	Blocker?
Phase 1 complete for first venture	Hard	Blocked	—	Yes
Second venture selected	Soft	prettymint or howzus	Nav	No

Critical Path

Migration (✅) → Generator (✅) → First Run (BLOCKED) → Acceptance → Domain Tables → Feature Scaffold → Real A2A → Second Sprout

Current blocker: Step 1.6 — running the generator. Everything else is downstream.

Parallelization

Can Run in Parallel	Dependency
Domain table design (Phase 2.1)	Only needs Phase 1 acceptance, not Phase 1 complete
Access control design (Phase 3.2)	Can design while Phase 2 builds
Second venture selection (Phase 4)	Can decide while Phase 1-2 execute

Key Finding

The critical path is a single thread: run the generator, then everything cascades. The only blocker is the codex crash that prevented Step 1.6. All hard dependencies before that point are resolved.

Context

Outcome Map — What we're unblocking
Value Stream Map — Why unblocking matters (435x improvement)
Capability Map — Maturity of each dependency

Dependency Graph​

Dependencies by Phase​

Phase 1 — Generator + First Sprout​

Phase 2 — Domain Entities​

Phase 3 — Execution Layer​

Phase 4 — Platform Proof​

Critical Path​

Parallelization​

Key Finding​

Context​