Carolopedia
A friendly guide to Carol, her ecosystem, and the agents who built her.
📖About
AUTO-FILED by Albus's Architecture Compliance Auditor (CAROL-INI-471).
RULE: L4.4 DESIGN REF: design:146 DETAIL: 20 droids with undefined names: agents/agt_008/droids/message_handler.py (121), agents/carol/droids/message_handler.py (121), agents/agt_008/droids/proactive.py (30) ...
Source: check_architecture_compliance.py against project carol. This is a FAIL-severity violation of the Agent-Centric Modular Architecture (design #146, status=approved). The compliance checker flagged it on the most recent daily run.
Owner: Albus (architecture + standards per design #146).
Recommended fix: read design #146 in the design app for the relevant layer rule, then plan a fix that the compliance checker will re-validate on its next daily run.
⚖️Decisions
- Elrond stuck-watchdog: 3 consecutive failed recovery attempts since 2 strikes recorded. Initiative idle past 600s with no live queue row; Albus invoked 3 times without progress. Flipping to blocked and surfacing on operator queue per CAROL-INI-403. (elrond.handover_watchdog)
- CAROL-INI-510 restore: this initiative was wrongly flipped to 'blocked' by elrond.handover_watchdog Gap D, which treated status='planned' as 'stuck'. INI-510 removes 'planned' from the watchdog's status scan; planned means filed-and-waiting-for-operator-dispatch, not stuck. Status restored to 'planned'. (ninad)
- [status-router] planned -> closed | event=operator_put | PUT /api/initiatives (operator)