Add a rubric-system matrix to the CI validation job #73

New issue

Closed

opened 2026-07-01 00:53:01 +00:00 by manlycucumber · 1 comment

manlycucumber commented

2026-07-01 00:53:01 +00:00

(Migrated from github.com)

Problem

With three systems, CI must validate each independently so a change to shared code cannot silently regress one. A system matrix is needed.

Acceptance criteria

CI runs validation for 1954, 1955, and 1962
Each system has its own oracle gate
A regression in any system fails the build
Matrix runtime stays within budget

Notes

Reuse cached fixtures per system.

## Problem With three systems, CI must validate each independently so a change to shared code cannot silently regress one. A system matrix is needed. ## Acceptance criteria - [ ] CI runs validation for 1954, 1955, and 1962 - [ ] Each system has its own oracle gate - [ ] A regression in any system fails the build - [ ] Matrix runtime stays within budget ## Notes Reuse cached fixtures per system.

manlycucumber commented

2026-07-06 21:02:28 +00:00

(Migrated from github.com)

Done in PR #457 (be94e04). The CI validate job is now a matrix over 1962/1954/1955 with fail-fast: false, each leg running only its @group edition-<system> oracles as an independent gate — 1962 = Computus + missalemeum + SSPX, 1954/1955 = the Divinum Officium agreement fixtures (split per edition). A regression in one edition fails only its leg and never masks another. Fixtures are committed (no network); composer deps cached. Verified green on the PR: validate (1962), validate (1954), validate (1955) all pass.

Done in PR #457 (`be94e04`). The CI `validate` job is now a **matrix over `1962/1954/1955`** with `fail-fast: false`, each leg running only its `@group edition-<system>` oracles as an independent gate — 1962 = Computus + missalemeum + SSPX, 1954/1955 = the Divinum Officium agreement fixtures (split per edition). A regression in one edition fails only its leg and never masks another. Fixtures are committed (no network); composer deps cached. Verified green on the PR: `validate (1962)`, `validate (1954)`, `validate (1955)` all pass.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Directorium/Core#73

No description provided.

Rows
Columns