Every 90 seconds
It heals.
A supervisor checks services, the model server, memory, disk, temperature, the network, the screen, its own configuration files and the indexes it builds from your memories and conversations. When a check confirms a fault, one of fifteen repairs may run.
Each repair is limited: no more than three restarts of one service in half an hour, no more than two rollbacks a day on any one thing, and no automatic retry for six hours after a rollback. Beyond the fifteen it only does housekeeping, like trimming logs when the disk runs low.
7 of the 15
It repairs, with an undo.
The seven repairs that touch files or indexes run as a transaction: snapshot, stage, check, apply, check again live. The change is kept only if every check passes.
If not, it puts back exactly what was there, checks that too, and leaves a notice in your Journal on the screen. Your own words are never rewritten from an index; the index is rebuilt from them.
Cause, not symptom
It looks for the cause.
It can tell when a fault is the cause and when it is a consequence of something else, or say honestly that it cannot tell. A repair aimed at a symptom is withheld when the evidence says the cause is elsewhere.
When it can't answer a question about its own health, it can propose what evidence would settle it.
Learns on your unit
It keeps score, and rehearses.
Every incident and every repair outcome is recorded. Where it has a choice of fixes, it prefers what has worked on your unit. On quiet days, once it has proved its own safe window, it breaks something built to be broken and watches the real repair path handle it.
It only ever chooses among fixes it was already allowed to make, and every unit starts with a blank record.