Document native configuration inheritance

This commit is contained in:
2026-10-04 15:25:48 +00:00
parent 39af6ef941
commit f1f71d8cdf
7 changed files with 75 additions and 13 deletions

View File

@@ -172,15 +172,22 @@ or other non-regular conflict into a successful restore.
## Configuration
Configuration is strict, explicit, centralized, and operator-oriented.
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.
- YAML decoding rejects unknown fields.
- Defaults are centralized and testable.
- Empty configured values do not silently replace meaningful defaults.
- Defaults apply only to absent fields. Explicit false, zero, empty, and null
values remain present and are evaluated by Narratio's domain rules.
- Validation rejects invalid configuration before stage execution where
practical.
- Root-owned imports and one selected overlay resolve deterministically 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.