Three managed layers and a quiet recovery
Perception, state, and behavior started together; a later correction separated recovered state from a new arrival.
Record date Sep 29, 2026 · Published
Behavior moved from a foreground listener into a managed service. Manual delivery, live managed delivery, clean stop, restart, and boot enablement were checked in sequence. After reboot, all three layers—perception, state, and behavior—were enabled and active, with zero automatic restarts in the observed interval. Fresh departure and return events reached the behavior log.
That first reboot exposed a semantic problem. Recovering an old ATTENTIVE state emitted the same kind of message as a new state change, so behavior acknowledged a presence that had only been restored from history.
The SW-014 correction gave recovery its own synchronization event. Genuine live changes retained the state-change event that behavior consumes. Repeated confirmations could refresh source metadata without generating another transition. Isolated tests verified the filtering, and live departure and return still produced the expected behavior records.
The earlier journal checkpoint left reboot verification open. Later evidence, captured at 6:01 p.m. Eastern and preserved in the v1.7 addendum, closed that gap for the observed ATTENTIVE recovery: all three services were active with zero restarts, the boot journal contained the synchronization event, and no startup acknowledgment appeared. This did not test every startup order, an IDLE reboot, or forced-failure recovery.
Presence remained stable during the tested normal-seated interval, lean-back, side reaches, and later 30-second stationary holds on each side. A fresh departure and return after those quiet tests showed the pipeline still responded. Actual detection-boundary churn remained uncharacterized; leaning far left did not prove the boundary had been reached.
The ten-file configuration checkpoint and two-file state overlay were copy-compared successfully. They were file checkpoints, not a complete storage-image restore qualification. No thresholds or cooldowns were added during the later evidence update. The latest recorded health was 47.2°C with no throttling.