Reliability · INTERNAL SYSTEM
Session Lifecycle Ledger
A disposition record for every AI session — because nothing gets killed without first being written down.
LIVE
INTERNAL
Ledger
SYSTEM NOTEThe problem it solves
When dozens of AI sessions run across several machines, something has to reclaim the dead ones. The naive reaper is worse than the leak: it looks at CPU, decides a session is idle, and kills a human's live work mid-thought.
PROCESS RAILHow it works
[01]
Register
every session enters the ledger
[02]
Signal
several independent liveness signals
[03]
Judge
reap only when all of them are cold
[04]
Tombstone
state recorded before anything is killed
[05]
Recover
the record can rebuild what was lost
SYSTEM NOTEUnder the hood
- A human reading and thinking draws almost no CPU — so CPU alone can never prove death, only activity can prove life.
- Shared signals prove life but never death: a quiet terminal is not an empty one.
- The reaper fails closed. If it cannot establish state, it does nothing.
- Lifecycle events are immutable, which makes post-mortems possible instead of speculative.
FIELD NOTEWhy it matters
Reclaiming resources is easy. Reclaiming them without ever destroying live work is the actual engineering problem.