Select named glossary collections with recursive directory imports
This commit is contained in:
@@ -130,8 +130,10 @@ file remain terminal.
|
||||
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.
|
||||
Use its [named collections and recursive import placement](glossary-stages.md#named-collections-and-recursive-imports--resolved),
|
||||
retaining native discovery, source context, and tier semantics.
|
||||
Complete its required durable decision record. The glossary roadmap owns
|
||||
the remaining collection schema, composition scope, identity, runtime-view,
|
||||
the remaining entry schema, import provisioning, identity, runtime-view,
|
||||
selection-input, and attribution decisions. This
|
||||
application scope model does not change native source composition or
|
||||
sibling-inheritance semantics.
|
||||
|
||||
Reference in New Issue
Block a user