[Epic] Validation harness #45
Labels
No labels
area: build
area: ci
area: compare
area: data
area: engine
area: model
area: provenance
area: rite
area: validation
backport
blocked
breaking
confirmed
dependencies
duplicate
epic
github_actions
invalid
needs-info
needs-triage
php
priority: high
priority: low
priority: medium
regression
type: bug
type: chore
type: correction
type: docs
type: enhancement
type: feature
type: fix
type: perf
type: refactor
type: security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Directorium/Core#45
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Stand up the 're-prove 100%' validation: Computus vs PHP easter_days(), a harvested missalemeum oracle fixture, the SSPX feed, and an optional Divinum Officium Perl oracle. Done when CI fails on any divergence from the oracles across the test date range.
Epic — child issues are tracked as sub-issues.
Epic complete — validation harness landed ✅
All six children are done; the engine is now re-proven against independent oracles on every PR, and CI fails on any divergence from the committed baselines.
Children
easter_days(), 1583–2200 + anchor dates.day()asserted field-by-field (class/colour/commemorations) vs missalemeum against a categorised 421-row known-differences baseline.validateCI job (deps cached); added to themainruleset's required status checks.Real bugs the harness caught (fixed under this epic)
Each was fixed as its own cited PR with the golden fixture re-frozen.
Follow-on
The baselines are living worklists, not rubber stamps (a regression and an improvement both fail until re-frozen). The 421-row missalemeum baseline + the corroborating SSPX rows are the base-1962 accuracy worklist tracked in #428; the SSPX-particular rows seed the v0.2 SSPX overlay.
Maintainer note
validateis now required on themainprotection ruleset (done via API). No further action needed.Closing as complete.