Implement documentation

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. This guide adds the documentation discipline on top of the base implement-task rules, carrying the Documentarian stance: the reader is a human who has not read the code, arrived with one question, and the doc answers it. 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 library.

Rules