Skip to content

LLM Resources

Maintenance โ€‹

Every conclusion here rests on hardware that degrades. An electrode calluses over, a soil probe corrodes, a serial link drops.

The failure that matters is not the loud one. A driver that throws gets caught and reported. The dangerous case is a component that keeps answering while being wrong โ€” a stuck humidity sensor reads 55% all week, the plant looks stable, the VPD calculation is confident, and every layer downstream reasons beautifully about a number that stopped being a measurement days ago.

stuck sensor โ†’ degraded

  mock [degraded]
     humidity: The last 28 readings are all exactly 55. A real measurement moves
     in its last digit even in a still room; this sensor has latched.

what to do about it:
  ยท Sensor "mock" is unreliable; readings from it should be treated as suspect.

suggested evidence weights: { "mock": 0.25 }
CheckedHow it is caught
Stuck sensorExact equality, repeated. A stable room still moves the last digit; a latched sensor does not
Impossible readingsValues outside what the metric can physically be
Flat electrodeLiving tissue is never electrically silent, so silence is the wire, not a calm plant
Mains humPower still at 50/60 Hz after filtering โ€” grounding, not physiology
Aliased samplingA rate at or below 2ร— mains folds the hum down into the plant's own band, wearing a plausible frequency
SaturationAn amplifier pinned at its rail reports numbers without measuring
Tiring contactReuses the continuity verdict rather than inventing a second opinion
Driver failuresConsecutive and proportional failure rates per driver
MemoryReadings out of chronological order break every window and trend computed from them
Colony linkNeighbours that were reachable and no longer are
BodySafety limits refused repeatedly โ€” the layer above keeps asking for what it cannot have

Nothing is quietly discarded. A component judged unreliable is marked unreliable, its suggested evidence weight drops, and the reason is stated โ€” because silently dropping a sensor is its own way of being wrong without saying so. Faults are filed as claims about the instrument (instrument_unreliable), so a conclusion can be discounted when the thing that produced it is broken.