📖About

Athena escalated to Orion (Agentbook 90, 2026-08-15) that Clara and Elrond are not waking. They ARE waking - the wake log shows both completing every day 08-11 through 08-15. The defect is in the MEASUREMENT. consciousness_health._schedule_hours understands "Every 6h" and "Every 15 min" only; the registry writes wake cycles as "Daily 06:05", which matches nothing and falls back to DEFAULT_SCHEDULE_HOURS=6. Grace becomes 6h x 3 = 18h, so a once-a-day mind is overdue by construction from ~18h after each wake. It surfaces as exactly two agents because Athena runs her roll-call inside the same 06:05 sweep, in droid-id order: al- and at- have already woken when she looks, cl- and el- have not. Same misread applies to every Weekly/Hourly/Every-minute schedule string in the registry. Fix the parser at its one home so every surface that reads consciousness health follows, and add a regression test over the real registry vocabulary.

⚖️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)
• [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 schedule parser reads every wake-cycle vocabulary the registry actually uses (Daily HH:MM, Weekly, Hourly, Every N min/h, Every minute) - proven against the live registry rows, not invented strings (must_have)
• Clara and Elrond read as healthy in the consciousness health record, with a grace window derived from their real daily cadence (must_have)
• A genuinely overdue daily mind is still caught - the fix must not blind the check (must_have)
• A regression test pins the vocabulary so the parser cannot silently fall back to 6h again (must_have)