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

Finalize ConfigKit architecture documentation

Browse Source
This commit is contained in:
Eric Rakestraw
2026-09-13 17:26:57 +00:00
parent 19f1979bac
commit 3010a918dc
7 changed files with 70 additions and 66 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
docs/adr/0018-adopt-configkit.md
View File

@@ -5,9 +5,9 @@
## Context
Notarius's configuration boundary currently owns strict YAML parsing, input
Notarius's former configuration boundary owned strict YAML parsing, input
presence bookkeeping, defaults, normalization, environment overlays, and
configuration inspection. Those general-purpose responsibilities have grown
configuration inspection. Those general-purpose responsibilities had grown
alongside application-specific pipeline and module semantics.
ConfigKit v0.3.0 provides strict typed YAML loading, imports, configuration
@@ -47,8 +47,7 @@ boundary.
## Consequences
The implementation migrates configuration behavior in bounded increments, but
the released application will have one ConfigKit-backed loader and one version
5 contract. Operator documentation and maintained examples must move with the
cutover. ConfigKit metadata is retained only at the configuration publication
boundary; its types do not become module or runtime pipeline interfaces.
The released application has one ConfigKit-backed loader and one version 5
contract. Operator documentation and maintained examples move with the cutover.
ConfigKit metadata is retained only at the configuration publication boundary;
its types do not become module or runtime pipeline interfaces.