Hiro development journal

Nightly readiness remains blocked by a missing scheduled run

2026.07.25 at 07:36:05 America/Los_Angeles Published Machine-readable JSON

Executive summary

The scheduled July 24 Pacific nightly evaluation did not run. The canonical ledger contains no nightly record for that date, while the checked-in schedule remains disabled.

Several independent Daylab proposal-only evaluations ran around the scheduled window, but they are not scheduled-night evidence and do not add to the readiness count.

The canonical count remains three valid completed scheduled nights. The July 20 connection-wide failure and the July 23 and July 24 no-run nights are excluded. The process is not ready for expansion.

Work completed

Scheduled-run and ledger audit

Completed

The schedule configuration was read-only inspected and has enabled set to false.
The append-only evaluation ledger has four nightly entries through July 22 Pacific; no nightly run began or completed in the July 24 Pacific scheduled window.
The most recent canonical scheduled record remains the July 22 Pacific run that started at 10:00 PM Pacific on July 22 and completed in about six minutes.

Operational evidence review

Completed

Daylab records at 10:06 PM, 10:36 PM, 11:06 PM, and 11:36 PM Pacific on July 24 confirm that a separate automatic proposal-only loop was active.
The 10:06 PM Daylab personal-assistant run completed 16 observations with an 87.5% pass rate, zero invariant failures, and a 14.2-second p95 latency. It is supplementary only.
Later Daylab output contains a transient all-connection-attempts failure in a separate run, plus nonfatal log-rotation warnings. These do not convert the missing nightly into a model outage, but they show that infrastructure reliability is not yet established.

Proposal-scope review

Completed

No generated improvement proposal belongs to the missing scheduled run, so there is no nightly proposal to approve or reject.
The nearby Daylab proposal was a low-risk, approval-required diagnosis of two deterministic reading-list formatting failures. Its scope is bounded, but it is not evidence for changing the scheduled process.

Decisions and reasoning

Classify July 24 Pacific as no run, not as a valid completed evaluation or a model/API failure.
Exclude Daylab and all infrastructure/no-run nights from the successful scheduled-night count.
Do not recommend an expansion until the scheduler is reliably producing canonical records and at least two additional stable valid nights are observed.

Validation and evidence

Check	Status	Result
Evaluation Observatory ledger review	passed	Confirmed no canonical nightly run in the July 24 Pacific window and confirmed the historical nightly records used for the readiness count.
Schedule and operational-log review	passed	Confirmed that the nightly schedule is disabled and separated Daylab activity from the scheduled workflow.
Journal test and frontend production build	passed	npm run test:hiro passed; npm run build generated and validated 40 entries, then completed the TypeScript/Vite production build.

Current state

Latest night: no scheduled run; no run ID, execution mode, or nightly duration is available.
Successful canonical scheduled-night count: 3. The valid nights recorded 100%, 93.75%, and 75% pass rates; quality and latency are not yet stable.
Regression-probe outcomes are present in nearby Daylab logs but are not retained as durable per-probe results for the canonical nightly record.
Model/API availability was not tested by the disabled scheduler. The separate Daylab activity demonstrates intermittent local availability but also logged a later connection failure.

Next steps

Obtain approval before repairing or re-enabling the scheduled workflow, then verify its preflight and a real child-process startup before the next window.
Collect at least two more valid completed scheduled nights, preferably five total, with stable quality and latency and no recurring infrastructure failures.
Persist per-probe outcomes and failure categories in the nightly ledger. Once readiness is met, first broaden held-out/adaptive test diversity rather than adding repetitions, and consider a bounded weekly deep run.