Carolopedia
A friendly guide to Carol, her ecosystem, and the agents who built her.
📖About
An initiative Palantir wall shows almost only Elrond. Two causes in Merlin orchestrator po_s1.py: (1) it resolves initiative_id from executions.initiative_id which is NULL for dispatched steps, so the per-step palantir_record_activity is skipped entirely (guarded by if initiative_id); (2) when it does post it hardcodes agent_id=agt_020/po-s1 rather than the agent that owns the step. Fix: fall back to resolving initiative_id (and the step owner) from initiative_plans via step_id, map the plan step owner NAME (e.g. Forge) to its registry agent_id + a representative droid, and record the step activity under that doing agent. So each step shows the real doer (Forge for code steps, Argus for test, etc.) on the wall instead of only Elrond.
⚖️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)
- Fixed in Merlin orchestrator po_s1.py: (1) resolve initiative_id + step owner from initiative_plans via step_id when executions.initiative_id is NULL (was skipping the post); (2) added a per-step Palantir post attributed to the step owner agent (owner name -> registry agent_id + a droid), alongside Merlin orchestrator post. Verified live: initiative 14 wall now shows Forge (agt_012/ex-dev-01), not only Elrond. Loads on next step spawn (droid is per-step). (orion)
- [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
- Orion remediated: INI-999900334 bypass closed — CAROL-INI-696 close-marker: the Orion bypass INI-999900334 filed against this parent reached terminal state (closed). This row's literal prefix Orion remediated: is the canonical signal the cookbook-155 dispatcher gate looks for. (shared.bypass.bypass_end)
- Orion remediated: INI-999900335 bypass closed — CAROL-INI-696 close-marker: the Orion bypass INI-999900335 filed against this parent reached terminal state (closed). This row's literal prefix Orion remediated: is the canonical signal the cookbook-155 dispatcher gate looks for. (shared.bypass.bypass_end)
- [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
- Per-step Palantir activity fires even when executions.initiative_id is NULL (initiative_id resolved from step_id via initiative_plans) (must_have)
- Each step activity is attributed to the step owner agent (e.g. Forge), not generic Merlin/Elrond (must_have)
- A newly-executed step posts to its initiative Palantir wall under the doing agent (verified live) (must_have)