📖About

Evidence-based relevance check (Ninad doctrine: retire on irrelevance only, never on 0 runs). RETIRE: tp-01 (pre-pipeline tactical-planner relic, 3 identical copies, zero invokers - superseded by the planner pipeline), mirror (empty stub; live bio sync covers its purpose), org-app (app mis-registered as droid), orion-logbook-backfill (one-time backfill, done). KEEP id-sync-01 (live user-identity linking used by Carol chat; fill its empty registry purpose). FILE separately (planner): steward run-audit gap - the steward sweep runs but NO steward emits run-audit rows, a mechanism-wide observability gap.

⚖️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)
• Current state at filing (Elrond validity check): The registry shows mirror, id-sync-01, org-app, tp-01, and orion-logbook-backfill all with status=running. id-sync-01's purpose field is empty. No steward run-audit rows are being emitted. The four droids targeted for retirement are active and monitorable. (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)
• [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

• The Process Health Scorecard and Scheduled Processes stop counting the 4 retired droids as monitorable and show them under Retired; none of them can generate liveness alarms or block assignments again (must_have)
• Anyone opening id-sync-01 in the registry reads what it actually does (user identity linking for Carol chat) instead of an empty purpose (must_have)