[Epic] Bilingual text assembler #103
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Directorium/Core#103
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?
Build the assembler that joins Latin and English text into the resolved office structure with per-string provenance. Done when an office renders bilingually from referenced sources.
Epic — child issues are tracked as sub-issues.
Design of record: docs/design/office-text-layer.md (approved 2026-07-17, PR #494). No engine code until Stage 0 (§9) lands.
Stage 3. Spec §4 (bilingual assembler #104), §4.4 (per-string provenance, fail-closed gate #105), §5 (downstream-consumer seam — writes reserved slots + the new additive day-level
officekey, no major bump #106).Epic done — all three children (#104, #105, #106) are closed.
An office renders bilingually from referenced sources through the frozen contract, with per-string provenance travelling with every leaf and the whole path failing closed on missing Latin or missing citation. Proven end to end by the per-annum Little Office of the BVM: all eight hours resolve into every 1962 day.
Scope note: this is the v1.1-shaped assembler pairing exactly one Latin + one English. The keyed multi-vernacular variant model is #295–#297, still open.