/qstack-plan-to-html

Takes a plan, from a Markdown draft or from the conversation that worked it out, 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: