Perception, state, and behavior recover together
Three managed services passed observed startup checks, with recovered state separated from a fresh arrival.
Record date Sep 29, 2026 · Published
RC-01’s three software layers reached a useful checkpoint: perception detected presence changes, state represented them as ATTENTIVE or IDLE, and behavior selected the corresponding acknowledgment or return-to-idle event.
The first three-service reboot passed autonomous startup and fresh live delivery, but exposed an unwanted acknowledgment caused by replayed state. The following correction separated synchronization from live change.
Later boot evidence verified the corrected ATTENTIVE recovery: all three services were active with zero recorded restarts, synchronization appeared in the journal, and no startup behavior acknowledgment appeared. Subsequent departure and return still produced behavior events.
This milestone is about service startup, state recovery, and software event delivery. It does not claim an IDLE-state reboot test, exhaustive failure recovery, speech, animation, or physical actuation.