Align configuration ownership policy with ADR 0003
All checks were successful
ci/woodpecker/push/verify Pipeline was successful

This commit is contained in:
2026-11-20 00:46:06 +00:00
parent 7ee362f1c3
commit 7cc877ea7f
3 changed files with 41 additions and 64 deletions

View File

@@ -6,61 +6,33 @@ Accepted
## Date
2026-10-05
2026-11-19
## 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.
Configuration loading, inspection, and domain execution need explicit ownership
so that effective configuration has one authority.
## 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.
- **ConfigKit owns configuration policy and resolution through the final
handoff.** Narratio supplies its schema, defaults, and configuration rules
through ConfigKit's supported extension points. The completed ConfigKit
result is authoritative.
- **Narratio owns domain interpretation and execution.** It consumes the
completed configuration without mutation and produces separate domain
objects. It must not construct a replacement effective configuration.
- **CommandKit owns CLI mechanics and presentation; `ckconfig` exposes
ConfigKit's inspection features.** Narratio supplies selection and acquisition
wiring and exposes those features through native adapters, without altering
their semantics or substituting its own inspection views.
## 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.
Post-handoff configuration resolution and custom inspection projections are
rejected because they create competing configuration authorities.
## 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.
Domain catalogs and plans remain separate from native configuration inspection.
Missing configuration or inspection capabilities are addressed upstream.