Define the generated corpus file schema and layout #39
Labels
No labels
area: build
area: ci
area: compare
area: data
area: engine
area: model
area: provenance
area: rite
area: validation
backport
blocked
breaking
confirmed
dependencies
duplicate
epic
github_actions
invalid
needs-info
needs-triage
php
priority: high
priority: low
priority: medium
regression
type: bug
type: chore
type: correction
type: docs
type: enhancement
type: feature
type: fix
type: perf
type: refactor
type: security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Directorium/Core#39
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
The engine reads generated static data. A documented schema and on-disk layout for identity records, per-edition attributes, temporal definitions, and precedence data is needed before generation can begin.
Design alignment (v0.1.0)
The corpus follows the identity / edition / year model. The identity record carries only the
Observanceslug (<rite>:<cycle>:<body>), kind, titulars, names, and aliases — no rank, colour, octave, or date. Rank / colour / placement live in per-edition attribute overlays keyed by (id, edition). Temporal day IDs are structural only (no Easter-offset aliases). Seedocs/design/observance-id-grammar.md.Acceptance criteria
Notes
Corpus is CC0; text strings carry per-string provenance (ties to the SOURCES ledger).