[Epic] Rubric-system abstraction #59
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#59
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?
Introduce a first-class rubric-system selector so the engine can run any of 1954/1955/1962 from data without code branches. Done when day() takes a rubric system and resolves accordingly.
Epic — child issues are tracked as sub-issues.
AC amendment (roadmap v3): every new edition/rubric-family must name ≥2 pinned validation oracles as an acceptance criterion (mirrors the 1962 oracle discipline that has caught real bugs each epic).
The rubric-system (edition) seam is complete (PR #446, squash
1531e98): aRubricSystemvalue object on a new edition axis, per-edition data selection in the sanctoral loader + precedence table, andDayResolver::forEdition()stamping the edition into the contract.day()/contract()/explain()take an appended, backward-compatible$rubricSystemselector; the overlay axis is unchanged and orthogonal. 1962 resolves byte-identically (golden fixture unmoved; 719 tests green). 1954/1955 are declared and reserved for #63/#68. Design:docs/design/rubric-system-model.md.