📖About

Register Sprint Planning as a first-class building block of the initiatives service (CAROL-INI-1939 capability). Add a blocks row (key sprint_planning, owner Elrond, parent_service initiatives) positioned right after Filing in the lifecycle; link the Sprint Builder droid to the block; add Carolopedia prose so the block page shows real details (what it does, where it fits, budgeting/ETA/rollover). Midas Services Catalogue reads blocks live from the registry so it surfaces automatically. Verify the block renders in both Midas and Carolopedia.

⚖️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)
• Note: twin-reviewer fail was an artifact of (a) success criteria added after close and (b) DB-only work (registry + Carolopedia writes, no tracked code files to grade). Deliverables VERIFIED live: Midas catalogue lists Sprint Planning at position 2; Carolopedia /wiki/block/sprint-planning returns 200 with full prose. Ready for UAT sign-off. (orion)
• [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

• Sprint Planning exists as a block of the initiatives service, positioned after Filing in the lifecycle chain (must_have)
• Midas Services Catalogue lists the Sprint Planning block for the initiatives service (must_have)
• Carolopedia renders a Sprint Planning block page with real details (purpose, budgeting, ETA, rollover) (must_have)
• The Sprint Builder droid is linked to the block so the block team shows Elrond and the builder (must_have)