Version. 0.1 Date. 2026-07-31 Author. Claude.ai (drafting session). Operator: Marvin Percival. Status. Standing. Applies to every versioned document a session executes from. Occasion. Identified by the executing session at the filing of CR-2026-159 v0.4, which was the first bump in that CR's series to change how the build runs rather than how the document reads.
The record's filing discipline is siblings, never overwrites: a revised document is filed under the next version and the prior version stands untouched. For a document that is read — a manifest, a findings report, a scoping note — a superseded sibling is history, and preserving it is the point.
**For a document that is executed, a superseded sibling is not history. It is a live instruction set that no longer matches the decision.**
CR-2026-159 is the worked case. Versions v0.1 through v0.3 differ from each other only in prose. v0.4 changed behaviour: it removed an Operator confirmation gate at Checkpoint A that the charter had already made unnecessary. A session opening v0.1, v0.2 or v0.3 by filename would halt for a gate that no longer exists, wait for an Operator who has not been asked for anything, and report a checkpoint the current decision does not contain.
The hazard is self-propagating. Each version carries a kickoff block naming its own path, so a session that starts from a stale sibling is told by that sibling that it has the right document.
Before executing any versioned document, confirm it is the highest version present in the record. One directory listing. If it is not, stop and open the highest.
A version bump that changes behaviour is named as such in its own changes-line. The distinction between reads differently and runs differently is the one an executing session needs, and only the drafting session knows it at the time of writing. CR-2026-159 v0.4 states it explicitly; v0.2 and v0.3 state the opposite, that nothing about the work changed.
The kickoff block names a version, never a bare document. A kickoff that says "execute the CR" inherits whichever file the session happens to open.
Nothing is edited retroactively. Superseded versions stay exactly as filed. The record's precedent for supersession is a marker in the new version — as the manifest does for its superseded entries — not an edit to the old one. This note follows that.
Ordinary archival is unaffected. The versioned-document archival discipline governs how superseded documents are kept. This note governs only the moment before execution, and only for documents that are executed.
The charter is F-4 — its own amendments are Operator acts. This is a working discipline that sits under it, not a change to its authorization classes, so it files as a standing note. If the Operator wants it in the charter proper, that is his to decide at cadence; it is recorded here as a queue-free candidate rather than a decision entry, because nothing is blocked either way.
DUNIN7 — Done In Seven LLC — Miami, Florida Loomworks — standing note — superseded versions of executable documents — v0.1 — 2026-07-31 A document that is read has history. A document that is executed has only a current version.