Define the particular-calendar overlay data format #76

New issue

Closed

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

manlycucumber commented

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

(Migrated from github.com)

Problem

Particular calendars differ from the universal calendar by adding, suppressing, or re-ranking feasts. A declarative overlay format is needed so each calendar is a thin data layer, not code.

Acceptance criteria

Overlay format expresses add, suppress, and re-rank operations
Overlays reference stable feast IDs
A sample overlay validates against the schema
Provenance is recorded per overlay

Notes

Overlays must not require engine code changes.

## Problem Particular calendars differ from the universal calendar by adding, suppressing, or re-ranking feasts. A declarative overlay format is needed so each calendar is a thin data layer, not code. ## Acceptance criteria - [ ] Overlay format expresses add, suppress, and re-rank operations - [ ] Overlays reference stable feast IDs - [ ] A sample overlay validates against the schema - [ ] Provenance is recorded per overlay ## Notes Overlays must not require engine code changes.

manlycucumber commented

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

(Migrated from github.com)

Done in #443. Cited overlay YAML (facts/overlays/<slug>.yaml) → reproducible overlays/<slug>/ NDJSON + overlay.json, born-cited (new sspx-ordo source), with overlay-operation/overlay JSON Schemas and the CorpusOverlayData loader. corpus-verify covers it.

Done in #443. Cited overlay YAML (`facts/overlays/<slug>.yaml`) → reproducible `overlays/<slug>/` NDJSON + `overlay.json`, born-cited (new `sspx-ordo` source), with `overlay-operation`/`overlay` JSON Schemas and the `CorpusOverlayData` loader. corpus-verify covers it.