The New Medium — Framework Map

Zone 1 — The Four Entry Points

01

Investigate

Understand an unfamiliar codebase, audit your own work, or run formal PE due diligence. Output lands in docs/ENGAGEMENTS/.

02

Build

Execute epics against a plan. Orchestrator coordinates agents: Builder → Reviewer → Debug. Output lands in docs/FEATURES/.

03

Refactor

Post-audit modernization. Read the coordination layer, execute epic by epic, update contracts as you go.

04

Boardroom

Strategic debates on hard decisions. Select a bench of advisors, facilitate a structured session, record the outcome.

Zone 2 — Shared Infrastructure

Shared Infrastructure — The same layer powers every workflow

MCP Tools (37)

run-epic
create-signal
list-epics
generate-contract
probe-org
get-workflow
+ 31 more

docs/ Layer

EPICS
FEATURES
ENGAGEMENTS
SIGNALS
OPPORTUNITIES
BACKLOG
PRODUCT_SOT

Templates

base
scripts
supabase
engagement
boardroom
installed via `core --preset`

Zone 3 — How They Connect

Investigate → Build

Investigation findings become signals. Signals become backlog items. Backlog promotes to epics. Epics execute in Build.

Build → Signal Loop

Work surfaces observations. Observations become signals in real time. Patterns synthesize into opportunities. Opportunities inform the next epic.

Investigate → Refactor

Audit Sprint produces the coordination layer. Refactor reads that layer to execute modernization in the right sequence.

Zone 4 — The Document Architecture

Layer 1 — Planning Artifacts (ephemeral)

Contents

EPICS/
PRD.md
ARCHITECTURE.md

Snapshots of intent. Time-ordered. Not updated when code changes.

Layer 2 — Living Artifacts (always current)

Contents

PRODUCT_SOT.md
FEATURES/
ENGAGEMENTS/

Reflect what the system actually does now. Updated after each epic closes.