📖About

RSI diagnosis (CAROL-INI-2223b/2246): Albus root-causes WHY CAROL-INI-2164-01 (row 999900575, 'CAROL-INI-2164-01: Move all BB initiatives from Carol to BB initiative system') blocked and records recommendations on the original so its retriggered attempt succeeds. This is a PIPELINE-FIXING initiative: any fix it implements to the pipeline MUST adhere to the cookbook (checked automatically per fix during the Albus bypass, verdicts recorded as decisions).

GROUP EVIDENCE (CAROL-INI-2311 leverage diagnosis): 38 blocked initiatives share routed cause 'stuck_10min_no_activity'. Root-cause the SHARED mechanism, not just this representative — your recommendations will be applied to every member on retrigger. Members: [999900575, 999900593, 999900649, 999900651, 999900661, 999900582, 999900641, 999900650, 999900653, 999900669, 999900709, 999900579, 999900587, 999900638, 999900676, 999900697, 999900609, 999900731, 999900739, 999900621, 999900637, 999900743, 999900675, 999900748, 999900749, 999900751, 999900752, 999900741, 999900758, 999900759, 999900755, 999900757, 999900765, 999900772, 999900766, 999900779, 999900782, 999900787]

⚖️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)
• Remediates INI-999900575: Orion bypass opened to remediate this blocked/closed parent. — CAROL-INI-696 linkage: this bypass is the operator-driven remediation of a previously-blocked-or-closed initiative. target_initiative_id set on this row; canonical Orion remediated: row will land on the parent at bypass_end. (shared.bypass.bypass_start)
• [status-router] executing -> closed | event=operator_put | PUT /api/initiatives (operator)
• Closed: superseded by follow-on INI 999900868 (RSI diagnosis and pipeline fix for CAROL-INI-2164-01 (INI 999900575): CAROL-INI-2164-01: Move all BB initiatives from Carol to BB) (elrond.initiative_author)

✅Success criteria

• The original initiative carries an 'Albus RSI diagnosis (root cause)' decision explaining why it blocked (must_have)
• The original initiative carries an 'Albus RSI recommendations' decision with concrete instructions for the next attempt (must_have)
• Every pipeline fix implemented by this initiative passes the automatic cookbook-adherence check (verdict recorded as a decision), keeping the pipeline cookbook-compliant while enabling CAROL-INI-2164-01 to succeed on retrigger (must_have)