Implementation Mapping
This document maps the (12 logical stages, Part B contracts) to the current eve-based runtime in this repository (11 stage-gated execution steps).
For the high-level public specification, see .
Summary
Stage mapping
Research stages 1–2
The LLM spec keeps Research Analysis (what is in the evidence) and Insight Generation (what it means) as separate governed steps. The runtime research subagent produces both in one artefact (01-research.md). The public site merges them into a single "Research synthesis" skill — do not assert a fixed skill count in user-facing copy.
Parallel branches (spec vs runtime)
The LLM spec defines:
- Stages 4 and 5 as parallel branches from Stage 3 (
requires_approved: [3]) - Stages 8 and 9 as parallel branches from Stage 7 (
requires_approved: [7])
The runtime executes these as sequential gated steps (assumptions → hmw, content → ux). Both branches still run; order is fixed for simplicity.
Agent registry mapping (B.5)
Governance implementation (B.3)
Code references
Known deltas
- Structured metadata — B.2
Metadataand B.1TraceabilityChainare normative in the LLM spec but not yet emitted as structured fields in runtime Markdown artefacts. - Stage count — Public marketing avoids fixed skill counts; the LLM spec defines 12 logical stages; runtime executes 11 gated steps.
- Prototype path — Root instructions use the built-in
agenttool, not the declaredprototypesubagent. - Subagent sandboxes — Stages 1–10 use isolated sandboxes with hook-based persistence to the parent sandbox.
- Naming — Subagent keys differ from documentation and information slugs. See
lib/documentation.tsandlib/information.ts.
Stage count policy
The skill set grows over time. Public surfaces present a curated subset under phase names (Discovery, Definition, Delivery, Prototype) and must not assert a fixed total skill count. When changing the pipeline, update the LLM spec, this mapping, agent/instructions.md, and affected subagent instructions together.
*