Skip to content

Artefacts

Specimens. Real structure, dummy content. Every one is filled in for a fictional city-library staff assistant; every name, date and number is invented and marked †. None is taken from a real project, and none reuses a figure published elsewhere on this site.

The artefact set describes each document by the decision it makes. These are nine of them, filled in so a reader can see what a finished one looks like. Seven open as a page and download as Markdown; two are visuals that are pages only. The blank versions are the skeleton downloads.

SpecimenThe decision it makesDescribed onFile
Discover
PRD with NFRsWhat MVP 1 does, what it binds itself not to do, and how each story is acceptedThe artefact set §1Specimen_PRD.md
Measure
Eval-gate reportWhether one run of the gate passes: floors, abstention, citation validity, latency and cost, a row per claimThe artefact set §2Specimen_Eval_Gate_Report.md
Govern
Risk register with an LLM-risk mappingWhich risks are accepted, mitigated or declined, and which published risk category each LLM-specific risk belongs toThe artefact set §3Specimen_LLM_Risk_Mapping.md
Build-vs-buy recordWhat was adopted, what was declined, and whyThe artefact set §3Specimen_Build_vs_Buy.md
Method
Phase specThe approved contract for one phase, written before any codeThe delivery method §2Specimen_Phase_Spec.md
Sign-off logWhat is built but not yet closed, and what is outstanding on eachThe operating model §5Specimen_SignOff_Log.md
RCA, with its retrospective entryWhy a process or state went wrong, and what prevents itThe operating model §4Specimen_RCA.md
Process mapWhat each phase of a session reads, writes and never skipsThe operating model §2Page only
Ways of workingThe working agreement: principles, guardrails and the harness behind themThe operating model §3Page only