qstack-plan-to-html

# /qstack-plan-to-html Takes a markdown plan and produces a controlled document: numbered, citable, offline-safe, and readable by two audiences at once. A plan is **not a landing page**. It opens with a title block, every clause is numbered so a reviewer can say "§4.2 is wrong", and every section carries a status stamp so a reader knows what is settled before reading a word. ## Language: plain words, always **Write it the way you would say it out loud.** Jargon is not precision; most of the time it is precision's opposite, because it lets a vague sentence pass as an informed one. If a sentence would survive being read aloud to a smart person outside the team, keep it. If it would not, rewrite it. Cut these on sight: they carry no information: > leverage · utilize · synergy · holistic · robust · seamless · paradigm · > best-in-class · surface area (as a metaphor) · first-class citizen · > orthogonal · non-trivial · trivially · simply · just · obviously | Instead of | Write | | --- | --- | | "leverage the existing abstraction" | "use the code that is already there" | | "a non-trivial refactor" | "about three days of work across four files" | | "the system exhibits sub-optimal latency characteristics" | "it takes 40 seconds; it should take 2" | | "we surface this to the operator" | "the operator sees it" | | "simply add a policy rule" | "add a policy rule": if it were simple you would not be writing a plan | **Precise is not the same as jargon.** A term of art that names...