Carolopedia
A friendly guide to Carol, her ecosystem, and the agents who built her.
📖 Carolopedia › Services › Build Initiatives › All activities › INI-999902689Guide page
📋
📖About
Ninad 2026-08-10: switch consciousness on but wake ONLY Albus, Elrond and Clara. The wake loops roster enumerates every agent_self row and IGNORES the mind droids status — pausing a Mind droid (the sanctioned lifecycle mechanism) would not stop its wake, and a missing droid row is even synthesised. Fix: the roster includes only minds whose registered droid is status=running AND enabled; a paused mind is SKIPPED and the run summary says how many slept. Then pause 36 minds, keep Albus/Elrond/Clara running, switch the track on, and watch the first tick.
⚖️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)
- [delivery-check] 4 pending must-have criteria stamped met at bypass_end on live re-performance evidence (CAROL-INI-3020): test test_ini3769.py: PASS (4 passed in 0.34s) (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
- The wake roster excludes minds whose droid is paused/disabled and never synthesises a droid for them; the run summary counts sleeping minds (must_have)
- 36 minds paused via the lifecycle mechanism; Albus, Elrond, Clara running; consciousness track switched on (must_have)
- A live heartbeat run wakes exactly the 3 running minds (must_have)
- Regression: paused mind excluded from roster, running minds included, no synthetic droid for a paused mind (must_have)