Define the LiturgicalDay aggregate and day() entry point #13

New issue

Closed

opened 2026-07-01 00:50:47 +00:00 by manlycucumber · 0 comments

manlycucumber commented

2026-07-01 00:50:47 +00:00

(Migrated from github.com)

Problem

The public surface is day(date) returning an object with celebration[], commemoration[], displaced[], and tempora[]. The aggregate and entry signature must exist before the resolver phases can populate it.

Acceptance criteria

day() accepts a date and returns a LiturgicalDay with the four arrays
Empty/placeholder day construction is well-defined and tested
The aggregate is immutable once built
Unit test asserts the shape of a returned day for a trivial date

Notes

This is the contract seam; the output-contract epic formalises serialisation.

## Problem The public surface is `day(date)` returning an object with celebration[], commemoration[], displaced[], and tempora[]. The aggregate and entry signature must exist before the resolver phases can populate it. ## Acceptance criteria - [ ] `day()` accepts a date and returns a `LiturgicalDay` with the four arrays - [ ] Empty/placeholder day construction is well-defined and tested - [ ] The aggregate is immutable once built - [ ] Unit test asserts the shape of a returned day for a trivial date ## Notes This is the contract seam; the output-contract epic formalises serialisation.

manlycucumber referenced this issue from a commit

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

feat: add LiturgicalDay aggregate and day() entry point (#205)

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

No description provided.

Rows
Columns