Derive expression and release labels; make their appellations optional

thecrealm commented

2026-07-23 14:23:55 +02:00

Owner

M5, follow-up to the D56 chain lanes. Structured decision 2026-07-23 (thecrealm): option A — appellations record names attested in the world; expressions and releases typically bear none, so their required synthetic appellations ('Deutsche Übersetzung, Band 5', '… (Release)') are fabricated provenance that drifts with the chain (§6.1 tension) and pollutes search.

Scope:

§11.1.2 amendment (same change-set as the code): the ≥1-appellation creation rule becomes type-conditional — required for work/manifestation/agents/concept, optional for expression and release; state the attested-names principle. §8.1 note: derived display labels (expression: realizes-target label + kind/language; release: of-manifestation label + date). §14.3 rows; D-entry.
Server: derived-label resolver on the read side (labels endpoint incl. picker q= search for type=expression via realizes join, ladder/board hydration, gap list, calendar fallback already in place at CalendarProjection.kt:156). Shape rule in ChangeSetService.validateShape goes type-conditional.
Web: chain composer (#58) and worklist chain step (#59) drop their expression/release title fields; ChainPanel mechanical middle stops generating appellations.
Existing synthetic appellations stay valid; optional cleanup batch (§5.5, revertible) as a separate follow-up decision.
Orphan subtrees (#60 gap shapes) fall back to 'Fassung (…)' + id.

Acceptance: creating an expression/release without appellation succeeds and renders with a derived label on entity pages, pickers, ladder, board, gap list and calendar (CR-6/CR-5 surfaces unaffected); works/manifestations still require an attested appellation; wizard and chain step no longer emit synthetic titles (CR-2: no references on statements that no longer exist).

M5, follow-up to the D56 chain lanes. Structured decision 2026-07-23 (thecrealm): option A — appellations record names attested in the world; expressions and releases typically bear none, so their required synthetic appellations ('Deutsche Übersetzung, Band 5', '… (Release)') are fabricated provenance that drifts with the chain (§6.1 tension) and pollutes search. Scope: - §11.1.2 amendment (same change-set as the code): the ≥1-appellation creation rule becomes type-conditional — required for work/manifestation/agents/concept, optional for expression and release; state the attested-names principle. §8.1 note: derived display labels (expression: realizes-target label + kind/language; release: of-manifestation label + date). §14.3 rows; D-entry. - Server: derived-label resolver on the read side (labels endpoint incl. picker q= search for type=expression via realizes join, ladder/board hydration, gap list, calendar fallback already in place at CalendarProjection.kt:156). Shape rule in ChangeSetService.validateShape goes type-conditional. - Web: chain composer (#58) and worklist chain step (#59) drop their expression/release title fields; ChainPanel mechanical middle stops generating appellations. - Existing synthetic appellations stay valid; optional cleanup batch (§5.5, revertible) as a separate follow-up decision. - Orphan subtrees (#60 gap shapes) fall back to 'Fassung (…)' + id. Acceptance: creating an expression/release without appellation succeeds and renders with a derived label on entity pages, pickers, ladder, board, gap list and calendar (CR-6/CR-5 surfaces unaffected); works/manifestations still require an attested appellation; wizard and chain step no longer emit synthetic titles (CR-2: no references on statements that no longer exist).

thecrealm added the

M5

now

labels

2026-07-23 14:24:04 +02:00

thecrealm referenced this issue from a commit

2026-07-23 14:43:22 +02:00

Make expression and release appellations optional; derive their labels (closes #62)

thecrealm closed this issue

2026-07-23 14:43:22 +02:00

Rows
Columns

Derive expression and release labels; make their appellations optional #62