Carolopedia

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

📖 CarolopediaDroidsRSI Diagnosis LoopMain page
RSI Diagnosis Loop

RSI Diagnosis Loop

Droid Serialized improvement loop: every 5 min, moves the oldest blocked initiative to diagnosis, drives Albus root-cause + standard retrigger with recommendations
Go to droid →

📖About & Usage

About

The RSI Diagnosis Loop is a scheduled droid that keeps the improvement pipeline inside RSI Dashboard from stalling. Owned by Elrond, it exists to automatically spot and unblock initiatives that have gotten stuck, so the pipeline never grinds to a halt. Every five minutes it scans for blocked work, picks the oldest item, and puts it into a diagnosis state so it can be fixed rather than forgotten.

When an initiative enters diagnosis, the droid calls on Albus to perform a root-cause analysis—figuring out exactly why the initiative stopped progressing. It then applies a standard re-trigger enriched with Albus’s recommendations, clearing the way for the initiative to resume. The whole loop is serialized so only one initiative gets this attention at a time, preventing a noisy pile-up of unresolved problems.

This droid isn’t a one-off: it’s a reusable pattern from a family of (none) droids, with 187 other agents across the Carolverse running identical copies for their own initiatives. It calls Claude (opus) to power the intelligent reasoning behind the diagnosis and the re-trigger advice, while the rest of the loop runs as pure automation. You can follow its results in the RSI Dashboard dashboard and the Carol Initiatives tracker.

🛰️Updates

Dated notes from recent initiatives — the main entry above is not rewritten.

Fix2026-07-26

The RSI Diagnosis Loop now catches the StatusRouteError from Status Router when a target reaches the 10-diagnosis cap, abandoning the exhausted target reliably instead of crashing every minute.

Fix2026-07-25

The RSI Diagnosis Loop failed its last run on 2026-07-22. Hermione detected the failure and will re-trigger RSI Diagnosis Loop for remediation.

Fix2026-07-18

RSI Diagnosis Loop RSI Diagnosis Loop failed at 2026-07-14 18:26:02; detected by Hermione and queued for pipeline remediation and re-testing.

Fix2026-07-06

A blind spot in the RSI Diagnosis Loop was discovered: it heals blocks one at a time and missed 67 identical watchdog blocks, 53 operator-path blocks, and a gate failure mode. A new pattern-diagnosis droid has been deployed to catch such batch issues hourly.

Change2026-07-06

The RSI Diagnosis Loop now implements a leverage-first picker that groups blocked initiatives by shared root cause and diagnoses one cause to unblock multiple initiatives, targeting 150% leverage per diagnosis. See Carol Initiatives for the full directive.

👤Owner

Elrond · Head of Engineering

📚Recent initiatives

Initiatives that touched this droid — a short summary each; open one for the full story.

CAROL-INI-3170-00: Auto-detected failed process: RSI Diagnosis Loop (el-rsi-loop-01) · recurred 2×
Recurring operational incident, collapsed to one entry.
Hermione · 2026-07-25 20:25
Browse all initiatives →