📖About

Elrond must prioritise SYSTEM INCIDENTS over regular transformation initiatives in his sprint plan. Three parts: (1) Define + build an EXPLICIT prioritization SCORE model for Elrond sprint planning — clear factors + tunable weights. Tiered by incident severity: CRITICAL incidents always rank first (hard top tier); below that a blended numeric score from incident-severity, urgency, age (anti-starvation), blocking/dependents, and roadmap/business value (no effort factor). Replace the current FIFO-ish (committed,urgency,age) sort. An incident = a monitoring/health fix-initiative (requester in hermione/inspector/guardian or carrying an incident/uat-target tag). Persist the computed score for observability. (2) Close the Inspector blind spot: the Inspector only checks Hermione is alive+firing, never whether her FILINGS landed. Add a filing-OUTCOME watch that detects file-failed sweep findings (detections with null initiative_id) and escalates. (3) Speed up incident filing: the create path makes blocking haiku LLM calls inline (service-classification always, semantic dedup on title overlap) under the single writer -> ~37s, exceeding Hermione 10s timeout -> file-failed. Add an incident fast-path that skips both LLM steps (deterministic Tier-1 dedup + deterministic service) so incidents file sub-second.

⚖️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)
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• Orion remediated: INI-999900190 bypass closed — CAROL-INI-696 close-marker: the Orion bypass INI-999900190 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-999900191 bypass closed — CAROL-INI-696 close-marker: the Orion bypass INI-999900191 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

• Elrond sprint planning uses an EXPLICIT priority-score with named factors and tunable weights (not FIFO); the constants are documented in the module. (must_have)
• Critical system incidents always rank ahead of every transformation initiative; non-critical incidents are heavily boosted but blend by score. (must_have)
• The Inspector detects when Hermione filings fail to land (file-failed / null initiative_id) and escalates, not just whether she is firing. (must_have)
• An incident filing commits in under 2 seconds (no inline LLM call), verified by timing; transformation filings keep full classification. (must_have)