📖About

Ninad rulings (CLI-248): (1) Clara's 'Carolverse' app (roadmap, 7175) is renamed 'Carolverse Strategy' - registry app name + the app header h1 (icon+h1+tagline block only; canonical topbar untouched). (2) In-app labels 'Services'/'All services' become 'Projects'/'All projects'. (3) The landing shows ONE umbrella card named 'Carolverse': the strategic card (55 real entries) is renamed from 'Carol (strategic)'; the duplicate 'Carol' project card shows 11 auto-drafted generic template entries (0 done) which are removed with a backup so the card hides by the existing zero-entry rule. (4) Header owner prose reconciled with the registry record. (5) Data Dictionary updated for these renames.

⚖️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 -> parked | event=bypass_blocked|pipeline_stopped_park_3044 | pipeline stopped (operator OFF or budget-paused) - parked instead of blocked so the stop does not strand live work (CAROL-INI-3044); resumes on turn-ON (or-bx-01)
• Bypass session failed — initiative blocked (exec 1428) — bypass_end called with success=False for exec 1428, run 3183 (shared.bypass.bypass_end)
• [status-router] parked -> executing | event=bypass_executing | bypass transition (or-bx-01)
• [status-router] executing -> parked | event=bypass_blocked|pipeline_stopped_park_3044 | pipeline stopped (operator OFF or budget-paused) - parked instead of blocked so the stop does not strand live work (CAROL-INI-3044); resumes on turn-ON (or-bx-01)
• Bypass session failed — initiative blocked (exec 1429) — bypass_end called with success=False for exec 1429, run 3184 (shared.bypass.bypass_end)
• [status-router] parked -> executing | event=bypass_executing | bypass transition (or-bx-01)
• [delivery-check] 5 must-have criteria remain pending at bypass_end — delivery has no mechanical re-performance lane; UAT must grade on live evidence, not checklist silence (CAROL-INI-3020): (no detail) (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

• Registry app row 'roadmap' is named 'Carolverse Strategy'; app header h1 matches; canonical topbar untouched (must_have)
• Landing section reads 'Projects' and back-link 'All projects'; no user-visible 'Services' label remains in the app (must_have)
• Landing shows exactly one umbrella card named 'Carolverse' (the strategic roadmap, entries intact); the duplicate Carol template card is gone with its 11 entries backed up, not destroyed (must_have)
• App header owner prose agrees with the registry owner record (must_have)
• Data Dictionary reflects the renames (Carolverse term/near-misses reference the Carolverse Strategy app correctly) (must_have)