/proof › RR-001 scoreboard › H8
Hypothesis H8
WordingPipeline runs >=27 of 30 days without intervention
Falsification threshold
>=4 outage days requiring manual fixCurrent statuspending
Evidence summaryAwaiting evaluator run
Pre-disclosed expected outcome (honesty disclosure):
Expected supported — production cron jobs (daily/weekly/monthly publish) are now wired with per-user lock + idempotency.
Expected supported — production cron jobs (daily/weekly/monthly publish) are now wired with per-user lock + idempotency.
How this hypothesis resolves
The threshold above is the pre-registered falsification rule. Once the evaluator runs (per the schedule in the protocol document), the `currentStatus` column on `reference_run_hypotheses` updates and this page reflects the verdict. All evaluator runs are cryptographically sealed via the daily Merkle anchor.
Source of truth
- Schema:
reference_run_hypotheses(migration 0104) - Evaluator:
lib/referenceRun/hypothesisEvaluator.ts - Writer:
DrizzleHypothesisDbWriterinlib/referenceRun/dbWriters.ts - Locked wording:
LOCKED_HYPOTHESESinlib/referenceRun/hypothesisEvaluator.ts