Serialise day() to the versioned output contract #53

New issue

Closed

opened 2026-07-01 00:52:16 +00:00 by manlycucumber · 0 comments

manlycucumber commented

2026-07-01 00:52:16 +00:00

(Migrated from github.com)

Problem

Downstream APIs consume a stable serialisation of day(). The contract's concrete shape (the four arrays plus metadata) must be defined and emitted consistently.

Acceptance criteria

day() serialises to a documented structure with celebration/commemoration/displaced/tempora
Each observance carries ID, rank, colour, and season
Serialisation is deterministic
A snapshot test pins the shape for a sample day

Notes

This is the public contract other Introibo repos build on.

## Problem Downstream APIs consume a stable serialisation of day(). The contract's concrete shape (the four arrays plus metadata) must be defined and emitted consistently. ## Acceptance criteria - [ ] day() serialises to a documented structure with celebration/commemoration/displaced/tempora - [ ] Each observance carries ID, rank, colour, and season - [ ] Serialisation is deterministic - [ ] A snapshot test pins the shape for a sample day ## Notes This is the public contract other Introibo repos build on.

manlycucumber referenced this issue from a commit

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

feat: serialise the resolved day to the versioned output contract (#53) (#354)

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

No description provided.

Rows
Columns