kami
f8fd2601a8
Health states are events. A HealthMonitor polls registered HealthProbes on an interval and appends HealthDegraded/HealthRestored only on a status transition (hysteresis), so health is observable, replayable, and renderable like every other fact in the log. The probe reads nondeterministic environment state and records it at observe-time (Invariant #9); HealthProjection rebuilds current health by replay, never re-probing (Invariant #8). Monitor is live-only, started in ServerModule.start alongside narration; seeded from the projection so a restart does not re-emit a degraded the log already records. First concrete probe: DiskWatermarkProbe — event-log + CAS size and growth rate, warning before the 2am surprise. Read surface mirrors `correx stats`: GET /health/checks replays the system session and `correx health` renders it. Health events ride the reserved __system__ session, filtered from operator session listings. LLAMA_SERVER (liveness + tokens/sec trend) and EVENT_STORE (append/fsync latency) probes plug into the same HealthProbe framework as follow-ups.