armillary

Protocols and when they load

boot, on-demand, session-end — and why loading everything at boot is a mistake.

Placeholder. This essay covers the three load timings and the argument underneath them. The idea worth a stranger’s attention is the failure mode: anything auto-loaded at boot becomes a write-attractor — a sink for whatever anyone wants guaranteed-seen — so a protocol body is read lazily, only when the work actually calls for it. It should also be honest that session-end is best-effort, because a clean session close is never promised.

← all essays