All checks were successful
ci/woodpecker/push/verify Pipeline was successful
39 lines
1.3 KiB
Markdown
39 lines
1.3 KiB
Markdown
# 0003. Assign configuration ownership
|
|
|
|
## Status
|
|
|
|
Accepted
|
|
|
|
## Date
|
|
|
|
2026-11-19
|
|
|
|
## Context
|
|
|
|
Configuration loading, inspection, and domain execution need explicit ownership
|
|
so that effective configuration has one authority.
|
|
|
|
## Decision
|
|
|
|
- **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
|
|
|
|
Post-handoff configuration resolution and custom inspection projections are
|
|
rejected because they create competing configuration authorities.
|
|
|
|
## Consequences
|
|
|
|
Domain catalogs and plans remain separate from native configuration inspection.
|
|
Missing configuration or inspection capabilities are addressed upstream.
|