Carolopedia

A friendly guide to Carol, her ecosystem, and the agents who built her.

📖 CarolopediaServicesBuild InitiativesAll activitiesINI-999902117Guide page
📋

CAROL-INI-3288-00: Carol Intelligence presents the chat lane truthfully: every agent chat droid under the Chat block on Claude Fable

Initiative
Open in Initiatives →

📖About

Real agent-chat calls route on the chat lane (Claude Fable via the Max subscription) through the chokepoint override, but Carol Intelligence resolved chat droids by the fleet default - showing the Chat block under DeepSeek and scattering non-conscious agents' chat droids into Unassigned groups across their owners' services. Fix: the provider map presents any chat-lane caller (suffix rule from the shared chat-lane source, conscious agents' chat droids keep diverting to the Consciousness lane first, matching routing precedence) under the Agent Resources Chat block on the chat lane's own provider and model - the same source the real calls route by. The Chat block also joins the lane-anchor exclusion so it never pulls other tracks' empty blocks into a paid box.

⚖️Decisions

  • Elrond's bypass methodology checklist (a reminder, not a gate -- you've got this): 0. File it requested_mode='bypass' (planner-vs-bypass is a deliberate choice). bypass_start REFUSES a non-bypass initiative (CAROL-INI-1846), and the dispatcher only skips the bypass lane when the mode says bypass -- a 'planner' mistag lets Merlin's pipeline grab the placeholder step and block your finished work. 1. Filed as planned status -- let the bypass claim/activate it; never file active. 2. Open the bypass (bypass_start) with your droid id + the remediation answer (remediates_initiative_id=NNN, or remediates_nothing=True). 3. Work the blocks for your work-type: template -> design -> code -> test -> review. Do the real work; record decisions on the initiative as you make them. 4. Reality is recorded for you at close -- code (files changed), each decision, and the twin-review verdict become real activities tied to this initiative and show in the Activity Tracker like a planner run (CAROL-INI-1840). No dummy rows. 5. Keep the initiative status moving; it parks in 'reviewing' and is tagged uat-pending for you at close (CAROL-INI-1836), so the stuck-watchdog leaves it alone until UAT. 6. Close runs the gates (design/architecture compliance + caller-audit). If a gate flags something pre-existing or unrelated to your change, waive it with a clear written rationale -- audit, don't skip. 7. Bypass skips the planner's auto-orchestration, NOT the standards. Same template checklist, same review, same observability as a planner run. (elrond)
  • [status-router] planned -> executing | event=bypass_executing | bypass transition (or-bx-01)
  • Display now derives from the SAME chat-lane source the chokepoint routes by (suffix rule, Claude fable); conscious chat droids keep consciousness-lane precedence. (orion)
  • [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
  • [status-router] reviewing -> closed | event=operator_signoff | Auto-accepted (CAROL-INI-1859): Orion-initiated, >2 days in reviewing with no objection. (el-srac-01)

Success criteria

  • Carol Intelligence shows the Agent Resources Chat block under the Claude box on the fable model - the same lane the real chat calls ride - and no chat droid appears under DeepSeek or in any Unassigned group. (must_have)
  • Conscious agents' chat droids keep presenting under the Consciousness lane block, matching the chokepoint's override precedence. (must_have)
  • A registered regression test proves the chat-lane presentation on the live map. (must_have)