Define stable cross-system feast identifiers #55

New issue

Closed

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

manlycucumber commented

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

(Migrated from github.com)

Problem

The same feast must carry a stable ID across rubric systems and calendars so clients can link, translate, and cache it. These IDs must be defined and guaranteed stable.

Acceptance criteria

Each feast has a stable cross-system ID independent of date or rank
IDs are documented as a compatibility surface
A test guards against accidental ID changes
Mapping from observance ID to stable feast ID exists

Notes

Later systems (1954/1955, monastic) reuse these IDs.

## Problem The same feast must carry a stable ID across rubric systems and calendars so clients can link, translate, and cache it. These IDs must be defined and guaranteed stable. ## Acceptance criteria - [ ] Each feast has a stable cross-system ID independent of date or rank - [ ] IDs are documented as a compatibility surface - [ ] A test guards against accidental ID changes - [ ] Mapping from observance ID to stable feast ID exists ## Notes Later systems (1954/1955, monastic) reuse these IDs.

manlycucumber referenced this issue from a commit

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

feat: guarantee stable cross-system feast identifiers (#55) (#356)

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

No description provided.

Rows
Columns