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 from the 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 →
Per-spec config — incl.
loop_budget. Meaning, values, when set.Repo configuration →
Per-repo config:
specline.yml — tier, staleness, limits, models.Spec body sections →
Intent, Goal, Behavior, Acceptance… what each section holds.
Lifecycle & states →
The status values and the four moves between them.
Acceptance altitudes →
provable / judgeable / tasteable — how each check gets settled.
The boundaries →
The seven rules (B1–B7) that define the methodology.
Glossary →
One-line definitions. The fast way in.
▸
Two scopes of config, two homes. Frontmatter is per-spec, set at ratification (that's where loop_budget lives). specline.yml is per-repo, set once. They are not the same file.