Evidence record
Automation & reliability engineering
Every published claim on this page was checked by running the command shown. Claims that did not pass were withdrawn before publication; their count is stated below and the full record is available on request.
Measured 2026-08-23 · figures expire with the next publish run; the site is rebuilt from one figures ledger.
Research artifact · published claims
| Claim | How it was checked | Status |
|---|---|---|
| 54 scheduled jobs run on one host — 43 timer units loaded and scheduled, plus 11 active cron lines. 50 timer files were authored by hand; of those, 44 catch up a firing missed during downtime, 29 randomise their start, and 8 are pinned to the US market clock. | systemctl --user list-timers --all --no-legend | wc -l → 43 ; crontab -l | grep -vcE '^\\s*(#|$)' → 11 ; ls -1 <units>/*.timer | wc -l → 50 ; grep -l 'Persistent=true' <units>/*.timer | wc -l → 44 ; grep -l 'RandomizedDelaySec' → 29 ; grep -l 'America/New_York' → 8 ; of the 43 loaded, 42 are from the authored 50 and 1 is supplied by the operating system | published |
| 17 of the 50 authored timer files are guards or hygiene rather than collection — roughly a third of the authored surface exists only to check the rest. | the 50 authored .timer files classified by role from the unit directory listing → 17 guard/hygiene, 33 collection or build. The matching pattern is withheld here because it enumerates internal job names. | published |
| 29 of 61 authored service units declare a non-zero exit status as success, so a check that found a gap is not reported to the scheduler as a crash. | ls -1 <units>/*.service | wc -l → 61 ; grep -l 'SuccessExitStatus' <units>/*.service | wc -l → 29 | published |
| On an ordinary day the host sensor makes 288 three-layer passes, 96 full ten-layer passes, 24 janitor runs and 24 outbound-only posture checks, plus one digest. Four different units of work; they are not summed. | crontab -l → five dispatcher lines: every 5 min quick (three layers — process, network, storage), every 15 min full (all ten layers), hourly janitor, hourly posture check, 06:00 digest. Sensor source: 1,611 lines, standard library only, 10 layers in its layer table. | published |
| The nightly build's watcher is 205 lines of standard library, imports no pipeline module, runs on its own schedule twenty minutes after the build, and its alert log has been 0 bytes since it was armed on 2026-06-05. | wc -l <pipeline-root>/<watcher> → 205 ; its import block is standard library only and names no pipeline module ; crontab -l → build 23:10 weeknights, watcher 23:30 weeknights ; stat -c '%s %y' <pipeline-root>/<watcher-log> → 0 bytes, armed 2026-06-05 | published |
| 61 gated nightly runs are on record: 56 PASS, 3 WARN, 2 FAIL, between 2026-06-05 and 2026-08-21. A WARN or FAIL holds publication. | verdict tally over the gate ledger CSV → 61 rows, [('PASS', 56), ('WARN', 3), ('FAIL', 2)] ; first/last run_at → 2026-06-05T01:28:59 → 2026-08-21T23:19:29 | published |
| The incident ledger holds 370 records across 96 subsystem areas, 2026-07-29 to 2026-08-21: 218 open, 114 fixed, 20 carrying a resolution, 18 closed by an automation. | JSON aggregation over the ledger file → records 370, areas 96, status {open 218, fixed 114, resolution 20, automated 18}; 218+114+20+18 = 370 ; window 2026-07-29 → 2026-08-21 | published |
| The change guard is 484 lines enforcing 7 invariants, runs daily at 07:30 with --fix, and writes whatever it cannot repair to a file the next working session is required to clear first. | wc -l <guard-root>/<guard> → 484 ; grep -c '^ C[0-9]' → 7 invariants ; the guard timer's OnCalendar → daily 07:30 ; the pending-fixes file is present and non-empty | published |
| Failed units at the moment of audit: 0 in system scope, 5 in user scope — 2 finance-scope units exiting 1 because they are holding findings, 3 inert leftovers from software no longer in use. | systemctl list-units --state=failed --no-legend | wc -l → 0 ; systemctl --user list-units --state=failed --no-legend → 5 rows ; systemctl --user show <guard>.service -p Result -p ExecMainStatus → Result=exit-code, ExecMainStatus=1 (findings pending, not a crash) | published |
| The local CI runner runs each repository's test suite plus a nightly check that installs each published Python release into a clean environment, runs its CLI and imports it, and checks the two npm packages against the registry: test suites green at 245, 157 and 16 tests, fresh install passing on all three Python releases, and an end-to-end run of 15 pass / 1 fail. | local CI status record, latest run per repository, 2026-08-23 → working trees green at 245 / 157 / 16 tests ; the e2e harness, 2026-08-23 18:24 → 15 pass / 1 fail, including install-from-index then CLI --help exit 0 for each of the three Python releases, and an import of the installed release; the single failure is the harness's outbound-link check | published |
12 claims tested · 10 published · 2 withdrawn before publication. Full evidence record available on request — king.hippopotamus@yahoo.com.
Author approval — 2026-08-23, hash f0cf48cc