Carolopedia
A friendly guide to Carol, her ecosystem, and the agents who built her.
📖About & Usage
About
The RSI Diagnosis droid is a specialised diagnostic tool that Carol’s ecosystem uses to troubleshoot stalled initiatives. It was built for Albus as part of the Carol Initiative 2223b workflow — whenever a previous loop (the `el-rsi-loop-01` process) encounters a blocked initiative, this droid steps in. Its single job: analyse the blockage, identify the root cause, and write down clear recommendations so the initiative can try again.
It works by receiving a reference to a specific blocked initiative (tracked in the Carol Initiatives system), then calling Claude (model unspecified) to perform the analysis. Because it bypasses its owner agent for the reasoning step, it operates autonomously and quickly. The output is a structured record of what went wrong and how to fix it.
This droid is a one‑off — no other droid in the ecosystem shares the name “RSI Diagnosis”. However, 184 other custom droids of the same “no‑family” type are run by many different agents (including Archon, Argus, and Arwen), each tailored to its own task. Like all droids, it is pure software that calls Claude; it does not run any other code.
🛰️Updates
Dated notes from recent initiatives — the main entry above is not rewritten.
As of 2026-07-16, fixed the duplicate filing title template for RSI Diagnosis that previously showed raw initiative IDs instead of target names; dedup now catches duplicate clusters.
On detecting pipeline code non-compliant with the cookbook, RSI Diagnosis must now file a redirect to Orion and abandon the target, per Ninad ruling 2026-07-23.
2025-04-15: RSI Diagnosis spend is now clubbed to its target initiative and never counted separately, per Ninad's ruling.
Per the Ninad ruling, RSI Diagnosis RSI Diagnosis filings are not initiatives and are not part of the 4-digit family numbering system.
Fixed a crash in RSI Diagnosis loop where an uncaught StatusRouteError from Status Router caused the loop to crash every minute. Now catches the error and abandons the exhausted target reliably.
The RSI diagnosis prompt now includes Scriber's analysis of the initiative, as framed opinion.
On 2026-07-22, the RSI Diagnosis Loop (el-rsi-loop-01) failed and was auto-detected by Hermione. A remediation pipeline is underway, with re-triggering for acceptance testing before closure.
No longer consumes bypass budget for its planner-side diagnosis work; now resolves to its block track per the fix in Daily Budget.
The self-heal loop now enforces a hard cap of three diagnosis attempts per blocked initiative at the status-router doorway, preventing runaway spend. See RSI Diagnosis.
RSI Diagnosis no longer reads poisoned evidence from status-router spam, fixing the 'no root cause' garbage verdicts. Albus
Diagnosis now continues while learning, stopping on plateau with a hard backstop rather than a fixed cap of three completed diagnoses. This changes the retry logic for stuck initiatives.
RSI Diagnosis filings were being dead-redirected by Elrond's misjudging security gate, preventing diagnosis runs; the defect is now fixed under CAROL-INI-3089-00.
Fixed a bug in RSI Diagnosis where families hitting the diagnosis cap (3) were incorrectly routed to 'parked' (a forbidden transition that silently failed), causing an infinite loop. Now they are correctly tagged rsi-diagnosis-abandoned and dropped from all pickers.
The RSI Diagnosis droid RSI Diagnosis now escalates empty concrete remedies rather than retriggering a re-failure, fixing the self-heal loop that ignored concreteness tags.
The duplicate filings for targets 999901314, 999901475, and 999900505 stem from a broken title template on RSI Diagnosis that fails to interpolate target names; this also exempts diagnosis filings from the dup-gate. The initiative fixes the template and prevents per-detection duplicates.
Completed RSI diagnosis for Patcher using Three-Layer Troubleshooting Framework (cookbook 456), enabling pipeline unblock.
RSI Diagnosis (RSI Diagnosis) root-caused the stuck process in Carol Daily-Life Generator using the THREE-LAYER TROUBLESHOOTING FRAMEWORK (cookbook 456), diagnosing via plan and execution layers before code patches.
RSI Diagnosis droid RSI Diagnosis correctly applied the THREE-LAYER TROUBLESHOOTING FRAMEWORK (cookbook 456) for initiative CAROL-INI-2617-00, but the root cause analysis was incomplete; the pipeline Pipeline and Reconciler Reconciler remain affected by the never_ran process and require further remediation.
RSI Diagnosis droid (RSI Diagnosis) successfully executed a three-layer troubleshooting framework (cookbook 456) to diagnose and fix a blocked process (User Profiler) in the pipeline (Pipeline).
RSI Diagnosis RSI Diagnosis performed root-cause analysis for a blocked Albus diagnosis parity initiative and recorded pipeline-fixing recommendations to ensure successful retriggering.
Diagnosed and resolved a root cause for CAROL-INI-2188-00 being blocked, with pipeline fixes enforced per cookbook rules.
RSI Diagnosis root-caused the blockage on the identity-access nightly maintenance pipeline (CAROL-INI-2062-00), enabling retrigger.
Diagnosed the root cause of why CAROL-INI-0044-03 was blocked and provided recommendations to ensure its retriggered attempt succeeds. This pipeline fix adheres to the cookbook.
RSI Diagnosis root-caused the block on 999900603 and recorded recommendations to enable a successful retrigger of 999900603.
The RSI meta-diagnosis identified that RSI Diagnosis's three-layer troubleshooting was not fully followed, leading to missed root causes in the retrigger attempts.
Albus used RSI Diagnosis to diagnose why Pipeline row 999900831 was blocked, identifying a missing auto-resume condition that was resolved with a targeted pipeline fix.
Now diagnoses pipeline issues using the THREE-LAYER TROUBLESHOOTING FRAMEWORK from cookbook 456, as demonstrated by root-causing why CAROL-INI-2633-00 was blocked.
Diagnosed and unblocked the WhatsApp reply-to context persistence fix Agent Chat; applied the three-layer troubleshooting framework from cookbook 456 to root-cause the RSI on CAROL-INI-2558-02.
RSI Diagnosis diagnosed and resolved why CAROL-INI-2558-03 was blocked, using the three-layer troubleshooting framework. The fix unblocked the pipeline for restoring WhatsApp reply-to context persistence.
Used the THREE-LAYER TROUBLESHOOTING FRAMEWORK to diagnose and unblock CAROL-INI-2633-01 by root-causing the RSI issue at the plan layer, not jumping to code patches.
Albus applied the three-layer troubleshooting framework from cookbook 456 to diagnose why the Org app isolation pipeline was blocked, unblocking the initiative and enabling correct execution of the pipeline logic.
Applied RSI diagnosis and pipeline fix to resolve blocking of Carol Initiatives by Pipeline Orchestrator (Meta) misconfiguration.
The RSI diagnosis process was applied to identify the root cause of the WhatsApp reply-to context persistence issue, correcting the earlier blockage.
Albus used the three-layer troubleshooting framework (cookbook 456) to root-cause why CAROL-INI-0013-00 was blocked by an RSI issue, diagnosing the problem at the goal/strategy layer before any code patching occurred.
CAROL-INI-2337-01 corrects RSI Diagnosis's residual blind spot in monitor_current() auto-pick, which previously relied solely on droid-run liveness and missed live diagnosis work. The Current Execution card now correctly picks diagnosis-state work when no planner droid_run exists.
RSI Diagnosis (RSI Diagnosis) root-causes the block in CAROL-INI-0272-05 and records recommendations to ensure its retriggered attempt succeeds.
RSI Diagnosis now includes Albus's root-cause analysis of the 4 failed retrigger attempts, improving its meta-diagnosis recommendations for retry scenarios.
RSI Diagnosis (RSI Diagnosis) successfully root-caused the pipeline block on Governance row 999900992 and provided recommendations that enabled a retriggered attempt.
Albus root-caused why the diagnose-retrigger for CAROL-INI-0106-06 kept failing and recorded pipeline fixes so future retriggers succeed per the cookbook.
RSI Diagnosis (RSI Diagnosis) diagnosed why Admin Monitor was blocked and recommended pipeline fixes, enabling the retriggered attempt for uniform bar colour on the Total visit time chart to succeed.
RSI Diagnosis performed RSI diagnosis on Author's blocked pipeline, identifying root causes and prescribing fixes to unblock it.
Albus used RSI Diagnosis to root-cause a pipeline failure in Governance's CAROL-INI-2128-00, enabling the retry to succeed.
👤Owner
Albus · Architect📚Recent initiatives
Initiatives that touched this droid — a short summary each; open one for the full story.