eric/audita
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 6 Wiki Activity

Resolve extensible glossary entry content fields

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-09 03:28:30 +00:00
parent 1b76a426cc
commit 77995b7a2c
2 changed files with 64 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/roadmap/configkit.md
View File

@@ -1,6 +1,6 @@
# ConfigKit Adoption Outline
**Updated:** 2026-11-08
**Updated:** 2026-11-09
**Status:** Initial outline. The [master roadmap](library-adoption.md) owns the
agreed adoption policy, reviewed versions, shared sequencing, and completion.
@@ -135,10 +135,11 @@ file remain terminal.
Supply its [optional default glossary sources](glossary-stages.md#default-sources-and-explicit-configuration--resolved)
in one underlay, with higher-priority explicit main configuration.
Register its [collection-scoped entry IDs](glossary-stages.md#entry-identity--resolved)
through native sequence identity registration.
through native sequence identity registration. Apply its
[extensible entry content contract](glossary-stages.md#entry-content-fields--resolved)
using native typed fields and inline extension data.
Complete its required durable decision record. The glossary roadmap owns
the remaining rich-field, runtime-view,
selection-input, and attribution decisions. This
the remaining runtime-view, selection-input, and attribution decisions. This
application scope model does not change native source composition or
sibling-inheritance semantics.