📖About

Ninad's UAT ruling on the Task Tracker reconciliation card (2026-08-02): the registry tracks are right. (1) Re-home the six backup task declarations from the nonexistent tracks backup-backups/backup-core onto the four real budgeted tracks (laptop backup -> backup-laptop, git ship -> backup-off-site, registry snapshot -> backup-on-machine, disk cleanup + infra score + infra improvement -> backup-upkeep) and seed their budgets from those tracks. Reconciliation card then shows these ten tracks clean; remaining drift only where genuinely undecided.

⚖️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_work_complete | CAROL-INI-3615 bypass work complete: backup re-home + five tracks declared and seeded; support-core honestly reported as nothing-countable (orion)
• [delivery-check] 4 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] 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 reconciliation card shows the four backup tracks with tasks whose budgets sum to each track budget, and the two nonexistent-track rows are gone (must_have)
• Each of the six previously empty budgeted tracks shows at least one declared task with a real counting source, budgets summing to the track budget (must_have)
• No new task overlaps an existing unit's meaning; every declaration names a source that actually records the delivery (must_have)
• The regression suite's task-registry tests still pass and the reconciliation drift list shrinks accordingly (must_have)