docslisted

# docs — author & review documents The DB owns document bodies: a `documents` row is the source — NEVER author a loose `.md` file as the canonical body. `sc render` writes the read-only flat copy to `specs_sc/` / `docs_sc/`; the GUI opens it rendered in md-converter. | kind | lives on | meaning | |---|---|---| | `spec` | the **Roadmap** (the dev cycle) | working spec for a feature; a feature can hold several at once; **freezes on ship** | | `doc` | the **Docs** tab | documentation; not part of the spec lifecycle | `<self>` = your shell_id. ## One feature, many specs Feature = the `roadmap` row; exists from `brainstorm` onward, before any spec. Specs hang off the feature, not off each other: several unfrozen specs per feature, each a `documents (kind='spec')` row, ordered by `seq`. No feature-to-feature links; no second roadmap row for related work — related work = another spec under the same feature. Freeze = the ship-time record of what was built to; it never gates the feature's other specs. | state | test | meaning | |---|---|---| | **shipped** | `frozen = 1` | delivered; immutable record | | **active** | unfrozen + has rows in `spec_tasks` | the spec being built now | | **backlog** | unfrozen, no task plan | the pile, ordered by `seq` | The **doc** (`kind='doc'`) = the feature's readable face — write it when the first spec ships, under the same `feature_id`. Sibling of the specs, not a parent. ## Assess the work-stream on every feature A feature attaches to a work