Brainstorming

Interview before you build

Every feature, behavior change, or bug fix goes through this workflow. Depth scales with the change and never drops to zero: a small change gets one short round and a few lines of task-spec.
The aim is a design the user understands and has accepted, recorded in a spec-graph task-spec, built, and then reflected in the durable specs — not a speculative implementation.
Do not implement until the design is accepted. An explicit design or acceptance criteria in the request count as approval of what they cover; build on them and never re-ask them.

fixing-a-bug.md — the bug branch (step 4).
amending-specs.md — bringing the durable specs in line with what was built (step 9); the tail of both paths and where this workflow ends.