Apply an overlay during the sanctoral phase #77

New issue

Closed

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

manlycucumber commented

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

(Migrated from github.com)

Problem

The engine must apply a selected overlay's operations to the universal sanctoral before precedence runs, so particular feasts resolve correctly.

Acceptance criteria

A selected overlay's add/suppress/re-rank ops apply before precedence
Overlay application is deterministic and order-independent where defined
Conflicts between overlay and universal data are resolved by a documented rule
Unit test applies a sample overlay and checks resolution

Notes

Core resolution logic stays unchanged; only data is layered.

## Problem The engine must apply a selected overlay's operations to the universal sanctoral before precedence runs, so particular feasts resolve correctly. ## Acceptance criteria - [ ] A selected overlay's add/suppress/re-rank ops apply before precedence - [ ] Overlay application is deterministic and order-independent where defined - [ ] Conflicts between overlay and universal data are resolved by a documented rule - [ ] Unit test applies a sample overlay and checks resolution ## Notes Core resolution logic stays unchanged; only data is layered.

manlycucumber commented

2026-07-02 21:20:59 +00:00

(Migrated from github.com)

Done in #442. OverlaidSanctoralData decorates the SanctoralData seam the resolver already reads through, so an overlay changes only data — precedence/concurrence/commemoration logic is untouched. Add/suppress/rerank value objects + 11 tests.

Done in #442. `OverlaidSanctoralData` decorates the `SanctoralData` seam the resolver already reads through, so an overlay changes only data — precedence/concurrence/commemoration logic is untouched. Add/suppress/rerank value objects + 11 tests.

manlycucumber referenced this issue from a commit

2026-08-05 19:02:29 +00:00

feat: particular-calendar overlay model and decorator (#75) (#442)

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#77

No description provided.

Rows
Columns