diff --git a/docs/adr/0003-assign-configuration-ownership.md b/docs/adr/0003-assign-configuration-ownership.md index 77de1e3..829ad20 100644 --- a/docs/adr/0003-assign-configuration-ownership.md +++ b/docs/adr/0003-assign-configuration-ownership.md @@ -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. diff --git a/docs/policy/architecture.md b/docs/policy/architecture.md index 75f513c..b44c41d 100644 --- a/docs/policy/architecture.md +++ b/docs/policy/architecture.md @@ -2,7 +2,7 @@ **Base Policy Version:** 1.3 -**Last Updated**: 2026-11-17 +**Last Updated**: 2026-11-19 **Upstream Source**: https://gitea.maximumdirect.net/eric/policy/src/commit/593c9b52273c5c879785ae9e995d21026df467b4/docs/policy/architecture.md @@ -52,7 +52,7 @@ their domains: - Notarius extracts validated structured artifact bundles; and - Scriptorium executes prompts and produces configured artifacts. -Narratio owns orchestration, configuration resolution, session and run state, +Narratio owns orchestration, configuration interpretation, session and run state, artifact and path modeling, manifest persistence, stage sequencing, resume, restore, cleanup gates, and publish semantics. External contracts are defined in the [integration documentation](../integrations/). @@ -73,7 +73,7 @@ itself an architectural goal. ## Ownership And Dependency Direction -The application boundary owns command dispatch, configuration selection, +The application boundary owns command composition, configuration selection, production composition, session locking, and top-level lifecycle. It may depend on concrete implementations to assemble a run. @@ -172,10 +172,19 @@ or other non-regular conflict into a successful restore. ## Configuration -Configuration is strict, explicit, centralized, and operator-oriented. ConfigKit -owns input loading, assembly, sibling inheritance, presence tracking, typed -secrets, and provenance. Narratio owns configuration-domain meaning and -fail-fast validation of the effective configuration. +Configuration ownership follows +[ADR 0003](../adr/0003-assign-configuration-ownership.md): + +- ConfigKit owns configuration policy and resolution through the final handoff. + Narratio supplies its schema, defaults, and configuration rules through + supported extension points. The completed ConfigKit result is authoritative. +- Narratio consumes that result without mutation and derives separate domain + objects. It must not construct a replacement effective configuration. +- CommandKit owns CLI mechanics and presentation; `ckconfig` exposes ConfigKit + inspection. Narratio supplies selection and acquisition wiring through native + adapters without changing upstream semantics or substituting inspection views. + +Missing configuration or inspection capabilities are addressed upstream. - YAML decoding rejects unknown fields. - Defaults are centralized and testable. @@ -183,14 +192,10 @@ fail-fast validation of the effective configuration. values remain present and are evaluated by Narratio's domain rules. - Validation rejects invalid configuration before stage execution where practical. -- Local document imports and one selected pipeline overlay resolve through - the configuration owner; commands do not implement their own merge rules. -- Native ConfigKit metadata and supported resolution callbacks provide presence, - inheritance, and provenance information without a parallel loading or - ownership system. -- Canonical party rosters are campaign-owned. Their derived players projection - and concrete character-family artifacts are resolved before runtime stages - or adapters receive configuration. +- ConfigKit resolves local imports and the selected pipeline overlay. +- Canonical party rosters are campaign-owned inputs. Narratio derives players + projections and concrete character-family artifacts as separate domain + objects before execution, without modifying configuration. - Resume uses stage- or artifact-owned semantic evidence for observable result-affecting configuration; overlay identity and an effective digest are provenance, never blanket cache keys. diff --git a/docs/roadmap/commandkit-notepad.md b/docs/roadmap/commandkit-notepad.md index 0a7529b..69f631b 100644 --- a/docs/roadmap/commandkit-notepad.md +++ b/docs/roadmap/commandkit-notepad.md @@ -558,9 +558,9 @@ checks and detailed implementation sequencing remain preparation work for the roadmap and subsequent plan. Release version selection remains deferred to release preparation. -The next discussion is whether and how to crystallize the agreed configuration -ownership boundary in an ADR. The boundary is settled; an ADR has not yet been -prepared. +The configuration ownership boundary is recorded in +[ADR 0003](../adr/0003-assign-configuration-ownership.md). Roadmap consolidation +is the next planning step. ## Discussion and decision record