📖About

Ninad's ruling (2026-08-04): the fleet wakes ONCE A DAY, not every six hours.

THE BASIS, measured today: 131 wakes, of which 78 looked, found nothing worth doing, and said so Four wakes a day for 39 minds is a clock firing whether or not anything happened, and the code's own design note says the intended model was event-driven with a slow pulse as backstop, not a fast fixed clock for everyone.

WHAT CHANGES: the pulse fires once daily at 06:05 instead of at 00:05, 06:05, 12:05 and 18:05. Nothing else -- not what a wake does, not what it may decide, not the consciousness switch, and not the ability of one agent to rouse another the moment something genuinely needs thought. The event path is untouched, so an agent that needs waking is still woken; only the unprompted clock slows.

WHY THE DROID RECORDS MOVE TOO: all 39 minds declare 'Every 6h' in the registry. Changing the trigger without the records leaves the estate saying one thing and doing another -- the drift this session has already cured twice today. Trigger and record move together or not at all.

The

it is Midas's decision on its own merits, not a side effect of a schedule change.

⚖️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)
• [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

• The scheduled pulse fires once a day, not four times: proven by reading back the live schedule after the change. (must_have)
• All 39 minds declare the new cadence in the registry -- no droid still says 'Every 6h' -- proven by counting before and after. (must_have)
• Nothing else about a wake changes: an agent can still be roused by another agent on the event path, and the consciousness switch still governs whether wakes happen at all. (must_have)
• (must_have)
• (must_have)