Three reference files, each stating whether a fact was measured, read from source, or asserted — an unattributed number is a rumour. math-on-the-web: MathML is the only no-JS route, the one pure-Go TeX→MathML library is an untagged 2023 commit, and writing MathML directly costs nothing since raw HTML renders. syntax-highlighting-choices: chroma is two modules and ~5MB, every alternative a search returns is JavaScript, and custom lexers load from XML at runtime without a rebuild. goldmark-behaviours: the seven surprises that caused or nearly caused defects — strikethrough claiming a single tilde, delimiter runs pairing across whitespace, per-parse heading id counters, footnote id prefixes, raw HTML being dropped rather than escaped, the language class already in the output, and ParseFS globbing.
Reference — facts worth keeping
Durable information surfaced in conversation that would otherwise be lost: measured numbers, external constraints, how a tool actually behaves, links worth having. One file per subject.
Not decisions (docs/decisions.md), not proposals (ideas/), not the present state of the code
(docs/state.md). A fact only true today belongs in state.md; a rule belongs in the doc owning the
topic.
Each file states how the fact was established — measured, read from a spec, or asserted — so a later reader knows whether to trust it or re-check it. An unattributed number is a rumour.
Scratch code illustrating a fact is welcome; verify.sh ignores .go here entirely, so it need not
compile.
Out of agent context by default, this index included. Opened only when the human names the topic.
Index
- agent-session-costs.md — how context and token cost accumulate in an agent session
- math-on-the-web.md — rendering maths with no JavaScript, and the state of Go TeX→MathML
- syntax-highlighting-choices.md — chroma's cost, what it gives, and why there is no lighter option
- goldmark-behaviours.md — the goldmark surprises that caused or nearly caused defects