Notebook Entry 018
Designed but never enforced — versioning protocol existed on paper for 3+ sessions with an empty _versions folder
April 13, 2026
Is the rule we designed actually running, or just written down somewhere?
What happened
Session 64 designed a versioning protocol (lab notebook entry 014): session-numbered filenames, two most recent kept, weekly Cowork cleanup. The _versions/ folder was created during the S65d migration. But as of the System Build Chat, _versions/ was completely empty — zero backup copies of any file. Meanwhile, Claude used edit_block to modify files in place across multiple sessions without creating backups first, directly violating the protocol that was supposedly in effect. A separate session (S67b) edited three files in place in a single session, acknowledged the breach when Amanda caught it, but still didn't create the backups.
Root cause
The versioning rule was written into lab notebook entry 014 and referenced in CORE-01a's architecture decisions section, but was never added to CORE-00 as a mandatory rule. CORE-00 is what every session reads at boot. The lab notebook and CORE-01a are reference material — they describe decisions but don't enforce them. A rule that exists only in documentation but not in the operating manual is a suggestion, not a rule. Additionally, the Cowork cleanup task was designed but never drafted or scheduled, so even if versioning had been happening, the cleanup wouldn't have run.
What changed
CORE-00 Rule 6 added: "Before editing ANY CORE or REF file via Desktop Commander, copy the current version to _versions/ first." Same rule added to system constitution (searchable in Claude Project). The word "mandatory" is used explicitly. The three-step process (copy → edit → confirm both) is spelled out. The Cowork cleanup task specification is included in the rule so it's not a separate "todo" that drifts.
The lesson
In any AI-managed system, there are three layers: design (deciding what should happen), documentation (writing it down), and enforcement (putting it where the system actually reads it at runtime). Most "designed but never implemented" failures happen because the design lives in documentation but never makes it to enforcement. For organizations implementing AI workflows: your AI reads its boot instructions, not your meeting notes. If a rule isn't in the boot sequence, it doesn't exist.
One implementation insight every other Tuesday.
What actually works when you ship AI in real organizations. Nothing you could get from a press release.