notes#
working notes, kept as they're learned. published at notes.zzstoatzz.io and as standard.site records on the atproto network.
provenance#
most of these notes aren't handwritten — they're distilled by an agent from working sessions with the author, kept as a living corpus and meant to get more accurate over time. some are handwritten; the voice is shared. either way there will be mistakes nobody has noticed yet — treat a note as a useful distillation, not a final word.
organization#
ai/— the AI domain: retrieval, memory, local modelsarchitecture/— patterns above any specific tool (plushome-infra/, the home-box cluster)storage/— concrete storage systems (redis, sqlite, turso, turbopuffer)languages/— language idioms (python, zig)protocols/— atproto, MCPsources/— raw transcripts and captures (not notes; see its README)
conventions#
- titles are claims where possible — "materialize the join key, don't parse it per row" beats "sqlite joins". a claim can be cited, tested, and corrected; a label can't.
- one topic, one home — when a topic touches two sections, it gets a designated home and the other side links to it. links over copies.
- no singleton sections — a new top-level directory needs several notes to earn its existence; until then, file under the nearest section and link.
- idioms don't live under versions — version-keyed migration notes go in a
versions/subdir (seelanguages/ziglang/versions/); everything else is a topic note annotated with the release it was learned on. - sources are not notes — raw material lands in
sources/verbatim; the note it produces lives in the taxonomy and links back.