method-rules-artifact-schemalisted

# Artifact frontmatter & evidence ledger schema Frontmatter is **phase-conditional**: artifacts with `phase: maintenance` follow the schema in the `method-rules-maintenance-rules` skill §9 instead of the block below. `phase: pipeline` (or no `phase` key) means exactly the rules below — nothing changes for pipeline artifacts. ## Frontmatter (required on every pipeline-phase `.md` artifact under `ideas/<slug>/`, except README and files under `private/`) ```yaml --- artifact: problem-hypothesis # kebab-case id, unique within the idea idea: <slug> stage: 0 # 0..6 gate: F # F | C | V1 | V2 | V3 | R1 | R2 | P | LOCK | BP status: draft # draft | ready | locked evidence_grade: none # highest grade backing this artifact: A | B | C | D | none rung: baseline-auto # enhanced-auto | baseline-auto | handoff (exactly three — see below) pipeline_version: 1.13.0 updated: YYYY-MM-DD --- ``` A PostToolUse hook validates these keys; missing frontmatter blocks with a fix instruction. `status: locked` is reserved for signed artifacts (kill-criteria, DoD, final positioning, mvp-spec) — a PreToolUse hook escalates edits to locked files. **`rung` has exactly three values** — `enhanced-auto | baseline-auto | handoff`. Two former values are gone by design (v1.2.0): - `handoff-only` was a synonym of `handoff` and added nothing over the capability's own `status: unavailable|unknown`. N