Document ConfigKit integration and dependency attribution

This commit is contained in:
2026-11-17 20:58:22 +00:00
parent 244f258413
commit 74e0f454e9
8 changed files with 65 additions and 27 deletions

View File

@@ -1,19 +1,21 @@
# ConfigKit Integration
Notarius uses the public root package
[`gitea.maximumdirect.net/eric/ConfigKit`](https://gitea.maximumdirect.net/eric/ConfigKit)
at v0.5.0 for version 5 configuration acquisition, imports, overlays, explicit
overrides, native sibling inheritance, diagnostics, and safe inspection
rendering. ConfigKit composes source precedence and inheritance before typed
decoding; Notarius does not perform a second inheritance merge.
Notarius application configuration uses
[`go.maximumdirect.net/configkit`](https://forge.maximumdirect.net/base-layer/configkit/src/commit/c1c7e87f2cdf77a0cbf3327831ac05578e756b9e)
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 owns the typed document, domain defaults and validation, runtime
conversion, catalog-dependent pipeline resolution, source-aware configured
paths, and command discovery. It uses only ConfigKit's public path, result,
diagnostic, and resolution-source APIs. Upstream documentation owns general
ConfigKit semantics; [Configuration](../config.md) owns Notarius's file and
operator contract. See the pinned upstream [v0.5.0 release notes](https://gitea.maximumdirect.net/eric/ConfigKit/src/commit/dc09959cca4e105f49ec316c6d4ba585bd2340bd/docs/releases/v0.5.0.md)
and [configuration contract](https://gitea.maximumdirect.net/eric/ConfigKit/src/commit/dc09959cca4e105f49ec316c6d4ba585bd2340bd/docs/config.md).
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](../config.md) for the operator contract and the pinned
upstream [consumer guide](https://forge.maximumdirect.net/base-layer/configkit/src/commit/c1c7e87f2cdf77a0cbf3327831ac05578e756b9e/docs/consumers/README.md)
and [configuration contract](https://forge.maximumdirect.net/base-layer/configkit/src/commit/c1c7e87f2cdf77a0cbf3327831ac05578e756b9e/docs/config.md).
See the canonical [ConfigKit attribution](../oss/attribution.md#configkit) for
its license and notices.
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](pkg-promptkit.md) and [attribution](../oss/attribution.md#configkit).