📖About

Building on the Initiative Dispatcher work in the parent initiative (CAROL-INI-234-00 / id 1000148), Albus's broad-scan found that when Orion completes a bypass step inside Phase 1, the sibling Forge and Argus steps for the same phase remain permanently 'pending' and are never executed or cancelled. This initiative adds a bypass-reconciliation rule to Elrond's step-progression logic: when a bypass step transitions to 'done', all co-phase pending steps are immediately marked 'superseded' so they do not accumulate as ghost work and Phase 2 address steps can be cleanly attributed. The four known affected initiatives (1000148, 1000149, 1000150, 1000151) will be backfilled once the rule is in place.

⚖️Decisions

• Follow-on to parent INI 999900613 (orion)
• Scope inherited verbatim from parent INI 999900613 per CAROL-INI-361. (elrond.initiative_author)
• Validator-refinement (CAROL-INI-509): Refined 'cookbook' criterion: present-day cookbook index shows 'bypass-methodology' exists (entries #226, #227, #367) but no generic 'bypass' category; changed to 'bypass-methodology' per current state. (elrond.initiative_author)
• Validator-refinement (CAROL-INI-509): Refined step about file path: 'agents/agt_011/droids/ds_s1.py' not found; replaced with correct droid implementation path. (elrond.initiative_author)
• Validator-refinement (CAROL-INI-509): Struck step about backfill using non-existent initiatives: initiatives 1000148-1000151 are not found in present-day registry; backfill step refocused on applying rule to known IDs. (elrond.initiative_author)
• Validator-refinement (CAROL-INI-509): Refined test criterion: test file location 'shared/test_a3_emitters.py' does not exist; use 'shared/test_albus_wiring.py' which appears in present-day failing tests. (elrond.initiative_author)
• Validator-refinement (CAROL-INI-509): Striked cross-reference to cookbook #173: Present-day cookbook category 'bypass-methodology' but #173 is about remediation linkage (separate initiatives), not superseded semantics; kept rule description but removed stale cross-reference. (elrond.initiative_author)
• Validator-refinement (CAROL-INI-509): Refined test criterion: parent said 'new bypass scenario in the test suite' but no bypass-done scenario test exists in registry or regression; kept verbatim as it is still valid to create one. (elrond.initiative_author)
• Validator round 2 still flagged 4 items — operator review needed (CAROL-INI-509). (elrond.initiative_validator)
• [status-router] planned -> dispatched | event=dispatch | RSI: auto-promoted bypasses depth limit (CAROL-INI-2198) (spb-01)
• [status-router] dispatched -> blocked | event=stuck_10min_no_activity | Elrond safety net: initiative has had no activity for 10+ minutes. Blocking under the parallel safety mechanism. (el-watchdog)
• Elrond blocked initiative under the CAROL-INI-2162 dead-Albus protocol. Albus was supposed to wake for step 0 (cause=albus_no_show) but did not respond. Cause: albus_no_show. Reason: Elrond safety net: initiative stranded 10+ min. Albus wake failed or produced no useful result. (el-s1)
• Orion remediated: Albus RSI group diagnosis (via INI 999900432): [procedural, confidence high] Albus executor did not wake to process the initiative after dispatch, as confirmed by the empty execution history and the Elrond safety net block at 2026-07-03 01:41:55 with cause=albus_no_show (see decision 'Elrond blocked initiative under the CAROL-INI-2162 dead-Albus protocol' and rsi_loop.log entries around that time). This is a procedural failure: the executor never started work, matching a systemic pattern affecting 63 other initiatives in the same block group. (orion)
• [status-router] blocked -> closed | event=operator_put | PUT /api/initiatives (operator)
• [rsi-group-cure] Cured by the group diagnosis on INI 999900432 (shared cause stuck_10min_no_activity); retriggered as INI 999900803. Root cause: [procedural, confidence high] Albus executor did not wake to process the initiative after dispatch, as confirmed by the empty execution history and the Elrond safety net block at 2026-07-03 01:41:55 with cause=albus_no_show (see decision 'Elrond blocked initiative under the CAROL-INI-2162 dead-Albus protocol' and rsi_loop.log entries around that time). This is a procedural failure: the executor ne (elrond.rsi_loop)

✅Success criteria

• When a bypass step owned by Orion transitions to 'done' in Phase 1, every other pending step in the same phase is automatically shown as 'superseded' — no manual intervention required. (must_have)
• The four initiatives 1000148, 1000149, 1000150, and 1000151 no longer show any Phase 1 steps in 'pending' status — each previously orphaned step is recorded as 'superseded'. (must_have)
• Phase 2 address steps in initiatives 1000148, 1000149, 1000150, and 1000151 are no longer blocked by unresolved Phase 1 pending steps and are correctly attributed in the monitor. (must_have)
• A new bypass scenario in the test suite confirms that a fresh initiative with a bypass-done step and pending siblings ends up with all siblings superseded and no ghost-pending rows. (must_have)
• Superseded steps are visually distinguishable from 'done' and 'cancelled' steps in the initiative monitor (distinct label or colour). (nice_to_have)
• The cookbook is updated with an entry under the 'bypass' category describing the bypass-reconciliation rule and the 'superseded' status semantics. (nice_to_have)