Reference
Reference
The operational truth — folders, files, fields, config, states. The handbook makes the argument; this is where you look things up. Every page is single-sourced fromthe canon and links back up to the handbook chapter that explains the why.
The
docs/ layout →Every directory: what's here, how to write it, what does not belong.
The spec folder →
Every file in a spec folder, and when it's present.
Frontmatter fields →
Four identity keys, plus the experimental unattended envelope. Meaning, values, when set.
Repo configuration →
Per-repo config:
specline.yml — the canon pin, the unattended switch, thresholds, models.Spec body sections →
Intent, Goal, Behavior, Acceptance… what each section holds.
Lifecycle & states →
State is location — the four folders and the moves between them.
Acceptance altitudes (experimental) →
provable / judgeable / tasteable — the unattended refinement of one acceptance list.
The boundaries →
Three writing rules and the record rule that define the methodology.
Glossary →
One-line definitions. The fast way in.
▸
Two scopes of config, two homes. Frontmatter is per-spec, set at the decider's go (that's where the experimental loop_budget lives). specline.yml is per-repo, set once. They are not the same file.