Plan ConfigKit glossary composition and derived runtime views

This commit is contained in:
2026-11-08 18:51:37 +00:00
parent af6f62e14b
commit 64786140e8
3 changed files with 276 additions and 170 deletions

View File

@@ -126,10 +126,13 @@ file remain terminal.
together with its [CLI precedence and native-support boundary](glossary-stages.md#cli-overrides-and-stage-precedence--resolved).
Use its [separate glossary and protection selections](glossary-stages.md#glossary-selection-and-protected-vocabulary--resolved),
including root protection defaulting through recorded application resolution.
Apply its [post-handoff application-resource path policy](glossary-stages.md#relative-paths-and-source-context--resolved)
while leaving upstream configuration resolution to ConfigKit.
Adopt its [glossary configuration ownership boundary](glossary-stages.md#glossary-configuration-ownership--resolved):
glossary assets use native loading, composition, inheritance, collection
identity, and typed decoding before handoff. Audita derives consumer-specific
runtime views from that result and removes its separate glossary YAML loader.
Complete its required durable decision record. The glossary roadmap owns
the remaining list-input, combined-entry, and attribution decisions. This
the remaining collection schema, composition scope, identity, runtime-view,
selection-input, and attribution decisions. This
application scope model does not change native source composition or
sibling-inheritance semantics.