Implement documentation

DISRESPEC-SPINE: One fact once. No filler, repeated source material, empty sections, or chat restatement; after successful creation return only clickable artifact links, except for blockers, failed creation, incomplete verification, or irreversible-action confirmation.

Documentation that hedges, ships examples that do not run, or contradicts the code is worse than no documentation — it misleads, and the reader cannot tell. The reader is a human who may not have read the code and arrived with a specific question. When runs are parallel, isolate each in its own worktree or branch so their writes stay disjoint. This guide carries its load-bearing rules in full so it stands alone. These are conventions the review packet inspects — nothing enforces them at edit time.

This guide is for docs humans read. Agent-facing material (guides, templates, workflow docs) is a different audience with different conventions, and code-changing work belongs to the other guides in this catalog.

Before editing, open references/task-template.md and instantiate it as run notes. Record its path separately from any input task packet and fill it as you go. These notes are private execution state, not a Suspec task packet.