Repository navigation
feat(behavior): a calm pet β lively after contact, still otherwise - #78
Merged
Merged
Conversation
Field: the dog never settled. Idle head turns, sniffs and stretches every few seconds, every noise an investigation, the servos warm, the family unnerved. - The engine is lively only BEHAVIOR_AWAKE_S (120) after contact: a voice input, a touch, a command or /behavior/start. Otherwise it sends nothing that moves, lights or speaks, and the daemon's sleep takes over. - BEHAVIOR_QUIET_HOURS (22-7): no autonomous motion at all; direct commands still work. - Sounds habituate (HoundMind pattern): 20 s cooldown, and four sounds within a minute are ignored for five minutes. - The face check runs only while awake (camera and CPU rest too). - An explicit patrol and the battery alarms pass. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The bridge fell back to nox_autonomous_v2 when the engine failed to start β without awake window or quiet hours. A still dog is the safe failure now. An explicit patrol passing awake window and quiet hours is intended and now documented. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Field report: the dog never came to rest. It kept moving, the servos got warm, and the family found it unsettling. It was supposed to be Nox's body, not something that stands around drawing power.
Cause: The behavior engine sent idle actions all the time, and its commands are
_internal, so they do not reset the daemon's sleep timer, yet they still move the servos. Every sound triggered a head turn plus INVESTIGATE. REST fell back to IDLE after 120 s.Change (patterns from Reachy Mini, HoundMind and the Jibo/Vector lessons):
BEHAVIOR_AWAKE_S(120 s) after contact. Contact means voice (/voice/input), a touch, a command (/action,/combo,/move) or/behavior/start. Outside that window the wrapper blocks every move, head, scan, rgb and speak command, and the FSM sits in REST.BEHAVIOR_QUIET_HOURS(default22-7) stops all autonomous movement. Direct commands still work._urgent), always go through.Not included: actually switching the servo PWM off in the daemon's deep sleep. Today that is only a flag. It needs a test on the hardware.
π€ Generated with Claude Code