Record the ConfigKit configuration ownership boundary
This commit is contained in:
66
docs/adr/0003-assign-configuration-ownership.md
Normal file
66
docs/adr/0003-assign-configuration-ownership.md
Normal file
@@ -0,0 +1,66 @@
|
||||
# 0003. Assign configuration ownership
|
||||
|
||||
## Status
|
||||
|
||||
Accepted
|
||||
|
||||
## Date
|
||||
|
||||
2026-10-05
|
||||
|
||||
## Context
|
||||
|
||||
Narratio uses ConfigKit to assemble typed configuration. Earlier integration
|
||||
code added source-authoring acceptance checks and cached field ownership.
|
||||
ConfigKit's native composition, inheritance, presence, and provenance APIs now
|
||||
provide the information needed for loading and operator inspection.
|
||||
|
||||
The ConfigKit adoption establishes a responsibility boundary around the
|
||||
effective configuration. This record captures the rationale for that boundary.
|
||||
The [architecture policy](../policy/architecture.md#configuration) owns the
|
||||
normative requirements, and the [configuration reference](../config.md) owns
|
||||
the operator-facing contract.
|
||||
|
||||
## Decision
|
||||
|
||||
Narratio receives a final configuration from ConfigKit. ConfigKit owns the
|
||||
process of resolving the configuration prior to that handoff. Narratio owns
|
||||
domain validation and application use of the configuration after that handoff.
|
||||
|
||||
ConfigKit owns input loading, source composition, sibling inheritance, presence
|
||||
tracking, typed secret resolution, and native provenance.
|
||||
|
||||
Narratio owns configuration-domain meaning, application-specific defaults and
|
||||
derivation, path resolution, and fail-fast validation of effective domain values.
|
||||
Narratio expresses these operations through ConfigKit's supported callbacks and
|
||||
the application resolution steps appropriate to its schema.
|
||||
|
||||
Narratio uses ConfigKit's public presence and metadata APIs as intended.
|
||||
Operator inspection exposes native sources, effective origins, and historical
|
||||
definition evidence. Narratio adds the derivation context for generated
|
||||
artifacts and campaign-owned party data.
|
||||
|
||||
Structural acceptance follows ConfigKit's loading rules. Domain acceptance
|
||||
follows Narratio's validation of the effective configuration. Contributor count
|
||||
and source history serve operator inspection.
|
||||
|
||||
## Alternatives Considered
|
||||
|
||||
- Retain Narratio-owned source-authoring checks and cached provenance. This
|
||||
preserves the earlier implementation but creates overlapping responsibilities
|
||||
and additional maintenance when ConfigKit's composition features evolve.
|
||||
- Consume typed configuration alone. This produces a smaller integration but
|
||||
discards useful presence information and native provenance needed for
|
||||
defaults and operator inspection.
|
||||
|
||||
## Consequences
|
||||
|
||||
ConfigKit upgrades carry responsibility for structural configuration semantics.
|
||||
Narratio integration tests cover effective domain outcomes, presence-sensitive
|
||||
defaults, safe credential projections, and useful operator inspection.
|
||||
|
||||
Composite definitions can have several contributors. Inspection presents that
|
||||
evidence alongside Narratio's generated-artifact context.
|
||||
|
||||
Configuration assembly and provenance have one library owner. Narratio's
|
||||
integration remains focused on application meaning and runtime preparation.
|
||||
Reference in New Issue
Block a user