All specification

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

LLM specRuntimeNotes
12 logical stages (B.4)11 runtime stagesSpec stages 1–2 combine into runtime research
Parallel stages 4 & 5 from 3Sequential assumptions then hmwRuntime runs both after problems; order is linear
Parallel stages 8 & 9 from 7Sequential content then uxRuntime runs both after stories; order is linear
ProblemAgent (stages 3–5)problems, assumptions, hmw subagentsLogical agent split across three eve subagents
GovernanceAgent (cross-cutting)Root orchestratorNot a declared subagent
PrototypeAgent (stage 12)Built-in agent toolDeclared prototype subagent exists but root uses built-in tool
B.2 Metadata / B.6 assertionsPartialEnforced via prompts and conversational gates; not yet full structured schema

Stage mapping

Spec stageSpec nameAgent (B.5)Runtime keySubagent / toolOutput
1Research AnalysisResearchAgentresearchresearch01-research.md
2Insight GenerationResearchAgentresearch (combined)research01-research.md
3Problem DefinitionProblemAgentproblemsproblems02-problems.md
4Assumption MappingProblemAgentassumptionsassumptions03-assumptions.md
5How Might WeProblemAgenthmwhmw04-hmw.md
6Hypothesis CreationHypothesisAgenthypotheseshypotheses05-hypotheses.md
7User Story GenerationStoryAgentstoriesstories06-stories.md
8UX ContentContentAgentcontentcontent07-content.md
9User JourneysJourneyAgentuxux08-ux.md
10UI PlanningDesignAgentuiui09-ui.md
11Design System MappingDesignSystemAgentdesignsystemdesignsystem10-designsystem.md
12Prototype GenerationPrototypeAgentprototypebuilt-in agent tooloutputs/<run-id>/prototype/

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 (assumptionshmw, contentux). Both branches still run; order is fixed for simplicity.

Agent registry mapping (B.5)

Spec agentStagesRuntime implementation
ResearchAgent1, 2agent/subagents/research/
ProblemAgent3, 4, 5problems/, assumptions/, hmw/
HypothesisAgent6agent/subagents/hypotheses/
StoryAgent7agent/subagents/stories/
ContentAgent8agent/subagents/content/
JourneyAgent9agent/subagents/ux/
DesignAgent10agent/subagents/ui/
DesignSystemAgent11agent/subagents/designsystem/
PrototypeAgent12Built-in agent tool
GovernanceAgentallRoot orchestrator

Governance implementation (B.3)

Spec capabilityRuntime location
State machine (draftreviewapproved / rejected)Conversational gate via ask_question; Markdown artefacts do not yet carry B.2 Metadata blocks
Approval before progressionagent/instructions.md — stage-gate rule
Audit trailMarkdown artefacts in outputs/<run-id>/ with evidence citations
Traceability (B.1)Subagent instructions require citing upstream artefacts and source quotes
GlobalRules (B.6)Enforced in prompts; future: validate in agent/lib/pipeline-artefact.ts

Code references

ConcernFile
LLM Operating Spec (canonical)spec/ucdops-agent-llm-spec-v1.0.md
Drop-in system prompt (Part A)spec/llm/08-system-prompt.md
Schema appendix (Part B)spec/llm/09-schema-appendix.md
Root orchestrator promptagent/instructions.md
Stage → filename mapagent/lib/outputs.ts
Artefact schemas and recoveryagent/lib/pipeline-artefact.ts
Subagent persistence hookagent/hooks/persist-subagent-artefacts.ts
Per-stage LLM promptsagent/subagents/*/instructions.md

Known deltas

  1. Structured metadata — B.2 Metadata and B.1 TraceabilityChain are normative in the LLM spec but not yet emitted as structured fields in runtime Markdown artefacts.
  2. Stage count — Public marketing avoids fixed skill counts; the LLM spec defines 12 logical stages; runtime executes 11 gated steps.
  3. Prototype path — Root instructions use the built-in agent tool, not the declared prototype subagent.
  4. Subagent sandboxes — Stages 1–10 use isolated sandboxes with hook-based persistence to the parent sandbox.
  5. Naming — Subagent keys differ from documentation and information slugs. See lib/documentation.ts and lib/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. *