Module specifications (PRDs)

The product requirements each module was built from: the problem, the user stories, the decisions made while specifying it, and what was left out. The code has moved on since some of them were written; where they disagree, the code and the ADRs win.

Module	Specification
M0	PRD — M0 "Who you study": describe the people, see who exists
M1	PRD — M1 schemas: the engine's contracts
M2	PRD — M2 brief: intake
M3	PRD — M3 population: who is in the study
M3.5	PRD — M3.5 corpus: what is actually in there, and what a field's value is worth
M4	PRD — M4 inference: every model call, recorded as what it was
M5	PRD — M5 elicitation: what a persona said, as a rating distribution
M6	PRD — M6 agent: one persona's reaction to what it was shown
M7	PRD — M7 world: environments, and who sees what
M8	PRD — M8 runner: running a study to completion inside a budget
M9	PRD — M9 trace: the append-only record and the questions that can be asked of it
M10	PRD — M10 analysis: deriving meaning from a trace
M11	PRD — M11 report: turning findings into documents
M12	PRD — M12 cli: the way in
M13	PRD — M13 web and M14 ui: the engine with a face on it
M15	PRD — M15 Channels and survey waves: information spreads the ways a study chooses, and intent is tracked
Optimization	PRD — Finished-world trace reuse
Optimization	PRD — Batched agent embeddings