The Body as the Platform — Sleep, Energy, Recovery

Establish the physiological infrastructure all cognitive discipline depends on. Audit your sleep, light exposure, exercise, and recovery patterns against current circadian science — including the honest, critique-aware reading of the popular sleep canon. Implement and defend three non-negotiables: a consistent sleep window, a daily anchor of physical activity, and recovery scaffolding around whatever your timezone-overlap or on-call pattern is. Walk away with a written physiological operating contract you will re-read in M11 when shipping pressure tempts you to break it. The body is your production environment. You wouldn't deploy to a server you haven't monitored, with unknown specs and no observability — and most engineers spend more rigor on their staging environment than on the cognitive substrate they run all their work on. The Operating Contract is the production config: defaults, alerts, scaling rules. Skipping it is shipping to a server you forgot to provision. Recovery is garbage collection. A long-running process that never GCs accumulates memory pressure and crashes; a long-running cognitive worker who never recovers accumulates allostatic load (Sapolsky's term for the cost of sustained stress activation) and crashes in less legible ways — irritability, low-grade symptoms, rereading the same Slack message four times. The Loehr/Schwartz oscillation principle is a GC schedule for the human worker; the discipline is to trigger collection before it's forced. And circadian misalignment is technical debt. It accumulates whether you feel it or not. The late-call working pattern is not zero-cost — it has a debt-service charge paid in next-day capacity, regardless of how alert you felt on the call. You can take on the debt; sometimes the trade is worth it. The contract's job is to make you price it in explicitly instead of pretending it's free.