1.5 KiB
ConfigKit Integration
Notarius application configuration uses
go.maximumdirect.net/configkit
at v1.2.0 for source selection, imports, overlays, identified collections,
inheritance, explicit overrides, diagnostics, and frozen inspection. Imports
and inheritance precede typed decoding; CLI assignments follow decoding and
precede application resolution. Notarius does not repeat source composition.
Notarius supplies the document schema, defaults, normalization, validation,
and the step identity registration. It owns runtime conversion and subsequent
catalog-dependent pipeline resolution. LoadSource receives the CLI's chosen
source; retained main-source evidence supplies the selected path. See
Configuration for the operator contract and the pinned
upstream consumer guide
and configuration contract.
PromptKit v0.12.0 separately retains old-path ConfigKit v0.5.0 for its exposed source and inspection types. The two module identities share YAML v4.0.0-rc.6; their named types remain inside their owning boundaries. See the PromptKit integration and attribution.