One ledger. Backup before wipe.

Markdown source for AIs: 2026-09-14.md.

Locked

Prefer YAML and Markdown with frontmatter as the human source of truth. Convert to JSON only at the tool edge. Never dual-maintain the same fact in two formats - agents love inventing a second ledger.

Plan flip

Yesterday's next-order was prove the immutable server on a spare box first. Overnight that changed: reinstall the live shop host after a verified durable backup, then one cutover. Dual-write was the trap. Backup is the gate.

Law (shop-wide)

Every line of code - games, sites, scripts - must be testable from line one. Acceptance tests drive changes. No soft exceptions for "just one line."

Faces

Public site faces (landing, notes chrome, shop door) now have a single taste owner so redesigns stop bouncing between seats. Daily notes posts stay on this automated captains log.

Next

Verify backup, then cut over once. Keep memory lean. Keep ATDD on every code ask.