ARAS Phase 1: ascending reticular activating system (global arousal gate)#123
Closed
TSchonleber wants to merge 1 commit into
Closed
ARAS Phase 1: ascending reticular activating system (global arousal gate)#123TSchonleber wants to merge 1 commit into
TSchonleber wants to merge 1 commit into
Conversation
…uation)
Brainstem-level global arousal broadcast. Sits ABOVE LC + NB —
ARAS gates whether the rest of the neuromod surface is responsive
at all. Anesthesia = ARAS shutdown; waking = ARAS ramp.
The May 15 brain_region_coverage.md audit flagged it on the 🟡
partial list: "neuromodulation_state table holds org-level
arousal/focus. Not wired into retrieval/admission."
Phase 1 is inspection-only / additive. No behavior change to LC,
NB, retrieval, or any existing subsystem.
- Migration 069 — 3 tables (aras_triggers, aras_state with
sleep_wake_mode + arousal_level + tonic_drive + phasic_alertness,
aras_transitions). Single-row aras_state seed. 5 seed trigger
classes (novel_query, high_pe_event, consolidation_complete,
idle_30min, explicit_user_alert).
- agentmemory.mcp_tools_aras — 5 MCP tools:
- aras_status: current state + last 5 transitions + 24h summary
- aras_transition: explicit mode change with soft-pull arousal update
- aras_drive: phasic arousal pulse via registered trigger;
auto-fires aras_transition on |delta|>=0.2 or phasic>=0.7
- aras_register_trigger: idempotent UPSERT on aras_triggers
- aras_history: paginated transitions with mode + agent filters
- 9 tests covering migration seeds, empty state, transitions,
invalid mode rejection, drive deltas, auto-transition logic,
unknown-trigger rejection, idempotent registration, history filters.
- Design proposal at docs/proposals/aras.md.
Phase 2 (separate PR) wires ARAS into the dispatch shadow consult to
log would-be mode transitions from event patterns. Phase 3 lets ARAS
modulate the downstream LC/NB response (low arousal damps LC phasic
firings; high arousal amplifies NB attention bursts). Phase 4 enforces.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced May 20, 2026
Owner
Author
|
Superseded by #138 ( |
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
1 participant
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.
Summary
Phase 1 of the ARAS subsystem — brainstem-level global arousal broadcast. Sits above LC + NB. The May 15
brain_region_coverage.mdaudit flagged it on the 🟡 partial list. Phase 1 is inspection-only.What's in
aras_triggers,aras_state,aras_transitions). Single-rowaras_stateseed. 5 trigger classes seeded.agentmemory.mcp_tools_aras— 5 MCP tools.docs/proposals/aras.md.What's NOT in
Live
~/agentmemory/backups/brain.db.pre-aras-20260520T044840Z.dbTest plan
docs/proposals/aras.md.pytest tests/test_mcp_tools_aras.py.🤖 Generated with Claude Code