Odin had no AGENTS.md, no CLAUDE.md and no notes/ or state/, so every session started cold in the repo whose deployment is the least routine in the estate. AGENTS.md carries what is specific to Odin rather than repeating estate doctrine: that the host is authoritative, that a local compile says nothing about the Linux release, that /etc/machine-id must be mounted or identity tests fail in a way that looks like broken code, and the two listing traps that have each misled a reading -- an alphabetically truncated unit list, and odin.service being active while owning no process. notes/odin-deployment-handoff-2026-09-10.md records why Odin currently cycles and why the two obvious interventions fail: an engaged lifecycle brake parks a continuity transaction on the target and blocks deployment, which the operator doctrine says it must not; and freeze_one_queued_command only runs when continuity made no progress, so a queued deployment is starved on exactly the unstable target it exists to repair. Both defects are named with the state that proves them rather than left as a description of a bad night. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
69 B
69 B
Repository doctrine for this project lives in AGENTS.md.
@AGENTS.md