Per-run artifacts

Each Lamina run lives under .lamina/runs/<run_id>/. run.json is the source of truth; readable files are generated or evidence-oriented views.

Directory layout


.lamina/runs/<run_id>/
├── run.json          # Canonical Contract v2 graph
├── run.md            # Generated readable graph
├── implement.md      # Generated ready-to-build contract
├── report.md         # Verification narrative
├── fix.md            # Evidence-backed fix brief
└── walkthrough/      # Optional live-product evidence

`run.json`

The graph records intent, classified decisions, actors, entity lifecycles, operations, workflows, invariants, dependencies, surfaces, distinct risk scenarios, persona findings, traceability, verification findings, and evidence. See the Contract v2 schema.

Generated views

run.md explains the active graph to a human.
implement.md is emitted only at ready_to_build; it excludes deferred nodes and preserves typed acceptance references.
report.md explains verification evidence and remaining uncertainty.
fix.md turns open findings into product, contract, or operational fixes with acceptance criteria.

Edit run.json, validate it, and render again. Do not hand-edit generated views into a competing contract.

Status lifecycle

Status	Meaning
`draft`	Graph is being shaped
`needs_input`	A consequential product decision blocks readiness
`ready_to_build`	Critical promises are traced and the implementation view exists
`verifying`	The live product is being checked against the frozen graph
`complete`	Verification artifacts are written; findings may still require fixes

Validation


node <lamina-orchestrator>/lib/graph-tool.mjs validate .lamina/runs/<run_id>/run.json
node <lamina-orchestrator>/lib/graph-tool.mjs render .lamina/runs/<run_id>/run.json

See Global artifacts for business-context.md, personas.json, and cross-run decisions.