Version. 0.1
Date. 2026-05-24
Author. Marvin Percival (DUNIN7), via Claude Code
Effective. Immediately. Supersedes the prior Downloads-then-record two-step for record-bound documents.
Documents that have discovery-record value land in the record automatically as part of producing them, not as a separate later step.
Markdown is the working source format. HTML is the Operator's reading form. Every document that lands in the record has both — the .md for editability and trajectory, the .html for the letterpress reading experience.
Going forward, CC produces documents directly into /Users/dunin7/loomworks-record/<section>/<subsection if applicable>/. CC commits, pushes, and Cloudflare Pages handles deploy. The Operator reads from record.dunin7.com. There is no Downloads intermediate for documents that are heading to the record anyway.
The prior discipline staged documents at /Users/dunin7/Downloads/ first, then a separate kickoff landed them in the record. The two-step served a purpose while the record's structure was still being established — it let the Operator inspect documents in an editor of choice before commit. With the record's structure now mature (sections settled, build tooling established, Cloudflare Pages deploying reliably), the two-step is friction without proportional benefit.
The transit zone collapses. CC writes directly to the record path, commits, pushes. The Operator reads at the public URL.
Kickoffs implicitly include "land in the record" unless they explicitly say otherwise. CC does not need to ask "should this go to Downloads or to the record?" — the default is the record. If a kickoff says "stage at Downloads only" (rare cases), CC respects that explicit instruction.
Corrections happen against record-resident documents. When the Operator surfaces a correction, v0.2 lands alongside v0.1 in the record per the discovery-trajectory discipline. The trajectory of corrections is itself the discovery record; it does not collapse to "latest version only."
Letterpress HTML companion is part of producing the document, not a follow-up ask. Every record-bound document ships with its .html companion in the same commit.
Filenames follow the existing kebab-case + version convention. loomworks-<topic>-v0_N.md or phase-XX-<topic>-v0_N.md for phase-aligned work. Subsections under sections (e.g., substrate/cleanup/) when the section grows topical.
The following stay at /Users/dunin7/Downloads/ (or wherever they currently live):
Downloads stops being a staging area for record-bound documents. That is the specific change.
The discipline note lives in the record so the discipline is persisted alongside everything else it governs. Future CC sessions read the discipline from the record (not from a CLAUDE.md or a one-off note) and apply it. If the discipline evolves, v0.2 lands here and the trajectory is preserved.
This is also the first concrete artifact produced under the new discipline — the discipline note about producing directly to the record was itself produced directly to the record.
DUNIN7 — Done In Seven LLC — Miami, Florida Record Production Discipline — v0.1 — 2026-05-24