thurview design

A design document says what should be built and why, argued against the code as it stands. It is the third thurview document kind, beside a review of a change and an explainer of a codebase, and it is read in the same browser surface: anchored code peeks, a map, threads, revisions, and a decision that is Approve the design or Send it back.

thurview is evidence-anchored, so the whole kind turns on one rule. Read Anchors and proposals before you write anything. The short version:

An anchor is evidence, never a proposal. Every anchor in a design document resolves to real code at the one pinned commit — what the design changes, and what constrains it. Code the design would write is declared as a proposal, and a proposal names the site: the anchor of the code it lands in, replaces or plugs into today.