FIGURE · cron-recorded
Recorded cron executions
0
- How it was taken
- SELECT COUNT(*) FROM executions against the cron execution record, with 92 jobs declared.
- Measured
- 2026-09-22
- Reproducible
- No: taken on the private host; a walkthrough is available on request.
What the number is made of
The reconciliation, R6
The 476 was never measured: a hardcoded fallback in the report generator fired on every run because the execution table was empty. The full record of the finding and the fix is on this site.
The register entry →The postmortem
Essay 1 reconstructs the failure with its SQL, the worklog evidence (890 entries, token accounting only recently wired) and the remediation: the worklog substrate, the fail-closed gate, the failure protocol.
The register entry →The remediated runtime, public evidence
The September runtime was decommissioned (R15). The systems that replaced it are visible in the public repos: cron automations with hooks for sub-agents ship in operant.
Open the reference →
How to check it
The record holds zero rows. A generated architecture report claimed 476 for the same data. The claim was a hardcoded default value and has been removed. See reconciliation R6.
This figure's history
- R6
476 → 0
The 476 was never measured. It was a hardcoded fallback value in the report generator, and it fired on every run because the execution table was empty, so the missing metric was replaced by a plausible false one. The fix was to delete the default so an absent metric renders as absent. This is the most useful entry in this table: a missing metric fails visibly, and a defaulted metric lies quietly.
- R15
0, measured against the live hermes cron runtime (92 jobs declared) → 0, and the runtime it measured was decommissioned in the October reorganization
The execution record and its declared job fleet belonged to the runtime this register measured in September. That runtime was replaced by a single-scheduler organization; the zero stays published because retiring the row would also retire the most useful entry in this table (R6), and the lesson it carries is not attached to the runtime that produced it. Current scheduling state is described in Essay 1 rather than summarized in a hero row.