📖About

Ninad ruling: Elrond can file or route the most urgent initiatives - infrastructure-related problems - to the Albus Bypass lane, especially while the planner pipeline is still self-healing. Every routing must carry a justification (why this initiative goes to the Albus lane) and a stated urgency. The Albus Bypass Runner prioritises Elrond's urgent requests over its abandoned-work pickups but executes them only. Albus sets aside half of his daily budget for Elrond's urgent requests; ordinary abandoned-work pickups may only consume that reserved half during the last hour of the budget day, so urgent requests filed during the day are never stranded while the reserve is not wasted overnight. The RSI loop and the Dispatch Queue card leave urgent-routed initiatives to the Albus lane. The discipline is recorded in the cookbook.

⚖️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)
• Urgent lane design (CAROL-INI-3284): routing lives in a new shared module - mandatory justification+urgency recorded as a decision, tag albus-bypass-urgent, mode flipped to bypass at routing; the Albus Bypass Runner picks urgent (oldest routed) before abandoned; reserve = 50% of the albus lane cap, abandoned pickups refused once spend would eat the reserve except after 23:00 UTC (the budget day rolls ~00:00:30 UTC); failed urgent attempts take the 24h cooldown decision but keep their routing and never get the rsi-abandoned tag; the RSI loop picker and Dispatch Queue card exclude urgent-routed initiatives (the Dispatch Queue exclusion-tag list placeholder count is now derived from the tuple, not hardcoded). (orion)
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• [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 can route an urgent infrastructure initiative to the Albus Bypass lane with a recorded justification and urgency; a routing without either is refused. (must_have)
• The Albus Bypass Runner picks Elrond's urgent requests ahead of abandoned work, and both the RSI loop and the Dispatch Queue card leave urgent-routed initiatives to the Albus lane. (must_have)
• Half of Albus's daily bypass budget stays reserved for Elrond's urgent requests: abandoned-work pickups cannot start once they would eat into the reserve, except in the last hour of the budget day when the reserve opens up so it is not wasted. (must_have)
• The discipline is written into the cookbook, and a registered regression test proves the routing rules, the priority order and the budget reserve. (must_have)