Prepare ConfigKit v0.5.0 release

.gitignore

@@ -25,6 +25,9 @@ go.work.sum
 # env file
 .env
 
+# Local codebase-memory tooling artifacts
+/.codebase-memory/
+
 # ---> Linux
 *~
 
@@ -81,4 +84,3 @@ Temporary Items
 .history/
 
 # Built Visual Studio Code Extensions
-*.vsix

AGENTS.md

@@ -1,2 +1,25 @@
-Please review `docs/development.md` for initial orientation in this repository
-and follow its task-specific reading guide.
+<!-- codebase-memory-mcp:start -->
+# Codebase Knowledge Graph (codebase-memory-mcp)
+
+This project uses codebase-memory-mcp to maintain a knowledge graph of the codebase.
+ALWAYS prefer MCP graph tools over grep/glob/file-search for code discovery.
+
+## Priority Order
+1. `search_graph` — find functions, classes, routes, variables by pattern
+2. `trace_path` — trace who calls a function or what it calls
+3. `get_code_snippet` — read specific function/class source code
+4. `query_graph` — run Cypher queries for complex patterns
+5. `get_architecture` — high-level project summary
+
+## When to fall back to grep/glob
+- Searching for string literals, error messages, config values
+- Searching non-code files (Dockerfiles, shell scripts, configs)
+- When MCP tools return insufficient results
+<!-- codebase-memory-mcp:end -->
+
+Start with `docs/development.md` for orientation and use its policy reading guide
+to select the policies applicable to the task. Do not read the entire suite by
+default.
+
+Read and follow `docs/policy/agents.md` before recommending, planning, or
+implementing repository changes.

COPYRIGHT

@@ -0,0 +1,25 @@
+ConfigKit
+
+Copyright (C) 2026 Eric Rakestraw
+
+SPDX-License-Identifier: LGPL-3.0-or-later
+
+This library is free software: you can redistribute it and/or modify it
+under the terms of the GNU Lesser General Public License as published by
+the Free Software Foundation, either version 3 of the License, or
+(at your option) any later version.
+
+The GNU Lesser General Public License version 3 and its incorporated
+GNU General Public License version 3 text are provided in LICENSE.
+
+This library is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU Lesser General Public License for more details.
+
+Third-party code and assets are subject to their respective license terms.
+
+Policy documents adapted from Standard Repository Policies, the root AGENTS.md
+orientation, and the Policy Reading Guide in docs/development.md remain licensed
+under CC-BY-SA-4.0. See docs/oss/attribution.md for the affected material,
+upstream credit, and license links.

README.md

@@ -2,9 +2,75 @@
 
 An opinionated Go library for applications that use YAML configuration files.
 
-ConfigKit is in pre-implementation. This repository currently contains its design
-and contributor policies; no usable Go library has been implemented yet.
+Linux is release-validated; macOS support is best-effort. See the
+[platform support policy](docs/policy/release.md#platform-support) for details.
 
-The [initial target design](docs/roadmap/initial.md) describes planned behavior.
-The [implementation plan](docs/roadmap/implementation.md) owns the pending stages.
-See the [development guide](docs/development.md) for repository orientation.
+ConfigKit's simple `Load` accepts one strict YAML source (or explicit
+defaults-only input). `LoadLayered` additionally combines explicit lower-priority
+source groups with an independently selected main input. Sources can be host
+files, native `fs.FS` files, labeled bytes or readers, or snapshotted mappings.
+Enabled path and glob imports compose strictly within their group; precedence
+between groups combines mappings recursively. Both entry points return a complete,
+validated configuration with detached metadata and safe diagnostics.
+Applications may perform audited defaulting and normalization through a resolver,
+then report domain errors and warnings through read-only semantic validation. Secret
+tags and a path predicate drive deterministic redacted effective YAML. Typed secret
+references resolve environment names before validation, and explicit
+secrets-directory bootstrap is available as a separate startup operation. Explicit
+CLI override records apply above overlays. Value explanation is available through
+detached structured records and deterministic redacted output. Built-in
+`extends` relationships let a mapping inherit from a named sibling during the
+same load, retaining explicit presence and source/derivation history.
+
+```go
+type Config struct {
+    Enabled bool `yaml:"enabled"`
+    Workers int  `yaml:"workers"`
+}
+
+func ReadConfig(path string) (Config, error) {
+    result, err := configkit.Load[Config](configkit.File(path))
+    if err != nil {
+        return Config{}, err
+    }
+    return result.Config, nil
+}
+```
+
+## Design philosophy
+
+ConfigKit favors one coherent, predictable configuration model over flexibility
+for reproducing each consumer's conventions. Its goal is to let applications
+load once, inspect where final values came from, and distinguish explicit values
+from omissions with minimal configuration bookkeeping. Applications retain their
+domain rules and execution responsibilities.
+
+Loading is synchronous and complete on return. Applications normally load once
+near startup and then use the final configuration and metadata; ConfigKit stays
+inactive until explicitly called again. Applications may initiate additional
+loads as needed. See the [loading lifecycle](docs/config.md#completion-and-resource-lifetime)
+for completion and ownership details.
+
+Within a configuration tier, independent contributions compose strictly: shared
+mappings combine, while overlapping non-mapping definitions are errors. Between
+precedence tiers, mappings combine recursively, retaining omitted lower-priority
+children; other values replace lower-priority values. The main document and its
+imports form one strictly composed tier. Explicit underlay groups sit below it
+and above typed defaults; a selected overlay and explicit CLI overrides sit
+above it. The [configuration contract](docs/config.md#strict-document-composition)
+owns the detailed combination rules and input-specific constraints.
+
+The [architecture goals](docs/policy/architecture.md#success-criteria) explain
+these priorities and how genuine new needs can justify extending the shared
+model. The [deferred scope](docs/roadmap/deferred.md) records deliberate exclusions.
+
+The [configuration contract](docs/config.md) describes implemented behavior. The
+[consumer adoption guide](docs/consumers/README.md) provides maintained simple
+native-filesystem, layered, and sibling-inheritance examples alongside the migration shapes.
+See the [development guide](docs/development.md) for repository orientation and the
+[release procedure](docs/release.md) for maintainer-only candidate and publication
+steps.
+
+ConfigKit code is licensed under the [LGPL v3.0 or later](COPYRIGHT).
+
+[Open Source attribution notices](docs/oss/attribution.md) are available.

conversion.go

@@ -0,0 +1,153 @@
+package configkit
+
+import "gitea.maximumdirect.net/eric/ConfigKit/internal/engine"
+
+func fromEngineLocation(value engine.Location) Location {
+	return Location{SourceID: value.SourceID, Line: value.Line, Column: value.Column}
+}
+func toEngineLocation(value Location) engine.Location {
+	return engine.Location{SourceID: value.SourceID, Line: value.Line, Column: value.Column}
+}
+func fromEngineLocationPointer(value *engine.Location) *Location {
+	if value == nil {
+		return nil
+	}
+	result := fromEngineLocation(*value)
+	return &result
+}
+func toEngineLocationPointer(value *Location) *engine.Location {
+	if value == nil {
+		return nil
+	}
+	result := toEngineLocation(*value)
+	return &result
+}
+func fromEngineLocations(values []engine.Location) []Location {
+	if values == nil {
+		return nil
+	}
+	result := make([]Location, len(values))
+	for i := range values {
+		result[i] = fromEngineLocation(values[i])
+	}
+	return result
+}
+func toEngineLocations(values []Location) []engine.Location {
+	if values == nil {
+		return nil
+	}
+	result := make([]engine.Location, len(values))
+	for i := range values {
+		result[i] = toEngineLocation(values[i])
+	}
+	return result
+}
+func fromEngineSourceInfo(value engine.SourceInfo) SourceInfo {
+	return SourceInfo{ID: value.ID, Label: value.Label, Path: value.Path, Layer: Layer(value.Layer), Kind: SourceKind(value.Kind), UnderlayIndex: value.UnderlayIndex, ImportedFrom: fromEngineLocationPointer(value.ImportedFrom)}
+}
+func toEngineSourceInfo(value SourceInfo) engine.SourceInfo {
+	return engine.SourceInfo{ID: value.ID, Label: value.Label, Path: value.Path, Layer: engine.Layer(value.Layer), Kind: engine.SourceKind(value.Kind), UnderlayIndex: value.UnderlayIndex, ImportedFrom: toEngineLocationPointer(value.ImportedFrom)}
+}
+func fromEngineOrigin(value engine.Origin) Origin {
+	result := Origin{Layer: Layer(value.Layer), Locations: fromEngineLocations(value.Locations), Operation: ChangeKind(value.Operation)}
+	if value.Inheritance != nil {
+		result.Inheritance = make([]InheritanceStep, len(value.Inheritance))
+		for index, step := range value.Inheritance {
+			result.Inheritance[index] = InheritanceStep{
+				From: fromEnginePath(step.From), To: fromEnginePath(step.To), Reference: fromEnginePath(step.Reference),
+				Locations: fromEngineLocations(step.Locations),
+			}
+		}
+	}
+	return result
+}
+func toEngineOrigin(value Origin) engine.Origin {
+	result := engine.Origin{Layer: engine.Layer(value.Layer), Locations: toEngineLocations(value.Locations), Operation: engine.ChangeKind(value.Operation)}
+	if value.Inheritance != nil {
+		result.Inheritance = make([]engine.InheritanceStep, len(value.Inheritance))
+		for index, step := range value.Inheritance {
+			result.Inheritance[index] = engine.InheritanceStep{
+				From: toEnginePath(step.From), To: toEnginePath(step.To), Reference: toEnginePath(step.Reference),
+				Locations: toEngineLocations(step.Locations),
+			}
+		}
+	}
+	return result
+}
+func fromEngineDiagnostic(value engine.Diagnostic) Diagnostic {
+	return Diagnostic{Code: Code(value.Code), Severity: Severity(value.Severity), Path: fromEnginePath(value.Path), Message: value.Message, Primary: fromEngineLocationPointer(value.Primary), Related: fromEngineLocations(value.Related)}
+}
+func toEngineDiagnostic(value Diagnostic) engine.Diagnostic {
+	return engine.Diagnostic{Code: engine.Code(value.Code), Severity: engine.Severity(value.Severity), Path: toEnginePath(value.Path), Message: value.Message, Primary: toEngineLocationPointer(value.Primary), Related: toEngineLocations(value.Related)}
+}
+func toEngineDiagnostics(values []Diagnostic) []engine.Diagnostic {
+	if values == nil {
+		return nil
+	}
+	result := make([]engine.Diagnostic, len(values))
+	for i := range values {
+		result[i] = toEngineDiagnostic(values[i])
+	}
+	return result
+}
+func fromEngineFieldInfo(value engine.FieldInfo) FieldInfo {
+	return FieldInfo{Explicit: value.Explicit, Null: value.Null, Origin: fromEngineOrigin(value.Origin)}
+}
+func fromEngineChange(value engine.Change) Change {
+	result := Change{Path: fromEnginePath(value.Path), Origin: fromEngineOrigin(value.Origin), Reasons: append([]string(nil), value.Reasons...)}
+	if value.Previous != nil {
+		result.Previous = make([]Origin, len(value.Previous))
+		for i := range value.Previous {
+			result.Previous[i] = fromEngineOrigin(value.Previous[i])
+		}
+	}
+	if value.Dependencies != nil {
+		result.Dependencies = make([]Path, len(value.Dependencies))
+		for i := range value.Dependencies {
+			result.Dependencies[i] = fromEnginePath(value.Dependencies[i])
+		}
+	}
+	return result
+}
+
+func fromEngineValueSnapshot(value engine.ValueSnapshot) ValueSnapshot {
+	return ValueSnapshot{Present: value.Present, Redacted: value.Redacted, YAML: value.YAML}
+}
+
+func fromEngineValueChange(value engine.ValueChange) ValueChange {
+	result := ValueChange{
+		Before:  fromEngineValueSnapshot(value.Before),
+		After:   fromEngineValueSnapshot(value.After),
+		Origin:  fromEngineOrigin(value.Origin),
+		Reasons: append([]string(nil), value.Reasons...),
+	}
+	if value.Dependencies != nil {
+		result.Dependencies = make([]Path, len(value.Dependencies))
+		for index := range value.Dependencies {
+			result.Dependencies[index] = fromEnginePath(value.Dependencies[index])
+		}
+	}
+	return result
+}
+
+func fromEngineExplanation(value engine.Explanation) Explanation {
+	result := Explanation{
+		Path:      fromEnginePath(value.Path),
+		Effective: fromEngineValueSnapshot(value.Effective),
+		Origin:    fromEngineOrigin(value.Origin),
+	}
+	if value.History != nil {
+		result.History = make([]ValueChange, len(value.History))
+		for index := range value.History {
+			result.History[index] = fromEngineValueChange(value.History[index])
+		}
+	}
+	if value.SecretReference != nil {
+		result.SecretReference = &SecretReferenceInfo{Name: value.SecretReference.Name}
+	}
+	return result
+}
+
+func fromEngineSecretFileResult(value engine.SecretFileResult) SecretFileResult {
+	return SecretFileResult{Name: value.Name, Path: value.Path, Status: SecretFileStatus(value.Status), ExistingEmpty: value.ExistingEmpty}
+}

diagnostic.go

@@ -0,0 +1,57 @@
+package configkit
+
+import (
+	"io"
+
+	"gitea.maximumdirect.net/eric/ConfigKit/internal/engine"
+)
+
+// LoadError reports safe structured diagnostics for a failed configuration load.
+// It intentionally does not expose or unwrap parser and application errors.
+type LoadError struct{ value *engine.LoadError }
+
+// Error implements error without rendering diagnostic messages or input values.
+func (e *LoadError) Error() string {
+	if e == nil || e.value == nil {
+		return "configkit: configuration load failed"
+	}
+	return e.value.Error()
+}
+
+// Diagnostics returns a deep copy of the error's canonical diagnostics.
+func (e *LoadError) Diagnostics() []Diagnostic {
+	if e == nil || e.value == nil {
+		return nil
+	}
+	values := e.value.Diagnostics()
+	if values == nil {
+		return nil
+	}
+	result := make([]Diagnostic, len(values))
+	for i := range values {
+		result[i] = fromEngineDiagnostic(values[i])
+	}
+	return result
+}
+
+// Sources returns a deep copy of sources discovered before loading failed.
+func (e *LoadError) Sources() []SourceInfo {
+	if e == nil || e.value == nil {
+		return nil
+	}
+	values := e.value.Sources()
+	if values == nil {
+		return nil
+	}
+	result := make([]SourceInfo, len(values))
+	for i := range values {
+		result[i] = fromEngineSourceInfo(values[i])
+	}
+	return result
+}
+
+// WriteDiagnostics writes diagnostics in canonical order. It escapes terminal
+// control characters and propagates writer errors, including short writes.
+func WriteDiagnostics(output io.Writer, diagnostics []Diagnostic) error {
+	return engine.WriteDiagnostics(output, toEngineDiagnostics(diagnostics))
+}

doc.go

@@ -0,0 +1,9 @@
+// Package configkit provides deterministic, application-owned configuration
+// loading for Go programs.
+//
+// Load supports file, byte, reader, and explicit no-input sources with strict YAML,
+// typed defaults, imports, overlays, CLI overrides, schema-version checks, detached
+// metadata, recorded application resolution, typed secret references, safe effective
+// rendering, read-only semantic validation, and structured load errors. The
+// configuration contract is documented in docs/config.md.
+package configkit

docs/adr/0001-separate-composition-and-overlay.md

@@ -20,8 +20,8 @@ Use distinct strict-composition and intentional-overlay operations. Composition
 rejects conflicting definitions; overlay provides explicit precedence. Keep the
 operations opinionated rather than adding arbitrary per-field merge strategies.
 The [architecture policy](../policy/architecture.md) owns the governing boundary;
-the [target design](../roadmap/initial.md#composition-and-overlay) owns the planned
-operation table until its current contract lands.
+the [current configuration contract](../config.md#strict-document-composition) owns
+the operation table and selected-profile overlay behavior.
 
 ## Alternatives considered
 

docs/adr/0002-own-yaml-semantics.md

@@ -20,7 +20,8 @@ ConfigKit defines its supported YAML policy and keeps parser integration private
 Application types and diagnostics must not require parser-specific public types.
 Use a small internal boundary rather than a general parser/provider framework.
 The [architecture policy](../policy/architecture.md) owns this constraint; the
-[target design](../roadmap/initial.md#yaml-and-scalar-policy) owns planned syntax.
+[current YAML document](../config.md#yaml-documents) and
+[scalar](../config.md#scalars) contracts own the implemented syntax.
 
 ## Alternatives considered
 

docs/adr/0003-preserve-presence-and-resolution-history.md

@@ -22,8 +22,9 @@ values. Keep application defaults and normalization application-owned, but recor
 resolution changes so final inspection and metadata describe the actual resolved
 snapshot. Do not promise language-enforced immutability of exported Go values.
 The [architecture policy](../policy/architecture.md) owns these invariants; the
-[target design](../roadmap/initial.md#recorded-resolution-and-validation) owns the
-planned recording mechanism and ownership semantics.
+[current resolution contract](../config.md#recorded-application-resolution) and
+[ownership contract](../config.md#typed-projection-and-ownership) own the implemented
+recording mechanism and ownership semantics.
 
 ## Alternatives considered
 

docs/adr/0004-secret-references-and-explicit-bootstrap.md

@@ -21,8 +21,9 @@ Existing environment variables win even when empty. Report skipped files and
 partial failures without values. Keep bootstrap provenance separate from later
 lookup provenance rather than imply an unchanged environment between calls.
 General environment-variable configuration overlays are not on the roadmap.
-The [feature roadmap](../roadmap/initial.md#secret-references-and-explicit-bootstrap)
-owns the unimplemented contract; stages remain in the implementation plan.
+The [current reference contract](../config.md#typed-secret-references) and
+[bootstrap contract](../config.md#explicit-secrets-directory-bootstrap) own the
+implemented behavior.
 
 ## Alternatives considered
 

docs/adr/0005-explicit-overrides-and-safe-explanation.md

@@ -19,8 +19,9 @@ node tree before typed decoding, retaining the existing parser adapter boundary.
 Recorded domain resolution follows input selection. Provide safe structured
 historical values and an explanation renderer in the initial release, building
 on ADR 0003's presence and audited resolution decision. Applications own commands.
-The [feature roadmap](../roadmap/initial.md#cli-overrides) owns the exact override
-contract and [explanation contract](../roadmap/initial.md#historical-value-explanation).
+The [current override contract](../config.md#explicit-cli-overrides) and
+[explanation contract](../config.md#historical-value-explanation) own the implemented
+behavior.
 
 ## Alternatives considered
 

docs/adr/0006-public-facade.md

@@ -0,0 +1,61 @@
+# ADR 0006: Keep the public facade root-owned
+
+## Status
+
+Accepted and implemented on 2026-09-12.
+
+## Date
+
+2026-09-12
+
+## Context
+
+The root `configkit` package formerly combined the supported consumer API with
+loading, decoding, inspection, and rendering machinery. That made ordinary
+consumer navigation harder and risked exposing implementation details through
+future public declarations. Moving files alone would not preserve the identity,
+method sets, callbacks, ownership rules, or reflection-sensitive behavior of the
+root's public types.
+
+## Decision
+
+Keep `configkit` as the sole supported consumer import path and keep all public
+named types defined there. Lifecycle machinery lives in a cohesive
+`internal/engine`; the root facade holds private engine state and forwards
+deliberately selected methods. The dependency direction is root to engine and
+its supporting internal packages. Internal production packages do not import the
+root package.
+
+The facade will use root-owned wrappers and explicit private conversions. It
+will not use public aliases to engine types, anonymous embedding that promotes
+engine methods, public engine types in signatures or fields, or public bridge
+methods. Existing document and YAML boundaries remain intact.
+
+The migration used a temporary internal candidate facade while the unchanged root
+remained the only production entry point. That duplication was a bounded
+relocation mechanism, not a second supported package, feature path, or runtime
+selection mechanism; the final cutover removed it and the old root implementation.
+
+The [architecture policy](../policy/architecture.md#public-api-and-dependency-direction)
+owns the binding boundary. The [component overview](../internal/overview.md)
+describes the implemented layout; the [development guide](../development.md)
+locates the completed roadmap and implementation history.
+
+## Alternatives considered
+
+- Alias root types to engine types: reduces forwarding, but makes the engine's
+  exported method set and type ownership part of the consumer API.
+- Keep all machinery in the root package: avoids migration work, but leaves the
+  public boundary difficult to navigate and easy to expand accidentally.
+- Introduce a generic adapter or registration framework: could reduce some
+  handwritten conversions, but adds machinery and obscures the ownership rules
+  this boundary needs to preserve.
+
+## Consequences
+
+The refactor carries explicit forwarding and conversion work, especially for
+callbacks, detached records, source ownership, frozen inspection, and the
+exact-type secret bridge. Public compatibility must be verified by behavior and
+external-package evidence rather than inferred from package names. Internal
+exports remain implementation surfaces, and the completed architecture will
+have one engine and one root facade.

docs/adr/0007-source-backed-underlays.md

@@ -0,0 +1,118 @@
+# ADR 0007: Add Source-Backed Underlays with Consistent Recursive Precedence
+
+## Status
+
+Proposed draft for review. Completed planning and remediation records are
+preserved in Git history at `b604aa1` under `docs/roadmap/`; the
+[configuration contract](../config.md#layered-loading) owns current behavior.
+
+This extends [ADR 0001](0001-separate-composition-and-overlay.md) and preserves
+its distinction between strict composition and intentional overlay.
+
+## Date
+
+2026-09-29
+
+## Context
+
+Configuration-backed defaults provide lower-priority settings that applications
+can override. These sources carry imports, locations, and relative-resource
+contexts. Integrating them into ConfigKit's loading lifecycle gives their values
+the same presence tracking and inspectable provenance as other configuration
+inputs.
+
+The [architecture goals](../policy/architecture.md#success-criteria) prioritize
+one coherent, predictable configuration model with consistent rules across
+source representations and loading interfaces. Consumers should load once,
+receive a complete validated configuration, and inspect its final values' origins.
+Reducing integration code is important subject to those principles.
+
+## Decision
+
+### Add underlays to the existing precedence model
+
+Introduce explicitly supplied source-backed underlays between typed defaults
+and main configuration. The proposed precedence, from lowest to highest, is:
+
+**Typed application defaults < source underlays < strictly composed main
+configuration < selected overlay < explicit CLI overrides.**
+
+Typed defaults remain the Go-value baseline. Underlays supply lower-priority
+configuration with source provenance and, where applicable, imports and resource
+context. This ordering describes value precedence; typed defaults fill fields
+absent from the assembled input under the existing defaulting rules.
+
+Preserve strict composition of the main document and its imports before applying
+the resulting configuration over underlays. Independent contributions within an
+underlay tier also compose strictly. Explicitly ordered tiers express intentional
+precedence. Strict composition reports conflicting contributions within each tier.
+
+Across precedence tiers, reuse the existing recursive mapping-overlay semantics.
+Omitted children retain lower-priority input; existing scalar, sequence, null,
+and cross-kind replacement semantics remain unchanged. Reusing these operations
+keeps the combination rules consistent across the loading model.
+
+### Keep source representation separate from composition semantics
+
+Native `fs.FS` and programmatic inputs join the shared loading model.
+Equivalent inputs using the same
+operation have the same presence and precedence semantics regardless of medium.
+Programmatic values enter directly as labeled configuration sources.
+
+Retain the contributing source's identity and resource context through layering.
+A retained underlay value keeps its originating source's resource context.
+Consumers remain responsible for opening and interpreting their domain resources
+under the supplied filesystem's lifetime and access semantics. Exact
+context-access and input APIs remain roadmap decisions.
+
+### Deliver one final configuration and its inspection metadata
+
+Assemble effective input, then run the typed loading lifecycle once for the load.
+Preserve explicit zero,
+false, empty, and null input versus omission through configuration and metadata
+together.
+
+Extend existing provenance and history through underlays, defaults, and recorded
+application resolution. The returned result includes the completed combination,
+defaulting, and provenance work. Domain resolution and validation
+remain application-owned within the recorded lifecycle, consistent with
+[ADR 0003](0003-preserve-presence-and-resolution-history.md).
+
+Preserve the existing opt-in schema-version ownership, path protections, and
+check timing before precedence
+assembly and typed decoding. The roadmap owns how layered input identifies that
+owner when version checking is configured.
+
+Favor near-linear processing in input, retained history, and output size through
+incremental assembly of load-owned state. This is an engineering objective
+subordinate to clarity and semantic consistency. Preserve the root-owned facade and
+private implementation boundary established by [ADR 0006](0006-public-facade.md).
+
+## Alternatives considered
+
+- **Leave bundled defaults to consumers.** Avoids extending loading, but makes
+  consumers reproduce merging, presence tracking, and provenance reconciliation.
+  It does not meet the goal of obtaining a complete configuration in one load.
+- **Offer recursive or atomic combination per layer.** Makes both behaviors
+  explicit and could serve more consumers, but expands the semantic surface and
+  its interactions with presence and provenance without a demonstrated need that
+  outweighs a single consistent rule. A future concrete requirement may justify
+  reconsideration; this feature does not add the option.
+- **Flatten all documents into last-wins layers.** Simplifies ordering but turns
+  accidental main/import conflicts into overrides, weakening the intentional
+  distinction established by ADR 0001.
+
+## Consequences
+
+Consumers gain source-backed defaults within the shared loading lifecycle.
+Strict contributions and intentional precedence remain distinct, with consistent
+combination rules across source media. Presence and provenance remain
+part of the same loading lifecycle as the final values.
+
+Higher-priority mappings retain omitted lower-priority children, so application
+validation assesses the final combined configuration.
+
+Implementation must integrate source context and underlay history into the shared
+engine with attention to assembly and history-retention costs. Current behavior
+documentation will change when the feature lands. The roadmap retains ownership
+of the remaining API decisions.

docs/adr/0008-complete-on-return-loading.md

@@ -0,0 +1,82 @@
+# ADR 0008: Synchronous, Complete-on-Return Configuration Loading
+
+## Status
+
+Proposed draft for review. The
+[configuration contract](../config.md#completion-and-resource-lifetime) describes
+the implemented loading lifecycle and
+[source resource contexts](../config.md#source-resource-contexts).
+
+## Date
+
+2026-09-29
+
+## Context
+
+Applications need a clear point at which configuration is ready for use.
+Completing configuration processing and inspection metadata together gives
+applications a coherent result whose values and origins agree. A bounded loading
+lifecycle also makes resource ownership and startup failures straightforward to
+reason about.
+
+ConfigKit's [architecture goals](../policy/architecture.md#success-criteria)
+emphasize complete configuration, inspectable provenance, predictable behavior,
+and minimal consumer bookkeeping. Applications own their execution lifecycle and
+the timing of configuration acquisition.
+
+## Decision
+
+Make loading a synchronous, complete-on-return operation. Within each load,
+ConfigKit completes input assembly, defaulting, typed decoding, configured
+application resolution, secret lookup, validation, and snapshotting before
+returning the final configuration and metadata. Reported failures return
+diagnostics and a nil result.
+
+Release all library-owned loading handles before returning on success or failure.
+The resulting configuration and metadata are independently usable, caller-owned
+data with a retained inspection snapshot. Caller-supplied readers and filesystems
+remain under caller ownership and lifetime control.
+
+After the call completes, ConfigKit remains inactive until explicitly invoked
+again. Applications normally load once at or near startup and may initiate
+additional loads when needed. Each load follows the same lifecycle and source
+reuse contracts. Inspection, rendering, and separately requested operations run
+in response to explicit application calls.
+
+For the planned resource-context capability, retain source context as passive
+information or a borrowed caller-supplied filesystem. Subsequent resource access
+acquires its own handles with explicit ownership. This preserves a clear boundary
+between configuration completion and application resource use.
+
+These choices give consumers one completion boundary for configuration and
+provenance, predictable resource lifetimes, and control over when ConfigKit runs.
+Application callbacks remain responsible for their own effects and resources.
+
+## Alternatives considered
+
+- **Background watching or refresh.** Can automate responses to source changes,
+  but adds scheduling, shutdown, publication, and resource-lifetime concerns to
+  the library. Explicit calls keep those responsibilities with the application.
+- **Lazy completion after return.** Can defer work until particular values are
+  used, but moves configuration failures into application execution and makes
+  the readiness of values and metadata harder to establish.
+- **Transactional atomic loading.** Could imply simultaneous observation of all
+  external inputs and rollback of callback effects. Filesystems, environment
+  variables, and application callbacks do not share a transaction mechanism.
+  Synchronous completion provides the required usable-result boundary without
+  promising those external guarantees.
+- **Retain loading handles in results.** Can preserve open filesystem access,
+  but gives configuration results an ongoing resource lifecycle and cleanup
+  obligation. Passive source context supports later explicit resource access
+  while keeping loading resources scoped to the load call.
+
+## Consequences
+
+Applications can treat successful return as the point at which the final
+configuration and its metadata are ready for use. Startup loading remains simple,
+and additional loads have an explicit application-owned trigger.
+
+Configuration inspection operates on retained data. Resource access observes the
+backing resource when explicitly requested and has its own failure and ownership
+boundary. Implementations of new source kinds and layering features preserve the
+same completion boundary, including cleanup on reported load failures.

docs/adr/0009-sibling-inheritance.md

@@ -0,0 +1,76 @@
+# ADR 0009: Resolve Sibling Inheritance After Source Assembly
+
+## Status
+
+Accepted and implemented. The [configuration contract](../config.md#sibling-inheritance)
+owns current behavior. The completed implementation plan is preserved in Git
+history at `83c59ea`.
+
+## Date
+
+2026-09-29
+
+## Context
+
+Named configuration mappings often share settings while retaining individual
+overrides. ConfigKit already distinguishes strict composition of independent
+source contributions from recursive overlay between explicit precedence tiers.
+Doing another untracked merge in applications would lose omission, source
+context, and historical explanation information. A shared structural operation
+must preserve the same presence and provenance model as the rest of loading.
+
+Inheritance also interacts with source precedence, nested namespaces, version
+ownership, and secrets. Resolving it before source assembly would validate
+superseded references and copy values that a later tier should replace. Fully
+resolving nested relationships inside a reusable parent would bind them to the
+wrong sibling scope when copied into a child.
+
+## Decision
+
+Reserve `extends` as a built-in input key on mappings. A string names one exact
+sibling mapping; null cancels the relationship. Complete source acquisition,
+strict composition, selected overlay, and CLI precedence first. Then resolve
+each effective relationship in the parser-independent document tree, before
+typed defaults and decoding. A child recursively overlays its own payload on
+its resolved parent using the existing mapping-combination rules. This creates
+neither a source tier nor a configurable merge strategy.
+
+Resolve enclosing sibling chains before nested relationships. Reuse memoized
+parent templates with unresolved nested instructions; evaluate those instructions
+at each destination. Preserve original source applications separately from
+structural transfer/control evidence. Effective origins carry concrete
+source-to-destination derivation, and inspection projects relevant inheritance
+events between source replay and typed reconciliation. Inherited input counts as
+explicit presence, while direct replacement retains its own effective origin.
+
+The existing main-input version check remains at its original point. Reject
+structural contributions or directive consumption affecting its protected path.
+Classify sensitivity at corresponding source and destination paths and retain
+historical redaction. Secret references remain unresolved input until the
+existing lookup point. Keep all machinery behind the root-owned public facade.
+
+## Alternatives considered
+
+- **Application-owned inheritance after `Load`.** Leaves every consumer to
+  recreate ordering, presence, provenance, error reporting, and redaction after
+  ConfigKit has already declared a result complete.
+- **Resolve each source before precedence assembly.** Makes superseded
+  references active and can copy a parent definition before higher-priority
+  input finishes changing it.
+- **Resolve nested relationships in a cached parent subtree.** Shares more
+  ready-made output but binds nested sibling lookups to the parent's scope,
+  giving incorrect values at a child destination.
+- **Registered collections, configurable keywords, or multiple-parent merge
+  modes.** Increase public setup and semantic branches without a requirement
+  that warrants diverging from one structural rule.
+
+## Consequences
+
+Consumers can load a configuration once and inspect direct, inherited,
+defaulted, and application-derived values through the existing result surfaces.
+`extends` is no longer an ordinary application field, so existing configurations
+using that key as data must migrate. Expanding many children can materialize
+substantially more output than the input contains; projection and retained-history
+budgets bound that work without charging copies as newly acquired sources.
+Applications still own domain validation, entry selection, and runtime resource
+use.

docs/config.md

@@ -0,0 +1,962 @@
+# Configuration Input Contract
+
+This document owns ConfigKit's currently implemented source-input, YAML syntax,
+schema, typed-decoding, loading, metadata, redaction, rendering, and ownership
+contracts. The parser, owned document representation, and decoder remain private
+behind the public loading lifecycle.
+
+## Sources
+
+ConfigKit exposes opaque sources through these constructors:
+
+| Constructor | Current contract |
+| --- | --- |
+| `File(path)` | Requires a nonempty path, opens a regular file for each consumption, and closes only the library-owned file handle. Missing, inaccessible, unreadable, directory, and other nonregular inputs fail. |
+| `NewFilesystem(label, filesystem).File(name)` | Borrows a caller-owned `fs.FS` under a safe nonempty display label. `name` must be a non-root slash-relative `fs.ValidPath`. Each load reopens the selected regular file; copies of the `Filesystem` preserve namespace identity. Separate constructors create separate namespaces even for the same label or filesystem. |
+| `Bytes(label, data)` | Requires a nonempty, non-secret diagnostic label and snapshots bytes during construction. Later caller mutation cannot affect the source. |
+| `Reader(label, input)` | Requires a nonempty, non-secret label and non-nil reader. The reader is claimed once across all copies of the source, consumed but never closed, and cannot be reused. |
+| `Mapping(label, values)` | Requires a safe nonempty label and a non-nil root `map[string]any`. Snapshots supported built-in values into an owned mapping document at construction; `{}` is valid. Constructor conversion failures become safe deferred diagnostics. |
+| `NoSource()` | Selects defaults-only loading, creates no source record, and marks no paths explicit. |
+
+The zero `Source` is invalid. Constructor argument failures are retained inside the
+opaque source and become safe structured diagnostics when the source is consumed.
+File and filesystem sources can observe changes between consumptions; byte and
+mapping sources cannot. Mapping accepts nil, built-in string, boolean, signed or
+unsigned integer, finite float, `[]any`, and `map[string]any` values recursively.
+Typed nil maps and slices represent explicit null; empty collections remain empty.
+Keys are sorted for stable provenance, integer decimal spelling stays exact, and
+cycles or unsupported types are rejected without exposing values. Mapping input
+uses the same directive and version rules as YAML, not CLI override restrictions.
+
+Each source is limited to 8 MiB. A load using imports or an active overlay is limited
+to 64 MiB across all accepted sources, 1,024 accepted sources, 64 active import
+edges, and 1,000,000 input nodes in aggregate. Glob expansion separately permits
+1,000,000 visited directory entries, including nonmatches. Reads request at most the
+remaining allowance plus one byte so excess data is rejected rather than silently
+truncated. Data returned together with a read error is not accepted as partial input.
+For mapping sources, key and string bytes use the same accounting as programmatic
+overrides, and the converted tree uses the same node and depth bounds.
+
+## Single-source loading
+
+`Load[T](source, options...)` accepts zero or one `Options[T]`. The configuration
+root `T` must satisfy the application schema contract below. With no options it
+starts from the Go zero value. A `Definition[T].Defaults` factory, when supplied,
+runs exactly once after successful source parsing, schema construction, optional
+schema-version checking, and selected-overlay loading. Its result is detached before
+input is applied. Resolver-provided mutable values are detached before secret lookup
+and validation, and a final detached copy prevents equal-valued aliases introduced
+by validators from escaping into the returned configuration. The publication copy
+preserves already validated secret state without rereading the environment.
+
+The current lifecycle is:
+
+```text
+validate options → parse the selected source → traverse/compose enabled imports
+  → build schema → check the optional application version → apply a selected overlay
+  → apply explicit CLI overrides → expand sibling inheritance
+  → create and clone defaults → strictly decode
+  → recorded application resolution
+  → resolve typed secret references → semantic validation → classify secrets
+  → snapshot configuration and metadata
+```
+
+`File`, `Filesystem.File`, `Bytes`, `Reader`, and `Mapping` each contribute the first base source with deterministic
+ID `source-1`; enabled imports continue in depth-first order as `source-2` onward.
+`NoSource` skips parsing, supplies an absent version to a configured version checker,
+contributes no source, and continues through defaults, decode, and projection. A
+missing file remains an error; it is never interpreted as no input.
+
+The current `Options` boundary accepts a defaults factory, `VersionRule`, resolver,
+semantic validator, explicit path and glob imports, one selected overlay, and
+filesystem context. It also accepts explicit CLI override records, static secret
+tags, and a dynamic path predicate. `NoSource` rejects imports, active overlays,
+and filesystem context as invalid combinations but accepts overrides. Input
+containing a reserved `configkit` mapping key is rejected while imports are
+disabled.
+
+Every source, options, schema, version, defaults, decode, resolution, or validation
+failure returns a nil result and a `*LoadError`. Successful results contain caller-owned `Config`, detached
+`Metadata`, a defensive source list, and defensive nonfatal diagnostics. Each source
+record's `Kind` identifies file, filesystem, bytes, reader, mapping, or CLI acquisition
+independently of its precedence `Layer`. Host file paths remain canonical;
+filesystem paths are slash-relative within their namespace; synthetic inputs have
+no path. Mutating
+the returned configuration or inspection records cannot alter ConfigKit's private
+snapshot. ConfigKit performs no logging. `Result.WriteEffective` exposes only the
+frozen redacted projection.
+
+### Completion and resource lifetime
+
+`Load` is synchronous and complete on return. Success means input assembly,
+defaulting, typed decoding, configured application resolution, secret lookup,
+validation, and configuration/metadata snapshotting have completed. A reported
+load failure returns diagnostics and a nil result, as described above.
+
+Before returning on success or failure, ConfigKit closes the filesystem handles
+it opened for loading, including files and directory/root handles. Caller-owned
+filesystems are borrowed, never closed. The returned
+configuration and inspection metadata require no close operation and remain
+usable independently of the source files. A supplied `Reader` remains
+caller-owned and is never closed by ConfigKit.
+
+ConfigKit performs no background work after returning: it does not watch inputs,
+refresh secrets, or mutate published results. Inspection and rendering run only
+when explicitly called and use the retained snapshot. Applications normally load
+once near startup, but may explicitly load again using sources that satisfy their
+documented reuse rules. Additional loads produce independently owned results.
+
+Completion is not a transaction over external state. Files and environment
+variables are observed during processing rather than as one simultaneous external
+snapshot. ConfigKit does not roll back application callback effects or manage work
+or resources created by application callbacks. The explicit secrets-directory
+bootstrap remains a separate operation invoked by the application.
+
+## Layered loading
+
+`LoadLayered[T](main, options...)` accepts zero or one `LayeredOptions[T]` value.
+Its `main` is an `Input` containing a source, import opt-in, and optional
+filesystem context. A zero source is invalid; `Input{Source: NoSource()}` omits
+the main document. Each `Underlay` contains inputs that compose strictly as
+one tier, including each input's enabled imports. Empty groups contribute
+nothing. Underlay groups are listed from lowest to highest priority. Repeating
+a file within one group remains an import/repetition error; the same reusable
+source may be selected again in another tier.
+
+ConfigKit acquires and composes the main input first, constructs the schema,
+and checks the optional application version from the main tier only. Underlay
+roots cannot claim that version path (`underlay.version`); imported fragments
+retain `import.version` protection. It then acquires and composes underlay
+groups in order, recursively combines the groups, and applies the main tier,
+one selected overlay, and explicit CLI overrides. Scalar, sequence, and null
+definitions replace lower values between tiers; mappings combine recursively.
+Syntax and strict-composition errors inside a tier cannot be masked by a
+higher-priority tier. Defaults, typed decoding, resolution, secret lookup,
+validation, and publication run once on the final assembled input.
+
+An active layered overlay requires `LayeredOptions.OverlayFilesystem` explicitly,
+independent of the main source's namespace. Its name and root-relative lookup
+follow the selected-overlay rules below; inactive overlays ignore the context.
+The same path in a different filesystem namespace is not a repeated file.
+Ordinary `Load` continues to infer its selected-overlay context from its source.
+
+Source IDs follow acquisition order—main and its depth-first imports, then each
+underlay tier's inputs and depth-first imports, then overlay and CLI—even though
+history follows precedence order. Source `Layer` describes precedence while
+`Kind` describes acquisition. Underlay records use `LayerUnderlay` and a
+one-based `UnderlayIndex` giving their original tier position; all other records
+have index zero. Explicit empty groups and `NoSource` consume no source ID.
+Byte, source, node, and glob-entry budgets are shared across the load, while
+the existing per-source and import-depth bounds still apply.
+
+The maintained [layered consumer example](consumers/README.md#native-filesystem-and-layered-input)
+shows a main host file, two underlay tiers, embedded defaults, a mapping source,
+and explicit resource access without a second configuration pass.
+
+### Sibling inheritance
+
+Any input mapping may declare `extends: name` to inherit from the mapping named
+`name` among its immediate siblings. Names are exact keys, including the empty
+string; lookup does not search ancestor or unrelated scopes. The document root
+and a sequence-element mapping have no sibling namespace for their own string
+relationship, though mappings nested inside them can have one. An `extends`
+value of null cancels a relationship without looking up a parent. Other value
+types, missing or non-mapping parents, and cycles fail the load with value-free
+diagnostics.
+
+`extends` is reserved structural input across ordinary and layered loads, every
+source kind, imports, selected overlays, and explicit CLI overrides. It is
+consumed before typed decoding and need not appear in the application's Go
+types. Applications previously using `extends` as an ordinary YAML field must
+rename that key and its field. No collection registration or keyword setup is
+required.
+
+ConfigKit completes strict composition within tiers and precedence assembly
+between tiers before resolving relationships. An omitted `extends` retains a
+lower-priority relationship; `extends: null` cancels it while preserving the
+child's own settings. Superseded references are historical evidence, not active
+relationships to validate. Each child recursively overlays its own settings
+over its resolved parent: explicit zero, false, empty string, sequence, and
+null values replace inherited values, while mappings combine recursively.
+The child retains its key. All effective relationships resolve, including
+entries the application may never select for execution. Partial parent
+definitions undergo normal typed decoding and application-owned validation,
+not a special structural exemption.
+
+Enclosing relationships resolve first. Nested instructions carried by a parent
+are then resolved separately at each destination, so a child's nested sibling
+override can change an inherited nested relationship. Typed defaults and
+application-derived values do not start another inheritance pass. Inherited
+input counts as explicit presence for `Metadata.IsExplicit`,
+`Resolution.IsExplicit`, and absence-based resolver defaults, even for false,
+zero, empty, or null input. `Origin.Inheritance` distinguishes it from a direct
+declaration with concrete source, destination, and controlling directive paths.
+A direct child replacement has its own effective origin; displaced ancestry
+remains inspectable in history. An inherited relative resource keeps the
+declaring source's passive `SourceContext`, not the child's directory.
+
+The optional schema-version checker still runs once against the main input at
+its original point. Inheritance cannot add, replace, or consume the protected
+version path; an unrelated relationship inside an enclosing mapping does not
+invalidate an unchanged version. Expansion uses the decoded projection
+node/depth limits without charging copied values as acquired sources;
+retained evidence uses the existing history-node limit. See the
+[consumer example](consumers/README.md#named-sibling-inheritance) for one-load
+usage.
+
+### Source resource contexts
+
+`Result.SourceContext(id)` and callback-scoped `Resolution.SourceContext(id)`
+return a passive `ResourceContext` for a source with filesystem context, or
+false for unknown and contextless IDs. The result query is nil-safe; the
+resolution query follows the callback's lifetime guard. Queries perform no
+filesystem access. Obtain IDs from exact origin locations rather than guessing
+one context for a composite origin or an application-derived value.
+
+`ResourceContext.FS` is rooted at the source's configured root, and `BaseDir`
+is its slash-relative directory inside that root. This includes imported
+sources, selected overlays, host files even without enabled imports, native
+files, and byte, reader, or mapping inputs with an explicit context. CLI and
+contextless synthetic inputs have no resource context. To open a relative
+resource, join `BaseDir` with the application resource name using slash-path
+operations and open that path through `FS`.
+
+For a resource-valued field, query `result.Metadata().Lookup(fieldPath)`, inspect
+its origin locations, choose a source ID only when the application's policy can
+identify the intended contributor, then call `result.SourceContext(id)`. The
+context belongs to that source even when the field survived from a lower-priority
+underlay. A composite origin has no automatically selected resource base.
+
+Native contexts borrow the caller's filesystem within the configured root.
+Host contexts retain a canonical root path, not an open root handle; each
+resource `Open` checks containment and opens a fresh handle that the returned
+file's `Close` releases. Applications own and close the files they open.
+Resources are application data, not configuration input, and do not consume
+configuration byte or node budgets. The loaded configuration and metadata stay
+usable if source files later change or disappear. Later resource operations
+observe the backing filesystem then and may fail if files move, disappear, or
+a caller-owned filesystem closes. This is not a snapshot or universal sandbox.
+
+### Application schema versions
+
+`VersionRule` declares a semantic path and non-nil checker. Before defaults or typed
+decoding, the checker receives a `Version` preserving absent, explicit null, string,
+or strict decimal-integer input. Strings and integers supply their exact spelling in
+`Version.Text`; ConfigKit does not impose a machine-integer range. Fractional or
+exponent numbers, booleans, mappings, and sequences produce `version.type`, and the
+checker does not run. ConfigKit does not interpret the text or impose a universal
+version path.
+
+Integer versions use the strict grammar `^-?(0|[1-9][0-9]*)$`. Their spelling is
+preserved exactly, including `-0`, and application policy decides which identifiers
+are supported. A numeric version has no built-in `int64` range limit. Existing parser
+policy still rejects leading zeroes, leading plus signs, hexadecimal notation, and
+other non-JSON scalar forms before version checking.
+
+At exactly the configured semantic path, accepted integer input can decode into a
+plain Go string or named string without a text codec, including pointer wrappers.
+This is a load-local exception: siblings and unrelated fields, dynamic values,
+integer and float destinations, durations, `Secret`, and text codecs retain ordinary
+strict decoding. The retained source and history stay numeric while typed projection
+and effective YAML contain the resulting string; explanation records this through
+the normal decoding reconciliation event. Fragment, overlay, and CLI ownership
+protections apply before this conversion.
+
+The checker reports safe, value-free errors and warnings through `Validation.Error`
+and `Validation.Warning`; ConfigKit resolves primary and related paths to exact or
+nearest input locations. Reported errors fail loading. If the checker returns an
+error without reporting one, ConfigKit emits a generic `version.hook_failed`
+diagnostic and suppresses the returned error text. Warnings alone are retained on a
+successful result. Callback panics remain programming failures.
+
+### Layered metadata
+
+`Result.Metadata` describes every final canonical path. Queries retain explicit
+key/index distinctions using actual effective and historical container shapes;
+only parsed numeric tokens are resolved contextually. A descendant that never
+existed is not historical merely because an atomic ancestor was replaced. Exact
+surviving direct or inherited input paths are explicit and retain their source
+layer and derivation; omitted paths have a default origin.
+An explicit parent mapping does not make omitted children explicit. Null state and
+available source coordinates are retained. `History` records the Go-zero or application
+default baseline followed by exact base or overlay definitions, including
+equal-valued input. Overlay replacement removes displaced descendants from effective
+metadata while retaining their base definition and the parent replacement operation
+in history. All metadata queries and returned nested records are detached.
+
+`Metadata.HistoricalPaths` enumerates observed paths, including removed paths,
+without reloading input or resolving unselected credentials. Consumers can use
+it with `History` to validate ownership of declarations hidden by an overlay;
+domain ownership rules remain application responsibilities. The method's Go
+documentation in [metadata.go](../metadata.go) defines enumeration and path-ordering
+details.
+
+History is chronological: a path can have a synthetic default record, its exact
+base definition, an overlay replacement, structural inheritance, and a recorded
+resolution operation. A descendant
+query uses the ancestor's path for a whole-container or whole-sequence replacement;
+the descendant can therefore retain history after `Lookup` stops reporting it as
+effective. Equal-valued input is still an explicit base definition, while a derived
+value for absent input remains non-explicit.
+
+A mapping assembled from the selected file and imports has one composite base origin
+whose locations retain source traversal order. A mapping also visited by an overlay
+has an overlay-layer composite origin with the lower contributing locations followed
+by the overlay location; an empty mapping is still an explicit container even though
+it contributes no children. Resolution origins are synthetic: they have layer
+`resolution`, no fabricated file location, and a `derived_default` or `normalization`
+operation. Reasons and dependency paths retain first occurrence order with duplicates
+removed. Source records remain ordered as selected source, depth-first imports, the
+selected overlay, then synthetic CLI records in supplied order.
+
+Inheritance adds no acquired source or precedence layer. `Origin.Inheritance`
+lists concrete transfers from contributor paths through destinations, with
+each step's controlling `extends` path and location. `History` retains source
+applications at their original paths and projects parent contributions, child
+replacements, and consumed controls at destination paths after source assembly
+and before typed decoding. `HistoricalPaths` includes consumed directives and
+displaced inherited descendants. A control can have history even when `Lookup`
+reports it absent. Queries return detached records.
+
+### Secret classification and effective rendering
+
+Secret classification combines `configkit:"secret"` field tags with the optional
+pure `Definition.Secret(Path) bool` predicate. Tags on concrete structs inside
+supported dynamic values are retained in typed projections, including superseded
+defaults and pre-resolution values. A tagged or predicate-classified
+container makes all descendants sensitive. ConfigKit evaluates final and historical
+paths, so replacing or deleting a definition does not erase its classification. The
+predicate can add sensitivity but cannot declassify a tagged path.
+
+Recorded resolution dependencies propagate sensitivity to their derived target.
+Propagation reaches a fixed point, so record/map iteration order does not affect the
+result and dependency cycles terminate. A dependency on a classified descendant or
+on a container that contains one is treated conservatively as sensitive. Applications
+must classify secret-producing transformations whose dependencies are not recorded.
+Inherited value and control paths link source and destination classifications
+through chains and nested copies; unrelated sibling fields are not classified
+merely because another field is secret. Displaced historical evidence remains
+redacted. Secret references are copied only as unresolved names; credential
+lookup stays after decoding and application resolution.
+
+`Result.WriteEffective` writes the frozen resolved snapshot as deterministic redacted
+YAML. Mappings sort by decoded key string, sequences retain order, indentation is two
+spaces with noncompact sequence indentation, line endings are LF, the document has no
+start or end marker, and output ends with a newline. Nil pointers/maps/slices remain
+`null`; non-nil empty maps and sequences remain `{}` and `[]`. A secret root is
+replaced by the quoted string `'[REDACTED]'`. Redacted output is intended for
+inspection and is not promised to be reloadable.
+
+Rendering uses only a safe adapter tree built from the already completed canonical
+typed projection. It does not invoke application YAML marshal hooks or text codecs;
+all text-codec projection has succeeded before `Load` returns. Caller mutation of
+`Result.Config` cannot change later output. Writer failures, including short writes,
+are returned and may leave partial redacted output; internal dumper failures are
+translated to a fixed safe error. There is no unredacted rendering option and
+ConfigKit performs no implicit logging.
+
+`Result.Config` is the explicit trusted boundary and contains ordinary typed values,
+including secrets. Metadata records, diagnostics, and load errors contain no
+configuration values. Explanation snapshots deliberately expose non-secret
+configuration history after applying the redaction contract below. Applications
+must still keep source labels, resolution reasons, and diagnostic messages value-free
+because ConfigKit cannot infer and sanitize secrets embedded in arbitrary application
+prose.
+
+### Historical-value explanation
+
+`Result.Explain(path)` returns a detached `Explanation` for any known effective or
+historical path. Its effective value and each chronological before/after value are
+`ValueSnapshot` records containing deterministic YAML text rather than mutable Go or
+parser values. `Present=false` with empty YAML means absence or deletion; explicit
+null is present and renders as `null`. The history starts with the canonical typed
+application-default or Go-zero baseline, then includes only relevant base sources in
+traversal order, the selected overlay, supplied CLI records, and audited net
+resolution operations. Structural inheritance events appear after source replay
+and before typed reconciliation, including consumed or canceled `extends` input
+and equal-valued child replacements. Overlapping parent/child resolution records
+are rendered
+as one net subtree event with combined reasons and dependencies, rather than
+pretending that the recorded assignments ran in lexical order. Explicit equal
+writes remain visible. When input replay
+differs from the final typed input, a `ChangeDecoding` event records the transition
+before domain resolution. Its origin retains the decoded path's source/default
+attribution; its reason identifies static-default retention and canonical decoding.
+This built-in inspection operation is not accepted by `Resolution.Record`.
+
+Base, overlay, and CLI history preserves the policy-validated input representation,
+including a superseded value that could not have decoded into the final Go field.
+Baseline, effective, and resolution values use canonical typed projection. A
+decoding event bridges replayed input and canonical typed values, so intermediate
+null/scalar replacements cannot incorrectly imply permanent default removal. Mapping
+queries reconstruct each source or override contribution, while sequences remain
+atomic: a descendant history identifies its presence before and after the containing
+sequence replacement without implying element-wise merging. Removed paths remain
+explainable; unknown and malformed paths return false.
+
+Every snapshot applies the same historical tag, predicate, and recorded-dependency
+sensitivity closure as effective rendering before YAML is exposed. A redacted scalar
+is the quoted marker `'[REDACTED]'`, and a container snapshot has `Redacted=true` if
+it contains a masked descendant. Typed `Secret` snapshots contain only the configured
+environment name. `SecretReference` reports that name only for a successfully
+resolved effective reference, and is omitted when its path is classified. Credential
+values are never retained in explanation history.
+
+`Result.WriteExplanation(output, path)` renders the safe structured result with the
+canonical JSON-pointer path, canonical-versus-input representation labels, effective
+source, composite locations, chronological values, resolution reasons and
+dependencies, and successful secret-reference lookup attribution. Control characters
+in paths, source identifiers and labels, reasons, dependencies, and reference names
+are escaped. An unknown path returns a fixed safe error before writing anything;
+writer errors and short writes are returned and may leave partial output. There is no
+unredacted mode.
+
+Retained history consists of immutable source applications and audited subtree
+deltas, rather than a full tree copy per field. Shared nodes count once toward a
+4,000,000-node retained-history limit; exceeding it fails loading with
+`explain.limit_exceeded`. Replaying one requested path is performed on demand, and
+the returned YAML strings and nested records cannot mutate later explanations.
+
+Application commands should render the separate `SecretsReport` immediately after
+an explicit `LoadSecretsDir` bootstrap, then use `WriteDiagnostics`,
+`WriteEffective`, or `WriteExplanation` on the later load result as appropriate.
+ConfigKit does not infer bootstrap outcomes from a secret reference and does not
+bundle these independent reports into a command framework.
+
+## Typed secret references
+
+Credential-bearing fields use the opaque `Secret` type and store an environment
+variable name in YAML, such as `api_key: OPENROUTER_API_KEY`. `SecretEnv(name)`
+constructs the same unresolved reference for application defaults or recorded
+resolution. Names must match `[A-Za-z_][A-Za-z0-9_]*`; they are public
+configuration and remain visible through `EnvName`, canonical projection, history,
+and effective output unless the path is separately classified for redaction.
+
+A non-pointer `Secret` is required. An absent, null, or invalid reference, or an
+unset or empty environment value, fails with a safe `secret.*` diagnostic at the
+configuration path. `*Secret` is optional only when nil; every non-nil reference
+must resolve to a nonempty value. Secret references work in typed structs, maps,
+pointers, slices, and arrays. A dynamic `any` value does not establish secret
+semantics and cannot contain `Secret`; applications must use a typed slot.
+
+ConfigKit resolves only the effective names after recorded application resolution
+and before semantic validation. Each unique name is read with `os.LookupEnv` once
+per load. Validation can inspect the credential through the deliberately named
+`Value()` accessor and distinguish success with `IsResolved()`. Later loads read
+the environment again, and cloned defaults are rebuilt from names so a previously
+resolved result cannot retain a stale credential. `Load` never writes to the
+environment.
+
+Credential bytes are held only in the per-load lookup state and the trusted returned
+configuration, and are returned only by `Value`. Secret formatting uses a safe
+public-name representation, JSON marshals only the name, and projection, metadata,
+histories, diagnostics, effective output,
+and resolution snapshots never retain the credential. Validation remains read-only:
+in addition to ordinary projected-value comparison, ConfigKit checks the private
+resolved state against this load's lookup result. Validator mutation checks also
+reject changes to projected field sensitivity, even when a replacement dynamic
+concrete type preserves the same textual values. Applications must keep their
+validation messages value-free and must not include `Value()` in diagnostics.
+
+For example, a typed pipeline field is declared as:
+
+```go
+type PipelineConfig struct {
+    APIKey configkit.Secret `yaml:"api_key"`
+}
+```
+
+The executable `ExampleSecretEnv` demonstrates loading and inspecting the safe
+reference state without printing its value.
+
+## Explicit secrets-directory bootstrap
+
+`LoadSecretsDir(directory)` is a separate, opt-in startup operation. It is never
+called by `Load`, is not a YAML option, and does not participate in configuration
+validation. Applications choose the native directory path and should invoke the
+operation once before starting concurrent work. The selected path may itself be a
+symlink; ConfigKit resolves it to an existing canonical directory before examining
+its immediate entries.
+
+The bootstrap enumerates at most 1,024 entries, including dot-prefixed entries.
+Entries whose names begin with `.` (files, directories, or symlinks, such as `.git`
+and `.gitignore`) are ignored before name or metadata validation, are never opened,
+and are omitted from the report. Remaining entries are sorted by filename; each
+must have an ASCII environment-variable name and be a regular, nonsymlink
+file. Metadata for all remaining entries is validated before file content is read
+or process state is changed. Existing environment variables win, including variables whose
+value is empty; their files are not opened. Each eligible file is limited to 1 MiB,
+and eligible content is limited to 8 MiB in total. ConfigKit removes exactly one
+terminal LF or CRLF, preserves all other whitespace, accepts an empty value, and
+rejects NUL bytes.
+
+All eligible files are read successfully before application begins. Presence is
+checked again immediately before each `os.Setenv`: a variable populated since
+preflight is skipped. A write failure stops application without rollback, so prior
+writes remain and later eligible entries are `not_applied`. This operation is not
+atomic and does not provide compare-and-set semantics for concurrent environment
+mutation.
+
+`SecretsReport.Entries` returns detached, filename-ordered `SecretFileResult`
+records with `loaded`, `skipped_existing`, `not_applied`, or `failed` status.
+`ExistingEmpty` distinguishes an empty existing winner. `SecretsReport.WriteTo`
+renders only quoted names, canonical paths, statuses, and that empty-state flag;
+it never retains or renders file contents. Failures return the non-nil partial
+report with a `*SecretsError` containing detached `secrets.*` diagnostics and no
+raw filesystem or environment error chain. Applications should retain the report
+alongside the later configuration result and explicitly present blocked and failed
+files when appropriate; ConfigKit stores no implicit global report.
+
+### Recorded application resolution
+
+An optional `Definition.Resolve` callback runs after successful typed decoding. It
+receives the working configuration and a per-load `Resolution` context. The context's
+`IsExplicit` query uses surviving input presence, so explicit false, zero, empty, and
+null are never confused with absence or static defaults.
+
+`Resolution.InputInfo(path)` returns detached effective metadata from the fixed
+decoded entry state, before application resolution runs. It includes retained static
+defaults, preserves explicit null, and uses the same exact semantic path matching as
+`Metadata.Lookup`; missing, malformed, and key/index-shape-mismatched paths return
+false without diagnostics. Its `Explicit` value agrees with `IsExplicit` for every
+found entry path. Resolution changes, additions, removals, and moves do not alter
+this entry view.
+
+`Resolution.Source(id)` returns a detached record for an already acquired source in
+the same load: the main source, imports, selected overlay, and supplied CLI records
+where applicable. Empty and unknown IDs return false. It never reloads input, reads
+the filesystem, resolves symlinks, or looks up credentials. A source path exists
+only when the acquired source has one; defaults and byte, reader, and CLI sources do
+not acquire an invented file path. Applications select a base directory from exact
+origin locations and these source records according to their own policy.
+
+Both queries are callback-scoped like the rest of `Resolution`: nil, zero, or
+retained contexts panic with the fixed closed-context failure outside the callback.
+Returned field and source records are detached and remain usable after callback
+exit; changing them cannot affect later queries, results, or another load.
+
+`Default` assigns and records a derived value only when its path is not explicit.
+`Normalize` always assigns and records. For transformations performed directly by
+application code, `Resolution.Record` declares a derived-default or normalization
+operation; a recorded container covers changes to its descendants. Records require
+a schema-valid path, valid kind, safe nonempty reason, and schema-valid dependency
+paths. Repeated records at one path are coalesced: reasons and dependencies retain
+their first occurrence, the last helper value is authoritative, and any normalization
+makes the combined operation a normalization.
+
+ConfigKit projects the configuration before and after the callback. Every net change
+must have an exact or ancestor record. Helper-assigned values must agree with the
+final value at their declared path, which supports ordinary map-entry copy/writeback
+while detecting forgotten writeback or unrelated targets. Invalid paths, kinds,
+values, records, helper targets, and unrecorded mutations fail the load. Equal-valued
+derived assignments may still record application intent even when there is no
+structural change.
+
+`Resolution.Error` and `Resolution.Warning` attach exact or nearest available input
+locations. Reported errors fail the load; warnings survive on a successful result. A
+returned resolver error adds one generic `resolve.hook_failed` error only when the
+callback did not report an error, and its text is never exposed. Callback panics are
+programming failures. Resolution and validation contexts are callback-scoped; using
+a nil, zero, or retained context outside its active callback panics with fixed,
+value-free text.
+
+Successful records update effective origins and append detached metadata history
+without changing input explicitness. Removed paths leave effective metadata but
+retain history. ConfigKit privately snapshots each recorded before/after subtree for
+later safe explanation; caller mutations of `Result.Config` cannot alter those
+snapshots.
+
+### Semantic validation
+
+An optional `Definition.Validate` callback runs after successful resolution and
+receives the resolved configuration plus a per-load `Validation` context. It can
+collect multiple independent `validate.error` and `validate.warning` reports.
+Warnings continue the lifecycle and are returned on success; any error returns a nil
+result with the full safe diagnostic and source report.
+
+Primary and related paths must be valid for the application schema. Omitted declared
+fields and missing string-map or dynamic keys are valid report targets; unknown
+struct fields and malformed paths produce `validate.invalid_path`. ConfigKit attaches
+the exact surviving input location when one exists, otherwise the nearest input
+container location, or no primary location for defaults-only synthetic state.
+
+Validation is read-only. ConfigKit projects the configuration immediately before and
+after the callback and returns `validate.mutation` at every detected net-change path,
+including nested mutable state. A value that can no longer be projected is also a
+mutation failure. No mutated or otherwise invalid configuration is published.
+Callback panics remain programming failures, and retained contexts use the same
+fixed closed-context panic as version and resolution callbacks.
+
+Only schema-bound exported state participates in loading, resolution audit,
+validation audit, metadata, and snapshots. Ignored or unexported ordinary fields are
+zero in returned detached values. Applications retain responsibility for domain
+rules and runtime initialization; validators should not start clients or depend on
+live services as a substitute for configuration validation.
+
+## Strict document composition
+
+ConfigKit strictly composes parsed base documents when `Options.Imports` is true.
+Application defaults do not participate in this operation.
+
+| Existing node | Incoming node | Result |
+| --- | --- | --- |
+| Absent | Absent | Absent |
+| Absent | Present | Retain the incoming node |
+| Present | Absent | Retain the existing node |
+| Mapping | Mapping | Recurse by mapping key |
+| Any other pair of present nodes | Any other pair of present nodes | `compose.conflict` |
+
+Every non-mapping overlap is a conflict, even when values are equal. Nulls and
+sequences are present atomic values, so they also conflict when repeated; sequences
+are never joined by index. Disjoint entries under shared mappings compose, making
+stable keyed mappings the natural representation for independently contributed
+entries.
+
+An empty mapping contributes no child definitions. Two empty mappings compose, and
+an empty mapping neither clears nor conflicts with another mapping's children.
+Shared mapping containers retain all contributing value locations as their composite
+base origin. A conflict reports the first claim as its primary location and every
+remaining claim as related locations, in deterministic source and declaration
+traversal order. Traversal order never authorizes replacement. Composition clones
+the resulting tree and its ordered claim records rather than mutating or aliasing an
+input document.
+
+## Selected overlays
+
+`Options.Overlay` selects at most one overlay by name. Names must match
+`[a-zA-Z0-9_-]+`; they are not paths. The empty name and exact lowercase name
+`default` select no overlay, and `overlays/default.yml` is never loaded implicitly.
+Every other name resolves only to `<configuration-root>/overlays/<name>.yml`, with
+no extension fallback, case normalization, inheritance between overlay files,
+or overlay stack. A selected missing overlay is an error.
+
+The overlay is a separately policy-validated YAML mapping. It is loaded after the
+base import graph is composed and its schema version is checked, but before defaults
+and typed decoding. Overlay bytes, nodes, and source records count toward the same
+aggregate limits as base inputs. Its canonical path must remain within the configured
+root and must not duplicate a file already present in the base graph.
+
+Overlay is intentionally distinct from strict composition:
+
+| Existing lower node | Incoming overlay node | Result |
+| --- | --- | --- |
+| Absent | Value | Retain the overlay value |
+| Value | Absent | Retain the lower value |
+| Mapping | Mapping | Recurse by mapping key |
+| Any other pair of present nodes | Any other pair of present nodes | Replace the entire lower node |
+
+Scalars, sequences, and null are atomic. Thus an overlay sequence replaces rather
+than extends a base sequence, `[]` clears it, null is an explicit replacement, and
+cross-kind replacement is allowed when the final application schema accepts it.
+Replacing a subtree removes all displaced descendants from effective presence and
+origin data; history retains the displaced definitions and identifies the parent
+replacement. Surviving overlay paths have overlay origins, while recursively shared
+mapping containers retain their contributing locations.
+
+An overlay may not contain `configkit` anywhere, contribute the configured schema
+version, or replace an ancestor of that version with a scalar or null. These rules
+apply even if the supplied version text would be unchanged. Overlays cannot mask a
+base parse, composition, or version failure because those checks run first.
+
+## Explicit CLI overrides
+
+`Options.Overrides` accepts only records the application knows were explicitly set
+by its CLI parser. Each `Override` supplies a non-root mapping `Path`, a detached
+`Value`, and a required safe display `Flag` such as `--workers`; ConfigKit has no CLI
+parser dependency. Parser defaults must not be submitted as overrides, and `Flag`
+must never contain the raw argument or configured value. General environment
+variable overlays are an explicit non-goal: environment access is reserved for
+typed secret references.
+
+Overrides apply after the selected overlay and before typed defaults/decoding, so
+the input precedence is application defaults < composed base < selected overlay <
+CLI. Recorded resolution, typed secret lookup, and semantic validation follow the
+effective override tree. Overrides also work with `NoSource`.
+
+Values are converted directly into ConfigKit's owned tree without YAML parsing or
+string coercion. Supported values are `nil`, built-in strings and booleans, all
+built-in signed and unsigned integer widths except `uintptr`, finite `float32` and
+`float64`, and recursive `[]any`/`map[string]any`. Strings stay strings; duration and
+secret fields therefore receive string values. Nil is explicit null; empty strings,
+false, and zero remain intentional; empty sequences replace whole lists; and mapping
+values recursively overlay existing mappings. Map keys are sorted canonically and
+sequence order is preserved.
+
+All records are detached and validated before any is applied. Root and explicit
+sequence-index paths are invalid; parsed numeric tokens remain mapping keys. A path
+may create missing mapping ancestors but cannot traverse an existing scalar, null,
+or sequence. Duplicate and ancestor/descendant-overlapping records are rejected.
+Neither paths nor values may create `configkit`, and no record may overlap the
+configured schema-version path. Unknown fields and effective type mismatches remain
+ordinary strict-decoder errors.
+
+At most 1,024 records are accepted, and each record creates one synthetic CLI
+source after file/overlay sources in supplied order. Override sources share the
+1,024-source ceiling. A record has an 8 MiB string-byte limit; override strings and
+source bytes share the 64 MiB aggregate limit. Synthetic mapping keys and values
+count toward the existing 1,000,000-node and depth-256 ceilings. Cycles, named or
+unsupported types, nonfinite floats, and limit excesses fail with safe `override.*`
+diagnostics. Diagnostics and provenance identify the safe `Flag` source, never raw
+arguments or values.
+
+Override origins are explicit CLI origins. History retains replaced base/overlay
+definitions and records equal-value replacements as well as structural changes.
+Caller-owned maps and slices are snapshotted during loading and must not be mutated
+concurrently with the call. The executable `ExampleOverride` shows translating a
+parser's explicit-set state into records while preserving an explicitly supplied
+zero.
+
+## Explicit imports
+
+Imports are opt-in. With `Options.Imports` enabled, a document may reserve its root
+`configkit` mapping for an `imports` sequence. ConfigKit removes that mapping before
+application decoding. Each sequence item is a mapping with exactly one nonempty
+string `path` or `glob` plus an optional boolean `optional`; all other shapes and
+fields are `import.invalid`. A `configkit` key below the root is invalid. With
+imports disabled, any occurrence remains `import.disabled`.
+
+The directive key is `configkit`, not the `_configkit` spelling used in v0.1.0.
+There is no legacy alias: `_configkit` is ordinary application data, subject to
+normal schema validation, and does not trigger imports. When upgrading, rename
+directive keys in root files and imported fragments, and rename any application
+fields previously named `configkit` to avoid the newly reserved key.
+
+Path declarations use slash-separated relative paths. Absolute paths and network
+URLs are invalid. Each path resolves from its declaring file's canonical directory,
+and files are traversed depth-first in declaration order: a file contributes its own
+body before its imports. Order stabilizes source records and diagnostics but never
+permits replacement. Required missing paths fail; `optional: true` suppresses only
+target nonexistence, not invalid paths, containment failures, directories,
+permissions, parse errors, or composition errors.
+
+Glob declarations use the slash-based Go `path.Match` grammar: `*`, `?`, character
+classes, and backslash escapes are supported, while recursive `**` syntax is invalid.
+Backslashes escape pattern characters rather than acting as directory separators.
+ConfigKit validates the complete pattern before filesystem traversal, walks only
+directories selected by preceding segments, and reads wildcard directories in
+bounded batches. Every examined entry consumes the separate visit budget, including
+nonmatches. Matches are sorted lexicographically by slash-relative spelling within
+each declaration before depth-first source traversal. A required zero-match glob is
+`import.missing`; `optional: true` suppresses only zero matches. Invalid patterns,
+walk failures, matched directories, invalid documents, escapes, and repeated targets
+remain errors. Final candidates are bounded by the remaining source limit before
+their contents are accumulated.
+
+For host files, the configuration root defaults to the selected file's canonical
+directory. A host file may supply `FilesystemContext.Root` to widen that root but
+may not supply `BaseDir` or a native `FS`. Byte, reader, and mapping inputs with host context
+must provide both `BaseDir` and `Root` as absolute existing directories.
+For `Filesystem.File`, the default root is `.` in its namespace and the base is
+the selected file's directory. An explicit context must use the same `Filesystem`
+namespace and may set `Root` to contain the file and its base; it may not supply
+`BaseDir`. Byte, reader, and mapping inputs with native context provide both `BaseDir` and
+`Root` as slash-relative `fs.ValidPath` directories in `FS` (`.` means its root),
+with the base inside the root. Context paths are checked even when imports and
+overlays are inactive. Diagnostic labels, including URI-looking labels, never
+imply filesystem paths. Nonregular targets are rejected before opening to avoid blocking on FIFOs;
+post-open regular-file checks remain in place under the stable-input assumption.
+ConfigKit canonicalizes symlinks,
+checks containment with relative paths, and opens the canonical root-relative target
+through a library-owned root handle. Contained relative or absolute symlink targets
+are accepted; escapes are rejected. Canonical paths define identity, so hard links at
+distinct paths remain distinct sources. Native filesystems use slash-path operations
+and their own symlink behavior; imports stay in their selected namespace and root.
+
+An active-stack repeat is `import.cycle` and reports the complete cycle's import
+sites. A previously visited canonical path is `import.repeated` and reports both
+inclusion routes, including diamonds and aliases. Each accepted file is read once.
+Imported fragments may contain their own root directives, but may not claim the
+application's schema-version path or replace one of its ancestors; the version must
+come from the selected source. No directory is scanned implicitly, including one
+named `conf.d`, and ConfigKit performs no remote fetching.
+
+## YAML documents
+
+The private YAML boundary currently accepts exactly one nonempty document whose root
+is a mapping. Comments and block or flow collections are supported. It rejects:
+
+- empty input or an empty document;
+- every additional document, including an empty one;
+- duplicate decoded mapping keys;
+- non-string mapping keys;
+- explicit tags, anchors, aliases, and merge keys;
+- a quoted or plain mapping key equal to `<<`; and
+- input exceeding the fixed depth or node limits.
+
+Mapping key comparison is exact: it performs no case folding or Unicode
+normalization. The private document tree retains declaration order, exact validated
+number spelling, source identifiers, and separate key/value line and column
+locations. It contains no upstream parser nodes or types.
+
+Root depth is zero. Input depth is limited to 256 and each parsed input tree to
+1,000,000 nodes, counting mapping keys as input nodes. The upstream parser also has
+a private calibrated depth guard; passing that guard never bypasses ConfigKit's tree
+limits.
+
+## Scalars
+
+Scalar meaning is determined by ConfigKit rather than upstream coercion:
+
+| Input form | Meaning |
+| --- | --- |
+| Quoted, literal, or folded scalar | String |
+| Plain `true` or `false` | Boolean |
+| Plain `null`, `~`, or an empty mapping value | Null |
+| JSON decimal number | Number, retaining its exact spelling |
+| Date/time-looking or other ordinary plain text | String |
+
+JSON numbers permit an optional minus, a zero or nonzero decimal integer without a
+leading zero, an optional fraction with at least one digit, and an optional decimal
+exponent. Hexadecimal, octal, digit separators, leading plus, leading/trailing-dot
+forms, incomplete exponents, and non-finite values are rejected. Legacy boolean
+words (`yes`, `no`, `on`, and `off`) and non-lowercase variants of the reserved
+boolean/null words are rejected unless quoted.
+
+Mapping keys use the same scalar classification and must classify as strings. Quote
+keys that otherwise classify as a boolean, number, or null.
+
+## Application schema binding
+
+ConfigKit builds a private reflection descriptor graph for each schema operation;
+it keeps no global mutable descriptor cache. A configuration root must be a struct
+or string-keyed map. Nested supported shapes are:
+
+- booleans, strings, signed and unsigned integers, and finite floating-point types;
+- `time.Duration`, typed `Secret` references, and paired
+  `encoding.TextMarshaler`/`TextUnmarshaler` scalars;
+- pointers, structs, string-keyed maps, slices, fixed arrays, and `any`; and
+- recursive type definitions whose eventual application values are acyclic.
+
+Named scalar types retain their Go identity. `uintptr`, complex numbers, functions,
+channels, unsafe pointers, non-string map keys, and nonempty interfaces are not
+configuration types. A custom text scalar must provide both directions on its value
+or pointer method set. Building a descriptor only inspects method sets; it never
+executes application methods or parser-specific hooks.
+
+Exported struct fields use an explicit `yaml` name or the lowercase Go field name.
+Unexported fields and `yaml:"-"` are ignored. `omitempty` is accepted but does not
+change binding or projection. An explicit `yaml:",inline"` flattens a struct
+or pointer-to-struct, or designates at most one string-keyed inline map for otherwise
+unmatched names. Ambiguous names, named inline fields, multiple inline maps, and
+unsupported or malformed tag options are schema errors. Inline pointers must
+terminate in a struct; pointer-to-map and recursive pointer-only inline declarations
+are rejected before the defaults factory runs. Embedded fields are ordinary
+named fields unless explicitly inlined. `configkit:"secret"` is the only current
+ConfigKit field tag and marks its bound field or container for secret classification
+and redacted inspection.
+
+Schema path traversal uses these same bindings. Explicit key segments address
+mappings, explicit index segments address sequences, and parsed numeric pointer
+tokens become indices only in a sequence. Sequence indices must use canonical
+nonnegative decimal spelling: no signs or leading zeroes except `0` itself.
+Tokens such as `+0` and `-0` remain literal keys in mappings but do not identify
+sequence elements. Fixed-array indices are bounds checked. Dynamic `any` and inline-map entries
+remain schema-valid for application-defined descendants, but dynamic values cannot
+introduce typed secret references.
+
+Descriptors are reused by typed decoding, projection, and cloning so those operations
+cannot acquire different field bindings.
+
+### Canonical module options
+
+Applications with a known module catalog represent each configured item as an object
+with an explicit module identifier and an options mapping. Ordinary typed structs,
+including a small union of optional option fields, use the same strict binding above;
+application validation decides which fields and combinations apply to each module.
+String shorthand, a library module registry, and custom structural decoder hooks are
+not supported alternatives.
+
+When a runtime-selected catalog genuinely requires dynamic options,
+`map[string]any` retains ConfigKit's canonical dynamic scalars. In particular,
+integers are `int64`; application validation owns allowed keys, value constraints,
+range checks, and conversion to runtime `int` or catalog objects. ConfigKit does not
+provide generic subtree conversion, and consumers must not add a YAML marshal/decode
+round trip to exercise supported behavior. The
+[consumer adoption guide](consumers/README.md) contains compiled typed and dynamic
+examples.
+
+## Defaults and typed decoding
+
+The private decoder starts from an independently owned clone of the application's
+typed defaults and applies only explicitly present input nodes. Defaults therefore
+never become explicit, while equal-valued input remains explicit. Successful decode
+produces detached typed state, baseline and final canonical trees, an input-presence
+index, and default/input origins for the later public loading lifecycle.
+
+| Configured input | Effect on the typed baseline |
+| --- | --- |
+| Absent field | Retain the default |
+| Explicit false, zero, or empty string | Replace the default |
+| Partial mapping or string-keyed map | Recurse and retain omitted default children or entries |
+| Empty mapping | Retain existing mapping children |
+| Sequence, including an empty sequence | Replace the entire sequence |
+| Pointer object | Recurse into a non-nil default; otherwise allocate an object whose omitted children have ordinary Go zero values |
+| Allowed null | Replace the value with nil and suppress its default |
+
+Null is allowed only for pointers, maps, slices, and dynamic `any` values. It is an
+error for scalars, structs, and arrays. New map entries and sequence elements begin
+from their Go zero values; ConfigKit does not invent entry-level defaults.
+
+Decoding is strict at every typed depth. Unknown struct fields, type mismatches,
+invalid nulls, numeric overflow, and arrays with the wrong length are errors at the
+original semantic path and source coordinates. String-keyed maps accept arbitrary
+keys but preserve the strict schema of their values; inline maps accept unmatched
+keys according to their element descriptor. Multiple independent field failures are
+collected without publishing the partially decoded object.
+
+Booleans and strings are not generally coerced. At exactly a configured
+`VersionRule.Path`, strict decimal-integer input may decode into a plain `string`, a
+named string without a text codec, or pointer wrappers around those types. The
+exception is load-local and does not apply to unrelated fields or loads without a
+version rule. Integer destinations require integer syntax
+and a value in the destination type's range. Float destinations accept finite JSON
+numbers representable by their destination precision. Dynamic numbers become
+`int64` for integer syntax and `float64` for fractional or exponent syntax, with
+range and finiteness checks. Named scalar types retain their identity. Durations
+decode only from strings accepted by `time.ParseDuration`; integers are rejected.
+Paired text scalars decode only from strings through `encoding.TextUnmarshaler`, and
+codec failures are classified without exposing application error text or input
+values.
+
+This decoder is available only through `Load`; ConfigKit exposes no generic document
+conversion API.
+
+## Typed projection and ownership
+
+ConfigKit can internally project a schema-valid application value directly into its
+owned canonical tree without YAML serialization. Projection includes every bound
+field, including ordinary zero values; `omitempty` has no effect. Struct fields keep
+binding order, dynamic map keys sort by decoded string, and sequences keep their
+order. Integers retain exact base-10 values, finite floats use their destination
+precision, durations use `time.Duration.String`, and paired text scalars use their
+canonical marshaled text.
+
+Nil pointers, maps, slices, and dynamic values project as null. Non-nil empty maps
+and slices remain empty containers, preserving the distinction. Recursive acyclic
+objects are supported. Cyclic values, non-finite floats, unsupported dynamic concrete
+types, invalid codec output, and depth/node-limit violations fail with safe schema
+classifications that omit codec error text.
+
+The same descriptor graph creates detached typed copies. Pointers, maps, slices,
+arrays, nested dynamic values, and shared references are recursively copied; shared
+pointer identity is not preserved as configuration meaning. Paired text scalars are
+rebuilt by unmarshaling their canonical text into fresh values, detaching private
+backing storage. Ignored and unexported struct fields are zeroed rather than copied.
+
+Private structural comparison operates on canonical trees. Mapping additions,
+removals, and descendant replacements retain semantic paths. A sequence is atomic:
+any sequence change reports the sequence path and never invents correspondence
+between old and new indices. Cross-kind and null/container changes replace the
+affected path.
+
+These mechanisms support decoding, resolution auditing, metadata,
+and rendering. They are not a public generic conversion or cloning API.
+
+## Safe failures
+
+Source failures use stable `source.*` codes and YAML failures use stable `yaml.*`
+codes declared by the root package. Diagnostics contain safe classifications,
+semantic paths when applicable, and available source coordinates. Raw parser,
+conversion, reader-error, and input text is not forwarded. Source labels and
+diagnostic messages are application-visible and therefore must never contain
+secrets; terminal control characters are escaped by `WriteDiagnostics`.

docs/consumers/README.md

@@ -0,0 +1,174 @@
+# Consumer Adoption Guide
+
+ConfigKit removes parser setup, strict decoding, presence bookkeeping, import and
+selected-overlay traversal, precedence, provenance, secret lookup, and safe inspection from
+applications. Consumers still own their configuration structs, defaults, semantic
+validation, schema-version policy, CLI parsing, runtime matching and conversion,
+resource checks, remote acquisition, and service initialization.
+
+The maintained [`examples/consumers`](../../examples/consumers) package demonstrates
+sanitized shapes using only ConfigKit and the Go standard library:
+
+| Shape | Demonstrated fit | Application code deliberately retained |
+| --- | --- | --- |
+| Narratio-like | Fresh defaults, explicit partial imports, artifact maps, recorded inherited defaults, normalization, and source ownership | Artifact meaning and the separate `model_profile` domain field |
+| Notarius-like | Canonical object bindings, a string-backed schema version accepting string or integer YAML, strict dynamic options, and `int64` dynamic integers | Catalog selection, allowed option keys, range-checked conversion to runtime `int` |
+| WeatherReporter-like | Defaults-only loading, report maps, canonical module objects, typed option unions, explicit CLI records, and typed secret startup | Report/module compatibility, rejection of explicitly empty domain lists, CLI parsing, and startup ordering |
+| Seriatim-like | Independent strict ordered speaker and autocorrect rule files | First-match and ordered replacement algorithms; no central application configuration file |
+| Bundled file | Simple native `fs.FS` source through ordinary `Load` | Selection and lifetime of the application-owned embedded filesystem |
+| Layered catalog | Embedded defaults with an import, a mapping underlay, an independent host main file, explicit false/zero input, and source-relative resource access | Domain validation and opening/interpreting the template resource |
+| Named presets | One-load sibling inheritance, explicit false, nested destination resolution, and source/derivation inspection | Choosing and executing a preset |
+
+The YAML under [`testdata`](../../examples/consumers/testdata) is loaded by the
+executable examples and ordinary tests. It contains no private application data,
+credentials, network calls, or dependency on a sibling checkout.
+
+The Notarius-shaped fixtures deliberately load both `version: 4` and
+`version: "4"` into the same string-backed application field. Its version checker
+still owns the supported identifier; fractional numeric input and unsupported
+integer identifiers remain negative examples.
+
+## Happy path
+
+An application defines ordinary types and passes one explicit source. Optional
+features appear only when the application needs them:
+
+```go
+result, err := configkit.Load[Config](configkit.File(path), configkit.Options[Config]{
+    Definition: rules,
+    Imports:    useDeclaredImports,
+    Overlay:    selectedConfigOverlay,
+    Overrides:  explicitlySetFlags,
+})
+if err != nil {
+    return err
+}
+return start(result.Config)
+```
+
+Simple consumers use neither imports nor selected overlays. A complex consumer can opt into
+both without redefining their syntax. ConfigKit overlays are configuration overlays;
+they do not select or replace an application's LLM, model, pipeline, report, or
+execution profile concepts.
+
+## Named sibling inheritance
+
+[`LoadPresets`](../../examples/consumers/inheritance.go) loads the maintained
+[`presets.yml`](../../examples/consumers/testdata/inheritance/presets.yml) in one
+call. `custom` inherits `enabled: false` from `base`, while its nested
+`settings.primary` changes the inherited `settings.secondary` result at the
+custom destination. The application struct has no `extends` field; ConfigKit
+consumes the relationship before strict typed decoding.
+
+The [executable example](../../examples/consumers/consumers_test.go) reads
+`Metadata.IsExplicit` for the inherited false value, then follows
+`Origin.Inheritance` back to the parent path while `Origin.Locations` identifies
+the declaring source. Applications still choose which preset to execute and
+validate domain meaning. The [configuration contract](../config.md#sibling-inheritance)
+owns exact lookup, precedence, cancellation, and migration rules.
+
+## Native filesystem and layered input
+
+[`LoadBundled`](../../examples/consumers/layered.go) keeps the simple `Load` shape:
+it selects a file in an application-owned embedded filesystem and needs no
+underlay setup. [`LoadCatalog`](../../examples/consumers/layered.go) uses
+`LoadLayered` with an imported embedded-defaults group, a separate
+`Mapping` group, and a host main file supplied by its caller. The groups
+compose strictly within themselves and recursively across precedence boundaries;
+the main file's explicit `false` and `0` replace lower values without being
+mistaken for omissions. Its validator owns allowed modes and resource-name policy.
+
+[`ReadWelcome`](../../examples/consumers/layered.go) follows the effective field's
+origin location to a source ID, queries `Result.SourceContext`, and opens the
+resource relative to that context's `BaseDir`. It does not assume the main file
+owns a retained underlay value. A composite origin needs an application choice;
+ConfigKit does not guess a directory. The context query is passive, while later
+resource reads observe the caller-owned filesystem or a freshly opened host root
+and may fail independently of the completed configuration load. The
+[configuration contract](../config.md#source-resource-contexts) owns exact
+lifetime and precedence rules.
+
+Known module catalogs should use canonical object entries with a module identifier
+and typed options. A small union struct is sufficient when the available option
+fields are known; validation selects which fields apply to each module. Runtime-
+selected catalogs may retain `map[string]any`, whose integers are `int64`; applications
+validate keys and ranges and convert only at their runtime boundary. Neither shape
+needs YAML reserialization, a parser hook, a ConfigKit registry, or a generic subtree
+conversion API.
+
+## Source-aware application path policy
+
+[`LoadNotariusPaths`](../../examples/consumers/consumers.go) is the maintained
+path-bearing example. Its application resolver uses `Resolution.InputInfo` and
+`Resolution.Source` before normalizing: relative CLI input uses an explicitly
+supplied invocation directory, retained defaults use the canonical main source,
+and a file-authored scalar uses its one declaring source. Absolute paths remain
+unchanged. Its executable test covers the matching effective YAML and explanation
+history, source-file ownership, and a symlink opened through an alias; canonical
+target-file directories, rather than the alias directory or process working
+directory, are the selected bases.
+
+The selected example policy leaves a relative value unchanged and emits a warning
+when a CLI base is absent or file provenance is missing or composite. That is an
+application choice, not a ConfigKit fallback: consumers can instead reject it or
+choose another explicit base. The example intentionally performs neither target
+existence checks nor confinement checks.
+
+## Intentional migration changes
+
+The examples preserve domain meaning while adopting one configuration convention:
+
+- Explicit empty strings, lists, zeroes, false values, and nulls remain intentional.
+  ConfigKit accepts an empty list structurally; WeatherReporter-shaped validation
+  rejects an explicitly or programmatically supplied empty module/template list as a
+  domain rule. Loaded and constructed values use the same validator.
+- Canonical module and object bindings replace string shorthand. Unknown fields and
+  incompatible option shapes fail at their semantic paths.
+- Schema versions remain string-backed in application types. A configured
+  `VersionRule` accepts string or strict decimal-integer YAML at its exact path and
+  supplies the spelling to both the checker and a plain string destination.
+- Integers inside dynamic options are portable `int64` values. Runtime `int`
+  conversion is explicit and range checked.
+- Strict YAML intentionally rejects duplicate keys, aliases, merge keys, unsupported
+  tags/scalars, trailing documents, and unknown typed fields. Diagnostics expose
+  stable classifications and safe paths, not copied parser text.
+- General environment-variable configuration overlays retire. Application CLI
+  parsers translate only explicitly set configuration flags into `Override` records.
+  Separate invocation state remains outside configuration.
+- Credential fields migrate to environment-name `Secret` references. Applications
+  explicitly call `LoadSecretsDir` before `Load` when they choose file bootstrap;
+  blocked empty variables remain blocked, and ordinary `Load` never changes the
+  process environment.
+
+### Selected-overlay migration
+
+To adopt the current selected-overlay API, rename `Options.Profile`,
+`LayerProfile`, and `CodeProfile*` references to their `Overlay` equivalents; move
+selected files from `profiles/<name>.yml` to `overlays/<name>.yml`; update any
+handling of the `overlay` layer and `overlay.*` diagnostic strings; then rebuild.
+The [configuration contract](../config.md#selected-overlays) is the canonical
+behavioral reference. Application-owned profile concepts, such as `model_profile`,
+are unchanged, and any CLI flag rename remains the application's decision.
+
+These examples are migration evidence, not completed changes to Narratio, Notarius,
+WeatherReporter, or Seriatim. Updating those repositories, their deployed YAML, CLI
+wiring, runtime catalogs, and operational documentation remains separate downstream
+work.
+
+## Maintained API examples
+
+Every nontrivial initial API sketch has a compiled example or a
+focused behavioral owner:
+
+| Roadmap surface | Maintained owner |
+| --- | --- |
+| `Load`, `NoSource`, validation, versions, resolution, `SecretEnv`, overrides, and explanation | Executable examples in [`example_test.go`](../../example_test.go) |
+| Source/import/selected-overlay pipeline rules and artifact defaults | Narratio-shaped executable example and fixture |
+| Canonical module objects and dynamic option handling | WeatherReporter- and Notarius-shaped examples and migration tests |
+| `LoadSecretsDir`, bootstrap reporting, typed lookup, CLI explanation | `Example_weatherStartup` |
+| Native filesystem, grouped underlays, programmatic mapping, retained resource context | `Example_nativeFilesystem`, `Example_layeredCatalog`, and their focused consumer tests |
+| Named sibling inheritance, presence, and derivation | `Example_inheritedPresets` and `TestPresetCatalogOneLoadAndDerivation` |
+| Results, metadata, diagnostics, effective output, and writer failures | Focused root-package load, provenance, rendering, and explanation tests |
+
+The package-level import-boundary test covers the consumer examples too: supported
+usage names no YAML dependency, parser type, parser option, or parser error chain.

docs/development.md

@@ -1,60 +1,169 @@
 # Development
 
-This is the contributor entry point for ConfigKit. Read the task-specific owners
-below before making changes. The repository is in pre-implementation: it has no
-Go module, packages, tests, or executable examples yet. The
-[component overview](internal/overview.md) owns the implementation inventory.
+Start here when contributing to ConfigKit. Read the task-specific owners below
+before making changes. The [component overview](internal/overview.md) maps
+implementation responsibilities; the [configuration contract](config.md) owns
+public behavior.
 
 ## Initial orientation
 
 1. Inspect the working tree and preserve unrelated changes.
-2. Read the architecture policy for code or design work.
-3. Read the policy, contract, and internal documents applicable to the task.
-4. Inspect relevant implementation and tests where they exist before changing them.
+2. Use the Policy Reading Guide below to select applicable policies.
+3. Read the contract and internal documents applicable to the task.
+4. Inspect the relevant implementation and behavioral tests before changing them.
+
+## Policy Reading Guide
+
+| Policy | Read before… |
+| --- | --- |
+| [Policy set provenance](policy/meta.md) | Adopting policies, checking upstream revisions, or updating the adopted policy set. |
+| [Agents](policy/agents.md) | Recommending, planning, or implementing repository changes. |
+| [Architecture](policy/architecture.md) | Planning or changing Go library code or its structure. |
+| [Testing](policy/testing.md) | Selecting validation for code changes, or adding, changing, removing, or evaluating tests. |
+| [Documentation](policy/documentation.md) | Writing, revising, or reorganizing documentation. |
+| [OSS](policy/oss.md) | Adding or updating dependencies or incorporated third-party material, or changing licensing or attribution. |
+| [Release](policy/release.md) | Preparing or publishing a release, changing release procedures, or making versioning and compatibility decisions. |
+
+- Read applicable policies before making decisions they govern; multiple policies
+  may apply.
+- Select policies using the task triggers above. Follow cross-references to
+  relevant sections when needed to resolve a concrete question.
+- Reuse policies already available in context; reread when changed or no longer
+  available.
+- Expand reading when the task's scope expands.
+- When revising a policy itself, read that policy and any provisions elsewhere
+  affected by the revision.
 
 ## Task-specific reading guide
 
 | Task | Read |
 | --- | --- |
-| Repository orientation or component responsibility | [Architecture policy](policy/architecture.md) and [component overview](internal/overview.md) |
-| Documentation changes | [Documentation policy](policy/documentation.md) and the owning document |
-| Architecture decisions or future work | [Documentation policy](policy/documentation.md), [initial target design](roadmap/initial.md), and relevant ADRs listed below |
-| Code and test changes | [Architecture policy](policy/architecture.md), [testing policy](policy/testing.md), and owning contracts/tests as they are introduced |
-| Examples or copyable assets | The owning implemented contract and related maintained examples, once available |
-| Release preparation | [Release policy](policy/release.md) and [release-readiness gaps](roadmap/release-readiness.md); the operational runbook will be added before release |
+| Repository orientation or component responsibility | [Component overview](internal/overview.md) |
+| Documentation changes | The owning document |
+| Licensing, dependencies, attribution, or release-document changes | [Project grant](../COPYRIGHT) and [attribution](oss/attribution.md); release changes also follow the release procedure |
+| Architecture decisions or future work | [Deferred scope](roadmap/deferred.md) and relevant ADRs listed below |
+| Code and test changes | The owning contract and tests from the map below |
+| Examples or copyable assets | The owning implemented contract and [consumer adoption guide](consumers/README.md) |
+| Release preparation | [Release procedure](release.md) |
 
 Accepted decisions:
 
 - [Separate composition and overlay](adr/0001-separate-composition-and-overlay.md)
 - [Own YAML semantics behind a private parser boundary](adr/0002-own-yaml-semantics.md)
 - [Preserve presence and record application resolution](adr/0003-preserve-presence-and-resolution-history.md)
-
 - [Secret references and explicit bootstrap](adr/0004-secret-references-and-explicit-bootstrap.md)
 - [Explicit overrides and safe explanation](adr/0005-explicit-overrides-and-safe-explanation.md)
+- [Keep the public facade root-owned](adr/0006-public-facade.md)
 
-For cross-cutting changes, follow every applicable row. The
-[implementation plan](roadmap/implementation.md) owns the ordered stages and their
-acceptance checks; all remain pending until implementation evidence is recorded.
+For cross-cutting changes, follow every applicable row. Completed implementation
+and remediation plans are preserved in Git history at `cb5b435`; use current
+contracts and the component overview for ongoing work. For example:
+
+```sh
+git show cb5b435:docs/roadmap/remediation.md
+```
+
+Release-candidate, publication, and verification work follows the operational
+[release procedure](release.md). Its single publication command validates the
+committed candidate and publishes only the intended refs.
+
+The completed string-and-integer schema-version implementation and remediation
+records are preserved in Git history at `244104f`. The
+[configuration contract](config.md#application-schema-versions) owns current behavior.
+
+The completed source-origins and public-facade roadmaps, implementation plan, and
+resolved review findings are preserved in Git history at `5760614`, for example
+`git show 5760614:docs/roadmap/remediation.md`. The earlier source-origins staged
+plan remains at `28e7fc5:docs/roadmap/implementation.md`. Current resolution
+behavior belongs to the [configuration contract](config.md#recorded-application-resolution),
+and current facade ownership belongs to the [component overview](internal/overview.md).
 
 ## Baseline validation
 
-For the current documentation-only repository:
+The completed filesystem-source and underlay roadmap, original feature request,
+implementation plan, and resolved remediation record are preserved in Git history
+at `b604aa1` under `docs/roadmap/`. Current behavior belongs to the
+[configuration contract](config.md#layered-loading). Built-in sibling
+inheritance is now part of the [configuration contract](config.md#sibling-inheritance).
+The completed request, roadmap, plan, and resolved review findings are preserved
+in Git history at `83c59ea` under `docs/roadmap/`.
+
+The completed overlay rename plan and release-workflow simplification record are
+preserved in Git history at `73ce6e9` under `docs/roadmap/`. Current overlay
+behavior belongs to the [configuration contract](config.md#selected-overlays),
+and release operations belong to the [release procedure](release.md).
+
+Install Go 1.25.0 or a supported patched/newer Go toolchain. Acquire declared
+dependencies explicitly before entering an offline development or validation
+environment:
 
 ```sh
-git diff --check
+go mod download
 ```
 
-Also inspect new untracked documents, verify changed local links and heading
-fragments, and review paths, examples, ownership, and current-versus-planned
-claims. The command above does not check links or untracked content.
+Run the everyday check with Bash 3.2 or newer and Git:
 
-Go validation is not runnable until a module and packages exist. The scaffolding
-change must establish and verify library test, vet, and build commands here,
-including their prerequisites. Do not use an application binary build as the
-library baseline. Add executable-example and other checks when those artifacts
-are introduced; do not document nonexistent tools as operational.
+```sh
+./scripts/check.sh
+```
 
-Once code exists, use focused checks while iterating and validation proportionate
-to the change under the testing policy. Documentation-only work does not require
-Go checks unless it changes behavior-bearing examples or commands they validate.
-Release validation is a separate, stricter gate governed by release policy.
+[The script](../scripts/check.sh) runs from the repository root regardless of the
+invocation directory. It checks Go formatting without rewriting files, checks
+staged/unstaged and untracked whitespace, then runs `go test ./...`,
+`go vet ./...`, and `go build ./...`, stopping on the first failure. It uses the
+installed Go toolchain by default, honors an explicit `GOTOOLCHAIN`, and disables
+dependency downloads. Acquire dependencies and any selected toolchain beforehand.
+Format reported Go files with `gofmt -w <files>`.
+
+The default suite includes executable examples, maintained consumer fixtures,
+local documentation-link checks, and the dependency import-boundary check.
+It must stay deterministic and runnable without network access or credentials.
+Still inspect new/untracked content and review paths, examples, ownership, and
+current-versus-planned claims; automated checks do not replace content review.
+
+Use focused checks while iterating, with validation proportionate to the change
+under the testing policy. Documentation-only work normally needs the local-link
+check below and whitespace review; behavior-bearing examples and commands also
+need execution. Use `go test -race ./...` for ownership or concurrency changes.
+The [publication command](release.md#4-publish-the-committed-candidate) invokes
+the release checker once. It performs one minimum-toolchain offline race-suite
+run, one full vet pass, and Linux cross-builds using readonly module mode.
+It already covers examples, links, and package boundaries; do not additionally
+run the everyday checker just to repeat those checks. CI never gates a release.
+
+## Task-to-test map
+
+Commands run from the repository root after dependency acquisition. These are
+starting points for focused iteration; run the everyday check before handing off
+code changes. Use the component overview to find the corresponding implementation.
+
+| Task | Behavioral test owners | Focused command |
+| --- | --- | --- |
+| YAML syntax, diagnostics, parser limits | [Adapter tests](../internal/yaml/parse_test.go), [source translation](../internal/engine/parse_test.go) | `go test ./internal/yaml` and `go test ./internal/engine -run '^TestParseSource'` |
+| File/reader access, imports, globs, containment | [Sources](../internal/engine/source_test.go), [FIFO](../internal/engine/source_fifo_test.go), [imports](../internal/engine/imports_test.go), [globs](../internal/engine/glob_test.go) | `go test ./internal/engine -run 'Source\|Import\|Glob\|Filesystem\|Nonregular\|RegularFile'` |
+| Native filesystem and mapping sources | [Native acquisition](../internal/engine/native_filesystem_test.go), [filesystem facade](../facade_filesystem_test.go), [mapping facade](../facade_mapping_test.go) | `go test ./internal/engine -run 'NativeFilesystem'` and `go test . -run 'TestFacade'` |
+| Composition, selected overlays, CLI precedence | [Composition](../internal/engine/compose_test.go), [overlay](../internal/engine/overlay_test.go), [selected overlays](../internal/engine/selected_overlay_test.go), [overrides](../internal/engine/override_test.go) | `go test ./internal/engine -run 'Compose\|Overlay\|Override'` |
+| Sibling inheritance, provenance, history, sensitivity | [Expansion](../internal/engine/inheritance_test.go), [destination scopes](../internal/engine/inheritance_walk_test.go), [origins](../internal/engine/inheritance_origin_test.go), [history](../internal/engine/inheritance_history_test.go), [secrets](../internal/engine/inheritance_secret_test.go), [public loading](../facade_inheritance_test.go) | `go test ./internal/engine -run 'Inheritance\|Inherited'` and `go test . -run '^TestFacadeInheritance\|^TestFacadeInheritedSecrets'` |
+| Layered loading and source equivalence | [Grouped lifecycle](../internal/engine/load_request_test.go), [layered facade](../facade_layered_test.go), [equivalence](../facade_equivalence_test.go) | `go test ./internal/engine -run '^TestGrouped'`, `go test . -run '^TestFacadeLayered'`, and `go test . -run '^TestEquivalentSourceForms'` |
+| Schema, defaults, projection, cloning | [Schema](../internal/engine/schema_test.go), [decoding](../internal/engine/decode_test.go), [projection](../internal/engine/projection_test.go) | `go test ./internal/engine -run 'Schema\|Decode\|Projection\|Clone\|Inline\|CompareDocument'` |
+| Lifecycle, resolution, validation, callback ownership | [Loading](../internal/engine/load_test.go), [resolution](../internal/engine/resolution_test.go), [validation](../internal/engine/validation_test.go), [ownership](../internal/engine/callback_ownership_test.go), [independence](../internal/engine/independence_test.go) | `go test ./internal/engine -run 'Load\|Resolution\|Validation\|Validator\|Hook\|Callback\|Parallel'` |
+| Paths, metadata, provenance | [Paths](../internal/engine/path_test.go), [metadata](../internal/engine/metadata_test.go), [provenance](../internal/engine/provenance_test.go) | `go test ./internal/engine -run 'Path\|Metadata\|Provenance\|Queries'` |
+| Passive resource contexts | [Engine contexts](../internal/engine/resource_context_test.go), [public contexts](../facade_resource_context_test.go) | `go test ./internal/engine -run 'Resource'` and `go test . -run 'SourceContext'` |
+| Secrets, bootstrap, redaction, explanation | [References](../internal/engine/secret_reference_test.go), [bootstrap](../internal/engine/secrets_test.go), [rendering](../internal/engine/render_test.go), [explanation](../internal/engine/explain_test.go) | `go test ./internal/engine -run 'Secret\|Bootstrap\|Effective\|Explain\|Explanation\|History\|Sensitivity'` |
+| Consumer examples and migration fixtures | [Consumer tests](../examples/consumers/consumers_test.go), [native and layered examples](../examples/consumers/layered_test.go), [API examples](../example_test.go) | `go test ./examples/consumers` and `go test . -run '^Example'` |
+| Assembly and layered scaling evidence | [Assembly benchmarks](../internal/engine/assembly_bench_test.go), [layered benchmarks](../internal/engine/underlay_bench_test.go) | `go test ./internal/engine -run '^$' -bench '^BenchmarkUnderlay' -benchmem`; repeat with `^BenchmarkCompose` and `^BenchmarkOverlay` |
+| Inheritance scaling evidence | [Expansion benchmarks](../internal/engine/inheritance_bench_test.go) | `go test ./internal/engine -run '^$' -bench '^BenchmarkInheritance' -benchmem` |
+| Documentation links and dependency isolation | [Link checks](../documentation_test.go), [import boundary](../import_boundary_test.go), [public boundary](../public_boundary_test.go) | `go test . -run 'TestLocalDocumentationLinks\|TestDependencyImportBoundary\|TestPublicFacadeBoundary'` |
+| Development and release checker behavior | [Shell regression](../release_check_test.go) | `go test . -run 'TestCheckScripts\|TestDevelopmentCheck'` |
+| Guarded release publication and recovery | [Publication regression](../release_publish_test.go) | `go test . -run '^TestReleasePublication'` |
+
+## Fuzz validation
+
+Run the bounded fuzz targets independently from the repository root. These exact
+commands keep each campaign short and constrain concurrent workers:
+
+```sh
+go test ./internal/engine -run='^$' -fuzz='^FuzzParsePath$' -fuzztime=30s -parallel=2
+go test ./internal/yaml -run='^$' -fuzz='^FuzzParseDocument$' -fuzztime=30s -parallel=2
+go test ./internal/engine -run='^$' -fuzz='^FuzzCompositionAndOverlay$' -fuzztime=30s -parallel=2
+```

docs/internal/extraction.md

@@ -0,0 +1,418 @@
+# Source Extraction Inventory
+
+This inventory records reusable implementation evidence from sibling applications.
+Those checkouts are review inputs only: ConfigKit does not import them, and its
+build and tests must not require them. ConfigKit's current contracts and roadmap
+govern every adaptation.
+
+## Inspected revisions
+
+| Application | Revision | Worktree | Role |
+| --- | --- | --- | --- |
+| Narratio | `b68435128be1e24b94fc7ec259d6e9093669fd99` | Clean `main` tracking `origin/main` | Primary parsing, composition, import, profile, presence, defaults, resolution, and inspection source |
+| WeatherReporter | `5d306a202471e10fe98923a1df27d0b0fce5c666` | Clean `main` tracking `origin/main` | Secrets bootstrap and simple-consumer/defaults/options evidence |
+| Notarius | `77ae132e5609916da40dcd4fcc749c000a63cbac` | Clean `main` tracking `origin/main` | Canonical binding, string-version, and dynamic-option migration evidence |
+| Seriatim | `0fc92f364316c874d366b00cdc884a33e1900b25` | Clean `main` tracking `origin/main` | Independent ordered speaker/autocorrect rule evidence |
+
+These revisions were inspected on 2026-09-06. Paths below are relative to each
+application repository. Record later source revisions and adaptations here when
+the owning implementation work extracts a symbol or case.
+
+## Adaptation rules
+
+- Copy and generalize only the smallest applicable mechanism or behavioral case.
+- Replace upstream YAML nodes, application types, commands, logging, digests, and
+  provider registries with ConfigKit-owned boundaries.
+- Preserve strictness, deterministic behavior, and useful failure coverage while
+  changing expectations that conflict with ConfigKit's accepted contracts.
+- Use sanitized local fixtures only. Audio, transcripts, credentials, private
+  configuration, and whole application package trees are application-only.
+- Record the exact copied/generalized symbols and tests in the owning section when
+  extraction occurs. Assignment prose records the original work boundary; dated
+  implementation records state what was actually generalized.
+
+## Narratio evidence
+
+### Source parsing and strict input
+
+Assigned to the YAML/source implementation:
+
+- Production: `internal/config/load.go` functions `decodeStrictYAML`,
+  `decodeStrictYAMLFromReader`, and `LoadSessionBytesWithOptions`; and
+  `internal/config/composition.go` functions `parseCompositionDocument`,
+  `parseCompositionBytes`, and `buildCompositionNode`.
+- Cases: `TestLoadersRejectTrailingYAMLDocuments`,
+  `TestStrictYAMLRejectsParserExposedEmptyTrailingDocument`, and
+  `TestStrictYAMLAcceptsSingleDocumentAndRejectsUnknownFields` in
+  `internal/config/loader_strict_test.go`; plus duplicate-key, alias, non-mapping,
+  malformed-input, scalar spelling, presence, declaration-order, and source-label
+  coverage in `TestParseCompositionDocumentRetainsPresenceOwnershipAndDeclarationOrder`
+  and `TestParseCompositionDocumentRejectsAmbiguousOrMalformedYAML`.
+- Preserve: labeled reader/byte input, strict unknown-field intent, rejection of
+  trailing documents (including an empty second document), duplicate detection,
+  and source-aware failures.
+- Adapt: translate v4 parser nodes into ConfigKit's private document tree, apply
+  ConfigKit's scalar grammar and limits, and replace raw parser errors with safe
+  diagnostics. Narratio's application decoders and YAML node types are not copied.
+
+Implementation record (2026-09-06): the labeled byte/reader ownership and strict
+single-document cases above were generalized into `source.go`, `parse.go`, and
+`internal/yaml`. No production line was copied verbatim. ConfigKit adds byte and
+tree ceilings, shared atomic reader claims, regular-file checks, exact numeric
+lexemes, parser-depth calibration, ConfigKit-owned locations, safe diagnostic
+codes, and an AST import-boundary regression. Application typed decoding, parser
+errors, YAML node types, and session-specific loaders were not retained.
+
+### Strict composition
+
+Assigned to document composition:
+
+- Production: `mergeAdditiveComposition`, `mergeAdditiveCompositions`,
+  `validateAdditiveClaims`, `appendCompositionClaims`, `mergeAdditiveNodes`,
+  `newCompositionConflict`, and cloning/path/source helpers in
+  `internal/config/composition.go`.
+- Cases: `TestMergeAdditiveCompositionJoinsOnlyDisjointMappings`,
+  `TestMergeAdditiveCompositionRejectsEveryDuplicateClass`, and
+  `TestMergeAdditiveCompositionReportsAllClaimingSources`.
+- Preserve: recursive joining of disjoint mappings, collisions for every overlapping
+  non-mapping value (including equal values and sequences), all claimant sources,
+  deterministic traversal, and nonmutation of inputs.
+- Adapt: empty mappings follow ConfigKit's no-child operation rule; paths use the
+  ConfigKit semantic path model; both precise locations and composite origins are
+  retained. Default values never participate in strict composition.
+
+Implementation record (2026-09-06): `composeDocuments`, its pre-order claim
+collection, conflict construction, and recursive mapping join in `compose.go` adapt
+the assigned production symbols. `TestComposeDocumentsJoinsDisjointMappingsAndTracksClaims`,
+`TestComposeDocumentsRejectsEveryPresentNonMappingOverlap`, and
+`TestComposeDocumentsReportsAllClaimantsAtExactLocations` adapt the assigned cases.
+The intentional empty-mapping difference is covered separately: empty mappings retain
+container provenance but contribute no child claims. No other semantic deviation
+from the extracted additive composer was required.
+
+### Imports
+
+Assigned to explicit import traversal and glob handling:
+
+- Production: `loadPipelineCompositionSources`,
+  `splitPipelineCompositionEnvelope`, `loadPipelineImports`, and related ownership
+  structures in `internal/config/pipeline_composition.go`.
+- Cases: `TestSplitPipelineCompositionEnvelopePreservesInputAndDeclarationOrder`,
+  `TestSplitPipelineCompositionEnvelopeRejectsMalformedShapesWithoutMutation`,
+  `TestLoadPipelineCompositionImportsDisjointFieldsAndTracksOwnership`,
+  `TestLoadPipelineCompositionMergesDisjointKeyedEntries`,
+  `TestLoadPipelineCompositionRejectsBaseConflictsWithAllSources`,
+  `TestLoadPipelineCompositionRejectsUnsafeOrInvalidImports`,
+  `TestLoadPipelineCompositionRejectsSameFileAliasesAndImportedComposition`,
+  `TestLoadPipelineCompositionReportsImportedParseAndSchemaSources`, and
+  `TestLoadPipelineCompositionKeepsRelativePathsRootBased`.
+- Preserve: explicit declarations, declaration-order traversal, disjoint
+  composition, conflict attribution, malformed/unreadable target failures, directive
+  removal, and imported parse/schema source labels.
+- Adapt: replace the root-only `composition` envelope with recursive
+  `_configkit.imports`; add path and glob declarations, bounded depth-first graph
+  traversal, canonical containment, cycle/diamond routes, and fixed source IDs.
+  Canonical paths—not `os.SameFile`—define identity, so hard links remain distinct.
+
+Path-import implementation record (2026-09-06): `splitImportDirectives`,
+`parseImportDeclaration` (now in `directives.go`), `importFilesystem` (now in
+`filesystem.go`), and `importTraversal.visitPath`/`loadImportedDocuments` in
+`imports.go` adapt the assigned envelope, loading, source,
+and failure mechanics. The corresponding ConfigKit tests adapt the assigned
+declaration-order, disjoint composition, keyed-entry, all-source conflict, unsafe
+target, alias, imported parse/schema, and relative-resolution cases. ConfigKit adds
+recursive bounded DFS, `os.OpenRoot` confinement, canonical symlink identity,
+cycle/diamond route locations, optional-path semantics, aggregate budgets, and
+fragment version-placement enforcement. That checkpoint parsed glob syntax behind an
+explicit unsupported gate that the subsequent glob implementation removed; hard
+links intentionally replace Narratio's same-file rejection with path identity.
+
+Glob-import implementation record (2026-09-06): ConfigKit retains the extracted
+declaration order, import failures, composition, and identity cases while adding the
+new `expandImportGlob`, `readGlobMatches`, and pattern-validation mechanisms in
+`glob.go`. Focused cases cover lexical ordering, multiple declarations, overlap,
+directories, hard links, contained and escaping symlinks, unmatched declarations,
+malformed and recursive patterns, escaped metacharacters, character classes,
+permission failures, explicit `conf.d` use, and entry/candidate budgets. This work
+has no Narratio production equivalent; it uses the selected standard-library
+`path.Match` and bounded `File.ReadDir` adaptation rather than its flat loader.
+
+### Upstream profiles and ConfigKit selected overlays
+
+The following upstream symbols and case names retain their original profile
+terminology. ConfigKit adapts their selected-overlay behavior without renaming the
+upstream evidence:
+
+- Production: `mergeOverlayComposition`, `mergeOverlayNodes`,
+  `selectPipelineProfile`, `loadPipelineProfileOverlays`, and
+  `loadedProfileOverlay`.
+- Cases: `TestLoadPipelineProfilesSelectDefaultAndExplicitOverlay`,
+  `TestLoadPipelineProfileSelectionErrors`,
+  `TestPipelineProfileNamesRejectControlCharacters`,
+  `TestLoadPipelineProfilesValidateEveryDeclaredOverlay`,
+  `TestLoadPipelineProfileOverlaySemantics`,
+  `TestLoadPipelineProfileRejectsNullAndKindChanges`, and
+  `TestLoadPipelineProfilePairResolvesIndependentEffectivePipelines`.
+- Preserve: recursive mapping overlay, atomic scalar/sequence replacement,
+  deterministic selection failures, source ownership, and independent results.
+- Adapt: load only the selected fixed overlay path; lowercase `default` means no
+  selection. ConfigKit permits null and cross-kind replacement and does not support
+  declared defaults, inheritance, arbitrary overlay paths, or validating every
+  unselected overlay.
+
+Implementation record (2026-09-06, updated 2026-09-23): `overlayDocuments`,
+`mergeOverlayMappings`, `loadSelectedOverlayDocument`, and
+`overlayDirectiveDiagnostics` adapt the assigned merge, selection, loading, and
+ownership mechanics. `TestOverlayDocumentsRecursesMappingsAndReplacesAtomicSubtrees`,
+`TestLoadAppliesSelectedOverlayAfterBaseAndBeforeDefaults`, selected-overlay
+selection/error, directive/version, containment, and budget cases adapt the assigned
+tests. ConfigKit
+uses exactly one fixed selected `.yml` source, permits null and cross-kind replacement,
+retains displaced descendant history, rejects any overlay directive or version-path
+contribution, and counts the overlay in aggregate budgets. Narratio's declared
+default, multi-overlay validation, inheritance-like application conventions, and
+null/kind restrictions were not retained.
+
+### Effective inspection and provenance
+
+Assigned to layered metadata, redaction, rendering, and explanation:
+
+- Production: `EffectivePipelineValues`, `EffectivePipelineSources`,
+  `MarshalEffectivePipeline`, `effectivePipelineFieldPaths`,
+  `effectivePipelineOwners`, and composition `semanticRecords`/
+  `compactSemanticRecords`.
+- Cases: `TestCompositionCanonicalOutputsAreDeterministic`,
+  `TestEffectivePipelineValuesIgnoreEquivalentSourceLayout`,
+  `TestConfigValidateAndShowPipelineOnlyAreSideEffectFree`,
+  `TestConfigSourcesReportsStableOwnership`,
+  `TestConfigSourcesReportsCanonicalFamilyAndPublishOrigins`,
+  `TestConfigSourcesPreservesProfileOwnershipThroughFamilyExpansion`, and
+  `TestConfigSourcesReportsRootImportProfileAndDefaultOwnership`.
+- Preserve: deterministic effective projection, stable logical paths, source
+  ownership, side-effect-free inspection, and domain-attribution evidence.
+- Adapt: project directly from ConfigKit-owned typed values without YAML round trips;
+  add line/column locations, composite origins, complete operation history, detached
+  records, and redaction. Narratio commands, diff/digest APIs, generated artifact
+  attribution, campaign logic, and party expansion remain application-owned.
+
+Layered-provenance implementation record (2026-09-06): ConfigKit integrated its
+previously extracted source claims, overlay displacement records, typed baseline,
+and audited resolution snapshots in `load_metadata.go`. The representative
+`TestLayeredProvenanceAgreesWithResolvedSnapshot` adapts Narratio's stable ownership,
+profile ownership, deterministic effective projection, and side-effect-free
+inspection cases across one default/import/overlay/resolution workflow. ConfigKit
+adds chronological descendant history for parent and whole-sequence operations,
+composite empty-mapping origins, canonical resolution reasons/dependencies, private
+snapshot agreement, defensive nested copies, and concurrent load isolation. Value
+That checkpoint deliberately left rendering, redaction, explanation, commands,
+generated attribution, diffs, and digests outside its scope.
+
+Effective-rendering implementation record (2026-09-06): ConfigKit adapts Narratio's
+deterministic effective-output and side-effect-free inspection cases in
+`classifySecretPaths`, `redactedDocument`, `Result.WriteEffective`, and the private
+`internal/yaml.Write` adapter. Tests cover stable sorted mappings, preserved sequence
+order, explicit indentation/line/document formatting, tagged containers, dynamic
+current and historical paths, fixed-point dependency cycles, nil/empty distinctions,
+resolved values, text-scalar snapshot reuse, application YAML-hook isolation,
+non-disclosure through failures and record formatting, caller mutation, and writer
+failures. Unlike Narratio's marshal/reparse path, ConfigKit renders only its owned
+frozen tree and substitutes redaction before the upstream dumper boundary. Historical
+value explanation and secret references were implemented at their later owning
+boundaries and are exercised by the consumer startup example below.
+
+### Defaults, presence, and domain resolution
+
+Assigned across schema, decoding, resolution, validation, and consumer examples:
+
+- Production: `NormalizeConfig.UnmarshalYAML`, `outputPathWasSet`,
+  `applyPipelineDefaults` and its component default helpers, `Resolve`,
+  `ResolveLoadedPipelineCampaign`, `mergeCampaignSession`, `selectStableInput`, and
+  application-supplied byte loading in `internal/app/config_loader.go`.
+- Cases: `TestNormalizeLoadAndValidate`,
+  `TestRepresentativeLoadDefaultsAndValidation`,
+  `TestMarshalEffectivePipelineRendersStablePublicConfiguration`,
+  `TestPipelineCampaignRegistryStrictDecode`,
+  `TestCampaignSessionMergeFillsStableInputs`,
+  `TestCampaignSessionMergeSessionOverridesStableInputs`,
+  `TestLoadWithSessionOptionsCarriesExplicitProfilePresence`, and the maintained
+  extraction-example coverage in `TestMaintainedExtractionExamplesPreservePublishedContracts`.
+- Preserve: fresh defaults, explicit-presence-sensitive domain decisions, strict
+  nested types, stable input selection, application-supplied labeled bytes, and
+  validation after resolution.
+- Adapt: presence comes from metadata rather than custom YAML hooks or pointer/zero
+  guesses; explicit empty and null values are retained; defaults are cloned and
+  application-owned; every domain mutation is recorded. Campaign/session fallback,
+  search paths, fetching, storage, and concrete default values remain in Narratio.
+
+Implementation record (2026-09-06): ConfigKit generalized Narratio's fresh-default,
+strict nested-type, and explicit-presence cases into `decode.go` and
+`decode_test.go`. The decoder applies the owned document tree over a detached typed
+baseline, treats mappings recursively and sequences atomically, preserves explicit
+false/zero/empty/null, rejects unknown nested fields, and returns private presence
+and default/input origin artifacts. Unlike Narratio's custom YAML hooks and
+pointer/zero inference, presence comes directly from the parsed tree and equal-valued
+input remains explicit. ConfigKit also adds destination-width numeric checks,
+dynamic `int64`/`float64`, exact arrays, duration strings, paired text codecs, safe
+multi-error collection, and repeated-result isolation. Resolution, validation,
+consumer defaults, and all campaign/session algorithms remain assigned to later
+work.
+
+Lifecycle integration record (2026-09-06): the public single-source `Load` boundary
+combines the already extracted labeled-source and strict-decoding mechanisms with
+Narratio's fresh-default and presence expectations. ConfigKit adds an application-
+defined pre-decode string-version check, defaults-only `NoSource` operation,
+detached base/default metadata and source reports, and explicit gates for every
+later lifecycle option. No application loader or production line was copied.
+Narratio's resolution, validation, import/profile, campaign/session, and command
+behavior remains assigned to its later owning work.
+
+Resolution implementation record (2026-09-06): ConfigKit adapted the intent of
+Narratio's `Resolve`, `applyPipelineDefaults`, component default helpers,
+`mergeCampaignSession`, and `selectStableInput` into a generic recorded resolver in
+`resolution.go`. The synthetic timeout/artifact cases preserve explicit-input
+decisions, derived dependencies, normalization, and map copy/writeback without
+copying campaign/session algorithms or concrete defaults. ConfigKit adds structural
+mutation auditing, container coverage, helper/path consistency checks, equal-value
+intent, coalesced repeated writes, private before/after snapshots, deterministic
+record ordering, and safe hook diagnostics. Semantic validation remains assigned to
+the next lifecycle work.
+
+Validation implementation record (2026-09-06): ConfigKit generalized Narratio's
+`TestNormalizeLoadAndValidate`, `TestRepresentativeLoadDefaultsAndValidation`,
+strict registry decoding, and maintained extraction-example expectations into the
+post-resolution `Validation` lifecycle and synthetic consumer examples. ConfigKit
+keeps domain rules application-owned, resolves schema-valid missing/dynamic report
+paths to nearest input locations, collects independent warnings/errors, and audits
+the full typed projection to reject validator mutation. Live resources, registries,
+campaign/session logic, commands, and application runtime initialization were not
+extracted.
+
+### Secrets bootstrap
+
+Assigned to the explicit bootstrap operation:
+
+- Production: `loadSecretsFromConfigWithDependencies`, `validateSecretDirectory`,
+  `validateSecretFile`, `readAPIKeyFile`, and
+  `internal/fileops/read_bounded.go` function `ReadFileBounded`.
+- Cases: `TestLoadSecretsFromConfigLoadsValidFiles`,
+  `TestLoadSecretsFromConfigPreservesExistingEnv`,
+  `TestLoadSecretsFromConfigRelativeDirUsesCWD`,
+  `TestLoadSecretsFromConfigMissingDirFails`,
+  `TestLoadSecretsFromConfigUnreadableValidEntryFails`,
+  `TestLoadSecretsFromConfigRejectsUnsafeModes`,
+  `TestLoadSecretsFromConfigRejectsNonRegularAndOversizedEntries`, and
+  `TestLoadSecretsFromConfigRejectsSymlinkAndAncestorReplacement`.
+- Preserve: bounded reads, valid environment names, existing variables (including
+  empty values) winning, regular-file checks, symlink rejection, and failure cases.
+- Adapt: use ConfigKit's deterministic report/preflight/apply state machine and
+  fixed budgets. Logging, configuration-driven implicit invocation, private-mode
+  conventions, and application API-key plumbing remain in Narratio.
+
+Implementation record (2026-09-06): `LoadSecretsDir`, `readSecretsEntries`,
+`readSecretValue`, and the private environment/file seams in `secrets.go` adapt
+Narratio's bounded-read and preserve-existing mechanisms at revision
+`b68435128be1e24b94fc7ec259d6e9093669fd99`. The corresponding tests retain its
+valid-file, existing-variable (including empty), missing/permission/read,
+nonregular, symlink, and byte-limit cases. ConfigKit validates invalid entries
+rather than skipping them, permits ordinary deployment permission modes, resolves
+the selected directory symlink, performs complete preflight before mutation, and
+emits per-file safe records without application configuration or logging.
+
+## WeatherReporter evidence
+
+### Secrets bootstrap
+
+Assigned to the explicit bootstrap operation:
+
+- Production: `loadSecrets`, `applySecrets`, `restoreEnvironment`, `secretValue`,
+  and `environmentValue` in `internal/config/secrets.go`.
+- Cases: `TestLoadSecretsDisabledLeavesEnvironmentUnchanged`,
+  `TestLoadSecretsOverwritesExistingEnvironment`,
+  `TestLoadSecretsTrimsOneTrailingLineEnding`,
+  `TestLoadSecretsRejectsInvalidDirectoryEntries`,
+  `TestLoadSecretsRejectsMissingDirectory`,
+  `TestLoadFileSecretDirectoryFailureLeavesEnvironmentUnchanged`,
+  `TestLoadFileValidationFailureLeavesSecretEnvironmentUnset`, and
+  `TestApplySecretsRollsBackOnEnvironmentFailure`.
+- Preserve: separate read/preflight and apply mechanisms, one-newline handling,
+  invalid-name/type/read coverage, no writes after preflight failure, and controlled
+  environment-write failure coverage.
+- Adapt: existing variables—including empty ones—are skipped, never overwritten;
+  application failures produce an accurate partial report and no rollback. Skip
+  entries are not read. Bootstrap is explicitly invoked and remains independent of
+  YAML loading and semantic validation.
+
+Implementation record (2026-09-06): the same `secrets.go` state machine adapts
+WeatherReporter's `loadSecrets`/`applySecrets` separation, environment-name check,
+regular-file rejection, and exact one-LF/CRLF removal at revision
+`5d306a202471e10fe98923a1df27d0b0fce5c666`. Tests adapt its newline matrix,
+invalid-entry and preflight-no-write cases, and controlled application failure.
+The overwrite/rollback expectation is intentionally replaced by existing-winner,
+presence-recheck, and partial-progress statuses; no configuration loader invokes
+the bootstrap.
+
+### Defaults, explicit presence, and module options
+
+Assigned to consumer-shaped examples and migration checks:
+
+- Production: `Load`, `mergeFile`, `normalizeReportModules`,
+  `traverseReportModules`, `normalizeModuleOptions`, and `decodeKnownOptions`.
+- Cases: `TestDefaults`, `TestOutputDirectoryLoading`,
+  `TestOutputDirectoryValidationIsConsistentForLoadedAndConstructedConfigs`,
+  `TestLoadMinimalExampleConfig`,
+  `TestReportDistributorPathTemplatesSetTracksExplicitEmptyList`,
+  `TestValidateReportModuleKeysWithoutMutatingOptions`,
+  `TestReportModuleOverridesNormalizesConstructedOptionsWithoutMutatingConfig`,
+  `TestReportModuleOverridesCanonicalizesTypedPointerOptions`,
+  `TestReportDistributorPathOverridesConsistentForLoadedAndConstructedConfig`,
+  `TestReportModuleValidationConsistentForLoadedAndConstructedConfig`,
+  `TestConstructedReportOverridesUseExportedFields`, and
+  `TestConstructedExplicitEmptyReportOverridesAreRejected`.
+- Preserve: defaults-only use, consistent loaded/constructed outcomes, explicit
+  empty-list domain rejection, typed module-specific options, normalization without
+  mutating caller input, and unknown-field rejection.
+- Adapt: ConfigKit permits empty lists structurally and exposes their presence to
+  application validation. Object bindings replace shorthand, explicitly set flags
+  become CLI override records, and general environment overlays retire. Report
+  semantics, registries, rendering, and module option validation remain application
+  responsibilities.
+
+Consumer-example implementation record (2026-09-06): at Narratio revision
+`b68435128be1e24b94fc7ec259d6e9093669fd99`, the maintained consumer cases adapt
+`TestMaintainedExtractionExamplesPreservePublishedContracts`,
+`TestConfigValidateAndShowPipelineOnlyAreSideEffectFree`, and the stable source-
+ownership tests into a sanitized partial-import/artifact fixture. ConfigKit replaces
+application composition envelopes and command output with `_configkit.imports`,
+typed defaults, recorded resolution, metadata, and explanation. Artifact meaning,
+model/pipeline profiles, commands, and generated-domain attribution remain in the
+example application layer; no production function was copied.
+
+At WeatherReporter revision `5d306a202471e10fe98923a1df27d0b0fce5c666`,
+`TestDefaults`, explicit-empty-list cases, loaded/constructed consistency cases, and
+nonmutating module-option normalization were adapted into the WeatherReporter-shaped
+fixtures and tests in [`examples/consumers`](../../examples/consumers). ConfigKit's
+detached defaults replace source mutation, canonical module objects replace string
+shorthand, ordinary validation retains empty-list and option compatibility rules,
+and explicit `Override` records replace external configuration-field overlays. The
+startup example composes the separately implemented bootstrap report, typed secret
+lookup, and explanation APIs without copying WeatherReporter's registries or
+rendering/runtime modules.
+
+Notarius revision `77ae132e5609916da40dcd4fcc749c000a63cbac` supplied
+binding/version/dynamic-option migration evidence only. The local example uses an
+ordinary canonical object, a string `VersionRule`, ConfigKit's `int64` dynamic
+integer convention, and application range checking; it does not copy a catalog or
+environment overlay. Seriatim revision
+`0fc92f364316c874d366b00cdc884a33e1900b25` supplied ordered rule-file evidence.
+The local examples load speaker and autocorrect files independently and keep their
+matching/replacement algorithms outside ConfigKit. Neither source is a build or test
+dependency.
+
+## Application-only material
+
+Do not extract application commands, filesystem discovery, logging, runtime
+initialization, remote clients, LLM/provider setup, audio/transcript fixtures,
+configuration digests, report rendering, campaign/session algorithms, or consumer
+resource validation into ConfigKit. Maintained consumer examples use only small
+synthetic types and fixtures to prove that these responsibilities remain
+straightforward.

docs/internal/overview.md

@@ -1,10 +1,46 @@
 # Internal Component Overview
 
-ConfigKit has no implemented Go packages or components yet. This document will
-inventory components and link to their current contracts and focused internal
-documentation as they are introduced.
+ConfigKit exposes one supported root `configkit` package. The root owns public
+named types, declaration comments, constructors, and explicit conversion/wrapper
+code. It delegates loading and frozen inspection to `internal/engine` through
+private state; public signatures and fields do not expose engine types.
 
-The [architecture policy](../policy/architecture.md) owns binding boundaries and
-invariants. The [initial target design](../roadmap/initial.md) describes planned
-behavior; it is not an inventory of implemented features. See the
-[development guide](../development.md) for contributor orientation and validation.
+Implemented component owners:
+
+- `internal/engine` owns host and native-filesystem source acquisition,
+  grouped strict composition, recursive precedence assembly, and destination-local
+  sibling inheritance before typed decoding. It also owns schema
+  inspection, lifecycle coordination, callback auditing,
+  provenance/history, passive source-context retention, secret resolution and
+  bootstrap, and safe inspection rendering. It never imports the root package.
+- Root `Source`, `Filesystem`, `Input`, `Underlay`, `Path`, `Secret`, records,
+  lifecycle callbacks, results, and bootstrap reports are root-defined wrappers
+  or records. Callback wrappers pass only live engine context during a callback;
+  `Result.Config` is detached and its private inspection remains frozen
+  independently.
+- Root conversion files explicitly cross the path, record, callback, secret, and
+  error boundaries. There are no public aliases, anonymous engine embeddings, or
+  public engine bridge methods.
+- `internal/document` owns the parser-independent ordered tree and cloning.
+  `internal/yaml` is the sole upstream YAML adapter and parser/dumper boundary.
+- Engine mechanism tests own source, composition, inheritance, decoding,
+  callback, provenance,
+  source-context, secret, history, rendering, and bootstrap behavior. Root tests
+  own public API compatibility, facade integration, documentation links, and
+  dependency/public boundary checks. Consumer examples remain under
+  `examples/consumers`.
+
+Dependency direction is root to engine to document/YAML support. The root may
+import only `internal/engine` among project internal production packages; engine
+and its supporting packages do not import root. The root boundary test enforces
+these constraints and rejects exported aliases, fields, or signatures involving
+internal types.
+
+The [configuration contract](../config.md) owns implemented YAML and lifecycle
+semantics. The [consumer adoption guide](../consumers/README.md) owns application
+guidance. The [architecture policy](../policy/architecture.md) owns contributor
+boundaries, and [ADR 0006](../adr/0006-public-facade.md) records the facade
+decision. See the [development guide](../development.md) for validation commands
+and [release procedure](../release.md) for source-candidate gates. [ADR
+0009](../adr/0009-sibling-inheritance.md) records why inheritance is a built-in
+post-assembly structural operation.

docs/oss/attribution.md

@@ -0,0 +1,38 @@
+# Open Source Attribution Notices
+
+## Standard Repository Policies
+
+Material: `docs/policy/meta.md`, `docs/policy/oss.md`,
+`docs/policy/documentation.md`, `docs/policy/agents.md`,
+`docs/policy/architecture.md`, `docs/policy/testing.md`, and
+`docs/policy/release.md`; root `AGENTS.md`; and the Policy Reading Guide in
+`docs/development.md`, adapted for this repository.
+
+Copyright (C) 2026 Eric Rakestraw
+
+SPDX-License-Identifier: CC-BY-SA-4.0
+
+License and notices: [CC BY-SA 4.0](licenses/CC-BY-SA-4.0.txt) |
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/COPYRIGHT) |
+[LICENSE](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/LICENSE).
+
+[Source](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843).
+
+## go-yaml v4
+
+Selected module: `go.yaml.in/yaml/v4` at `v4.0.0-rc.6`.
+
+Copyright 2011-2019 Canonical Ltd
+
+Copyright 2025 The go-yaml Project Contributors
+
+Copyright 2006-2010 Kirill Simonov
+
+SPDX-License-Identifier: Apache-2.0 AND MIT
+
+License and notices: [Apache 2.0](licenses/Apache-2.0.txt) |
+[MIT](licenses/MIT.txt) |
+[NOTICE](https://github.com/yaml/go-yaml/blob/1c17b9cee72bf81ae73a8be50fbd7dd3a9985125/NOTICE) |
+[LICENSE](https://github.com/yaml/go-yaml/blob/1c17b9cee72bf81ae73a8be50fbd7dd3a9985125/LICENSE).
+
+[Source](https://github.com/yaml/go-yaml/tree/1c17b9cee72bf81ae73a8be50fbd7dd3a9985125).

docs/oss/licenses/Apache-2.0.txt

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

docs/oss/licenses/CC-BY-SA-4.0.txt

@@ -0,0 +1,170 @@
+Creative Commons Attribution-ShareAlike 4.0 International
+
+ Creative Commons Corporation (“Creative Commons”) is not a law firm and does not provide legal services or legal advice. Distribution of Creative Commons public licenses does not create a lawyer-client or other relationship. Creative Commons makes its licenses and related information available on an “as-is” basis. Creative Commons gives no warranties regarding its licenses, any material licensed under their terms and conditions, or any related information. Creative Commons disclaims all liability for damages resulting from their use to the fullest extent possible.
+
+Using Creative Commons Public Licenses
+
+Creative Commons public licenses provide a standard set of terms and conditions that creators and other rights holders may use to share original works of authorship and other material subject to copyright and certain other rights specified in the public license below. The following considerations are for informational purposes only, are not exhaustive, and do not form part of our licenses.
+
+Considerations for licensors: Our public licenses are intended for use by those authorized to give the public permission to use material in ways otherwise restricted by copyright and certain other rights. Our licenses are irrevocable. Licensors should read and understand the terms and conditions of the license they choose before applying it. Licensors should also secure all rights necessary before applying our licenses so that the public can reuse the material as expected. Licensors should clearly mark any material not subject to the license. This includes other CC-licensed material, or material used under an exception or limitation to copyright. More considerations for licensors.
+
+Considerations for the public: By using one of our public licenses, a licensor grants the public permission to use the licensed material under specified terms and conditions. If the licensor’s permission is not necessary for any reason–for example, because of any applicable exception or limitation to copyright–then that use is not regulated by the license. Our licenses grant only permissions under copyright and certain other rights that a licensor has authority to grant. Use of the licensed material may still be restricted for other reasons, including because others have copyright or other rights in the material. A licensor may make special requests, such as asking that all changes be marked or described.
+
+Although not required by our licenses, you are encouraged to respect those requests where reasonable. More considerations for the public.
+
+Creative Commons Attribution-ShareAlike 4.0 International Public License
+
+By exercising the Licensed Rights (defined below), You accept and agree to be bound by the terms and conditions of this Creative Commons Attribution-ShareAlike 4.0 International Public License ("Public License"). To the extent this Public License may be interpreted as a contract, You are granted the Licensed Rights in consideration of Your acceptance of these terms and conditions, and the Licensor grants You such rights in consideration of benefits the Licensor receives from making the Licensed Material available under these terms and conditions.
+
+Section 1 – Definitions.
+
+     a.	Adapted Material means material subject to Copyright and Similar Rights that is derived from or based upon the Licensed Material and in which the Licensed Material is translated, altered, arranged, transformed, or otherwise modified in a manner requiring permission under the Copyright and Similar Rights held by the Licensor. For purposes of this Public License, where the Licensed Material is a musical work, performance, or sound recording, Adapted Material is always produced where the Licensed Material is synched in timed relation with a moving image.
+
+     b.	Adapter's License means the license You apply to Your Copyright and Similar Rights in Your contributions to Adapted Material in accordance with the terms and conditions of this Public License.
+
+     c.	BY-SA Compatible License means a license listed at creativecommons.org/compatiblelicenses, approved by Creative Commons as essentially the equivalent of this Public License.
+
+     d.	Copyright and Similar Rights means copyright and/or similar rights closely related to copyright including, without limitation, performance, broadcast, sound recording, and Sui Generis Database Rights, without regard to how the rights are labeled or categorized. For purposes of this Public License, the rights specified in Section 2(b)(1)-(2) are not Copyright and Similar Rights.
+
+     e.	Effective Technological Measures means those measures that, in the absence of proper authority, may not be circumvented under laws fulfilling obligations under Article 11 of the WIPO Copyright Treaty adopted on December 20, 1996, and/or similar international agreements.
+
+     f.	Exceptions and Limitations means fair use, fair dealing, and/or any other exception or limitation to Copyright and Similar Rights that applies to Your use of the Licensed Material.
+
+     g.	License Elements means the license attributes listed in the name of a Creative Commons Public License. The License Elements of this Public License are Attribution and ShareAlike.
+
+     h.	Licensed Material means the artistic or literary work, database, or other material to which the Licensor applied this Public License.
+
+     i.	Licensed Rights means the rights granted to You subject to the terms and conditions of this Public License, which are limited to all Copyright and Similar Rights that apply to Your use of the Licensed Material and that the Licensor has authority to license.
+
+     j.	Licensor means the individual(s) or entity(ies) granting rights under this Public License.
+
+     k.	Share means to provide material to the public by any means or process that requires permission under the Licensed Rights, such as reproduction, public display, public performance, distribution, dissemination, communication, or importation, and to make material available to the public including in ways that members of the public may access the material from a place and at a time individually chosen by them.
+
+     l.	Sui Generis Database Rights means rights other than copyright resulting from Directive 96/9/EC of the European Parliament and of the Council of 11 March 1996 on the legal protection of databases, as amended and/or succeeded, as well as other essentially equivalent rights anywhere in the world.
+
+     m.	You means the individual or entity exercising the Licensed Rights under this Public License. Your has a corresponding meaning.
+
+Section 2 – Scope.
+
+     a.	License grant.
+
+          1. Subject to the terms and conditions of this Public License, the Licensor hereby grants You a worldwide, royalty-free, non-sublicensable, non-exclusive, irrevocable license to exercise the Licensed Rights in the Licensed Material to:
+
+               A. reproduce and Share the Licensed Material, in whole or in part; and
+
+               B. produce, reproduce, and Share Adapted Material.
+
+          2. Exceptions and Limitations. For the avoidance of doubt, where Exceptions and Limitations apply to Your use, this Public License does not apply, and You do not need to comply with its terms and conditions.
+
+          3. Term. The term of this Public License is specified in Section 6(a).
+
+          4. Media and formats; technical modifications allowed. The Licensor authorizes You to exercise the Licensed Rights in all media and formats whether now known or hereafter created, and to make technical modifications necessary to do so. The Licensor waives and/or agrees not to assert any right or authority to forbid You from making technical modifications necessary to exercise the Licensed Rights, including technical modifications necessary to circumvent Effective Technological Measures. For purposes of this Public License, simply making modifications authorized by this Section 2(a)(4) never produces Adapted Material.
+
+          5. Downstream recipients.
+
+               A. Offer from the Licensor – Licensed Material. Every recipient of the Licensed Material automatically receives an offer from the Licensor to exercise the Licensed Rights under the terms and conditions of this Public License.
+
+               B. Additional offer from the Licensor – Adapted Material. Every recipient of Adapted Material from You automatically receives an offer from the Licensor to exercise the Licensed Rights in the Adapted Material under the conditions of the Adapter’s License You apply.
+
+               C. No downstream restrictions. You may not offer or impose any additional or different terms or conditions on, or apply any Effective Technological Measures to, the Licensed Material if doing so restricts exercise of the Licensed Rights by any recipient of the Licensed Material.
+
+          6. No endorsement. Nothing in this Public License constitutes or may be construed as permission to assert or imply that You are, or that Your use of the Licensed Material is, connected with, or sponsored, endorsed, or granted official status by, the Licensor or others designated to receive attribution as provided in Section 3(a)(1)(A)(i).
+
+     b.	Other rights.
+
+          1. Moral rights, such as the right of integrity, are not licensed under this Public License, nor are publicity, privacy, and/or other similar personality rights; however, to the extent possible, the Licensor waives and/or agrees not to assert any such rights held by the Licensor to the limited extent necessary to allow You to exercise the Licensed Rights, but not otherwise.
+
+          2. Patent and trademark rights are not licensed under this Public License.
+
+          3. To the extent possible, the Licensor waives any right to collect royalties from You for the exercise of the Licensed Rights, whether directly or through a collecting society under any voluntary or waivable statutory or compulsory licensing scheme. In all other cases the Licensor expressly reserves any right to collect such royalties.
+
+Section 3 – License Conditions.
+
+Your exercise of the Licensed Rights is expressly made subject to the following conditions.
+
+     a.	Attribution.
+
+          1. If You Share the Licensed Material (including in modified form), You must:
+
+               A. retain the following if it is supplied by the Licensor with the Licensed Material:
+
+                    i.	identification of the creator(s) of the Licensed Material and any others designated to receive attribution, in any reasonable manner requested by the Licensor (including by pseudonym if designated);
+
+                    ii.	a copyright notice;
+
+                    iii. a notice that refers to this Public License;
+
+                    iv.	a notice that refers to the disclaimer of warranties;
+
+                    v.	a URI or hyperlink to the Licensed Material to the extent reasonably practicable;
+
+               B. indicate if You modified the Licensed Material and retain an indication of any previous modifications; and
+
+               C. indicate the Licensed Material is licensed under this Public License, and include the text of, or the URI or hyperlink to, this Public License.
+
+          2. You may satisfy the conditions in Section 3(a)(1) in any reasonable manner based on the medium, means, and context in which You Share the Licensed Material. For example, it may be reasonable to satisfy the conditions by providing a URI or hyperlink to a resource that includes the required information.
+
+          3. If requested by the Licensor, You must remove any of the information required by Section 3(a)(1)(A) to the extent reasonably practicable.
+
+     b.	ShareAlike.In addition to the conditions in Section 3(a), if You Share Adapted Material You produce, the following conditions also apply.
+
+          1. The Adapter’s License You apply must be a Creative Commons license with the same License Elements, this version or later, or a BY-SA Compatible License.
+
+          2. You must include the text of, or the URI or hyperlink to, the Adapter's License You apply. You may satisfy this condition in any reasonable manner based on the medium, means, and context in which You Share Adapted Material.
+
+          3. You may not offer or impose any additional or different terms or conditions on, or apply any Effective Technological Measures to, Adapted Material that restrict exercise of the rights granted under the Adapter's License You apply.
+
+Section 4 – Sui Generis Database Rights.
+
+Where the Licensed Rights include Sui Generis Database Rights that apply to Your use of the Licensed Material:
+
+     a.	for the avoidance of doubt, Section 2(a)(1) grants You the right to extract, reuse, reproduce, and Share all or a substantial portion of the contents of the database;
+
+     b.	if You include all or a substantial portion of the database contents in a database in which You have Sui Generis Database Rights, then the database in which You have Sui Generis Database Rights (but not its individual contents) is Adapted Material, including for purposes of Section 3(b); and
+
+     c.	You must comply with the conditions in Section 3(a) if You Share all or a substantial portion of the contents of the database.
+For the avoidance of doubt, this Section 4 supplements and does not replace Your obligations under this Public License where the Licensed Rights include other Copyright and Similar Rights.
+
+Section 5 – Disclaimer of Warranties and Limitation of Liability.
+
+     a.	Unless otherwise separately undertaken by the Licensor, to the extent possible, the Licensor offers the Licensed Material as-is and as-available, and makes no representations or warranties of any kind concerning the Licensed Material, whether express, implied, statutory, or other. This includes, without limitation, warranties of title, merchantability, fitness for a particular purpose, non-infringement, absence of latent or other defects, accuracy, or the presence or absence of errors, whether or not known or discoverable. Where disclaimers of warranties are not allowed in full or in part, this disclaimer may not apply to You.
+
+     b.	To the extent possible, in no event will the Licensor be liable to You on any legal theory (including, without limitation, negligence) or otherwise for any direct, special, indirect, incidental, consequential, punitive, exemplary, or other losses, costs, expenses, or damages arising out of this Public License or use of the Licensed Material, even if the Licensor has been advised of the possibility of such losses, costs, expenses, or damages. Where a limitation of liability is not allowed in full or in part, this limitation may not apply to You.
+
+     c.	The disclaimer of warranties and limitation of liability provided above shall be interpreted in a manner that, to the extent possible, most closely approximates an absolute disclaimer and waiver of all liability.
+
+Section 6 – Term and Termination.
+
+     a.	This Public License applies for the term of the Copyright and Similar Rights licensed here. However, if You fail to comply with this Public License, then Your rights under this Public License terminate automatically.
+
+     b.	Where Your right to use the Licensed Material has terminated under Section 6(a), it reinstates:
+
+          1. automatically as of the date the violation is cured, provided it is cured within 30 days of Your discovery of the violation; or
+
+          2. upon express reinstatement by the Licensor.
+
+     c.	For the avoidance of doubt, this Section 6(b) does not affect any right the Licensor may have to seek remedies for Your violations of this Public License.
+
+     d.	For the avoidance of doubt, the Licensor may also offer the Licensed Material under separate terms or conditions or stop distributing the Licensed Material at any time; however, doing so will not terminate this Public License.
+
+     e.	Sections 1, 5, 6, 7, and 8 survive termination of this Public License.
+
+Section 7 – Other Terms and Conditions.
+
+     a.	The Licensor shall not be bound by any additional or different terms or conditions communicated by You unless expressly agreed.
+
+     b.	Any arrangements, understandings, or agreements regarding the Licensed Material not stated herein are separate from and independent of the terms and conditions of this Public License.
+
+Section 8 – Interpretation.
+
+     a.	For the avoidance of doubt, this Public License does not, and shall not be interpreted to, reduce, limit, restrict, or impose conditions on any use of the Licensed Material that could lawfully be made without permission under this Public License.
+
+     b.	To the extent possible, if any provision of this Public License is deemed unenforceable, it shall be automatically reformed to the minimum extent necessary to make it enforceable. If the provision cannot be reformed, it shall be severed from this Public License without affecting the enforceability of the remaining terms and conditions.
+
+     c.	No term or condition of this Public License will be waived and no failure to comply consented to unless expressly agreed to by the Licensor.
+
+     d.	Nothing in this Public License constitutes or may be interpreted as a limitation upon, or waiver of, any privileges and immunities that apply to the Licensor or You, including from the legal processes of any jurisdiction or authority.
+
+Creative Commons is not a party to its public licenses. Notwithstanding, Creative Commons may elect to apply one of its public licenses to material it publishes and in those instances will be considered the “Licensor.” Except for the limited purpose of indicating that material is shared under a Creative Commons public license or as otherwise permitted by the Creative Commons policies published at creativecommons.org/policies, Creative Commons does not authorize the use of the trademark “Creative Commons” or any other trademark or logo of Creative Commons without its prior written consent including, without limitation, in connection with any unauthorized modifications to any of its public licenses or any other arrangements, understandings, or agreements concerning use of licensed material. For the avoidance of doubt, this paragraph does not form part of the public licenses.
+
+Creative Commons may be contacted at creativecommons.org.

docs/oss/licenses/MIT.txt

@@ -0,0 +1,18 @@
+MIT License
+
+Copyright (c) <year> <copyright holders>
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and
+associated documentation files (the "Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the
+following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial
+portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT
+LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO
+EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE
+USE OR OTHER DEALINGS IN THE SOFTWARE.

docs/policy/agents.md

@@ -0,0 +1,91 @@
+# Agent Policy
+
+**Base Policy Version:** 1.3
+
+**Last Updated**: 2026-09-28
+
+**Upstream Source:** [Standard Repository Policies](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/agents.md)
+
+## Purpose
+
+Agents must read and follow these rules.
+
+## Implementation Discipline
+
+**KEY PRINCIPLES:** Write the simplest idiomatic code that satisfies the user's
+request. Do not implicitly strengthen requirements, restrictions, or guarantees
+beyond what the user actually requested.
+
+**Keep implementation machinery proportionate.** Use straightforward,
+idiomatic code and introduce only the machinery needed to support the requested
+behavior and flexibility. Optimize for conceptual simplicity and
+maintainability, not for the fewest lines, fewest options, or narrowest product
+surface.
+
+**Do not invent restrictions.** Do not reject, prohibit, constrain, cap,
+harden, or otherwise narrow behavior unless required by the user, an explicit
+repository contract, or an unavoidable correctness constraint. Preserve
+operator and caller choice where policy has not been established. If an
+additional restriction appears advisable, present it as a decision rather than
+silently implementing it.
+
+A correctness constraint must follow from the requested behavior or an
+established invariant, not from the convenience of the chosen implementation.
+Explain the specific failure it prevents and why a less restrictive
+implementation cannot satisfy the contract.
+
+**Do not invent guarantees.** Do not strengthen public contracts, guarantees,
+or invariants beyond those expressly requested by the user.
+
+**Use the standard library.** For example: in almost every case, the best
+approach to copying files is to use the standard library. Writing custom code to
+implement power-loss protection at the application level, or to guard against
+bad actors with privileged and concurrent access to the host's filesystem,
+is wasteful, unnecessary, and not idiomatic. Stick to the simple, standard, and
+idiomatic approach unless another path is expressly requested by the user.
+
+**An implementation detail is not repository policy.** Tests and documentation
+must not elevate incidental behavior into a durable guarantee or restriction
+unless that behavior was expressly selected as part of the contract. Existing
+explicit contracts remain authoritative; changing or weakening one requires a
+deliberate decision rather than being inferred from this principle.
+
+Agent-authored plans, tests, documentation, and prior implementations are not
+evidence that an additional restriction was deliberately approved. Identify the
+authorizing requirement or decision; when that authority is unclear, surface
+the ambiguity rather than treating repetition as approval.
+
+## Git Commit Policy
+
+By default, commit each completed, nonempty unit of work using a
+concise, plain-English message describing what changed. This policy is standing
+authorization to create those local commits; a separate user request is not
+required. An explicit user instruction to leave work uncommitted takes precedence.
+
+A unit of work is a focused, reviewable outcome, including its relevant tests and
+documentation.
+Complete the appropriate validation before committing. If work is incomplete or
+validation is blocked, report that state accurately.
+
+Before committing:
+
+1. Run `git status --short` and review the relevant diff, including any staged
+   changes. Identify changes that predate the current unit of work.
+2. Exclude secrets, local environment files, generated junk, and unrelated changes.
+3. Stage only the files or hunks belonging to the completed unit. Use `git add .`
+   only when every included change belongs to that unit. Preserve unrelated
+   staged and unstaged work.
+4. Review `git diff --staged` and run appropriate checks for the change. Reuse
+   successful checks for unchanged content.
+5. Review `git log --oneline -n 10` and use
+   `git commit -m "<concise plain-English commit message>"`.
+6. Report the commit identifier and any remaining uncommitted work.
+
+If the unit cannot be safely separated from pre-existing work, leave it uncommitted
+and explain the overlap rather than silently including that work. If a commit
+fails, preserve the changes and report the failure; do not bypass hooks.
+
+Default commit authorization does not authorize pushing, publishing, amending,
+resetting, reverting, or rewriting history. Those actions require a separate user
+instruction. Do not use `git commit -a` or `git commit --no-verify` to bypass the
+staging and validation discipline above.

docs/policy/architecture.md

@@ -1,18 +1,55 @@
 # Architecture Policy
 
-**Base Policy Version:** 1.0
+**Base Policy Version:** 1.3
 
-**Last Updated:** 2026-09-06
+**Last Updated**: 2026-09-29
 
-## Purpose and applicability
+**Upstream Source:** [Standard Repository Policies](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/architecture.md)
+
+## Purpose And Ownership
+
+The adopted policy defines the application's purpose and the architectural
+constraints contributors must follow. It owns system boundaries, responsibility
+and dependency rules, established invariants, and explicit non-goals.
+
+Describe the concrete package inventory and implementation mechanics in internal
+documentation. Link to canonical public contracts for their exact behavior and
+to ADRs for decision rationale.
 
 ConfigKit is an opinionated Go library for consistent YAML configuration loading
-and resolution across consuming applications. This policy governs contributions
-now; it does not claim that the target features are implemented. The
-[component overview](../internal/overview.md) owns implementation inventory and
-[initial roadmap](../roadmap/initial.md) owns unimplemented target behavior.
+and resolution across consuming applications. The [component overview](../internal/overview.md)
+owns implementation inventory, the [configuration contract](../config.md) owns
+implemented behavior, and the [deferred scope](../roadmap/deferred.md) preserves
+deferred scope.
 
-## Success criteria
+## Adopted Constraints And Implemented Structure
+
+Architectural constraints govern current and future development. Record
+implemented structure accurately, proposals and implementation status in the
+roadmap, and significant decisions and rationale in ADRs. Describe a target
+structure as implemented when its changes land.
+
+Constraints must reflect deliberately selected requirements and decisions.
+Do not promote incidental implementation choices into architectural invariants.
+
+## Success Criteria
+
+ConfigKit prioritizes a coherent configuration model: consistency and
+predictability take precedence over flexibility for accommodating individual
+downstream conventions. Consumers should learn one set of rules, not different
+combination or presence semantics depending on the source format or consuming
+application. Distinct operations such as strict composition and intentional
+overlay express distinct purposes within that model.
+
+Consumers should be able to load once and receive a complete, validated
+configuration with inspectable provenance for its final values, including
+defaults and recorded application-derived values. Configuration and metadata
+together must distinguish explicit zero, false, empty, and null input from
+omission; ordinary Go values alone need not encode those distinctions.
+Application-owned resolution belongs within the recorded loading lifecycle, so
+consumers need no subsequent generic merging, defaulting, or provenance
+reconstruction. This does not transfer domain execution or runtime resource
+management into ConfigKit.
 
 1. **Reduce application infrastructure:** Can applications delete substantial
    configuration infrastructure while retaining clear ownership of their domain
@@ -21,8 +58,11 @@ now; it does not claim that the target features are implemented. The
    configuration model, with only the flexibility needed to express genuine
    application requirements?
 
-Both criteria must hold. ConfigKit should not preserve divergent consumer
-conventions merely for compatibility, nor impose restrictions that prevent useful
+Both criteria must hold. Minimize consumer loading and processing code subject
+to the consistency, presence, and provenance principles above, rather than
+trading those principles for consumer-specific shortcuts. ConfigKit should not
+preserve divergent consumer conventions merely for compatibility, nor impose
+restrictions that prevent useful
 domain information from being expressed. Prefer a canonical representation using
 existing primitives before adding another mechanism. Extend the model when a
 concrete requirement cannot be accommodated cleanly, not simply because a
@@ -48,10 +88,10 @@ existing primitives cannot accommodate it cleanly, and show how the extension
 preserves a coherent model. Application-specific interpretation and validation
 remain appropriate. Reuse Narratio's applicable infrastructure under these
 boundaries, and keep simple consumers independent of optional composition
-features. The [consumer API design](../roadmap/initial.md#consumer-api-design)
-describes the proposed surface; this policy does not claim it is implemented.
+features. The [consumer adoption guide](../consumers/README.md) demonstrates the
+implemented surface against representative simple and complex shapes.
 
-## Responsibility boundaries
+## Responsibility Boundaries
 
 ConfigKit owns configuration input processing and the coordination of decoding,
 resolution, validation, and inspection. Applications own their configuration
@@ -68,34 +108,85 @@ must never run implicitly as part of configuration loading.
 Remote data can enter through application-supplied input without introducing a
 network provider into the library.
 
-## Public API and dependency direction
+## Loading Lifecycle
+
+Configuration loading is a synchronous, complete-on-return operation. A successful
+load provides the final configuration and inspection metadata after the configured
+processing and validation phases complete. A failed load reports diagnostics and
+returns no usable partial result. The normal application pattern is one load near
+startup; applications may explicitly initiate additional loads.
+
+ConfigKit releases its library-owned loading handles before returning and remains
+inactive until the application explicitly invokes it again. It performs no
+background watching, refresh, or mutation of published results. Caller-owned
+resources and application callback effects remain the caller's responsibility.
+The [configuration contract](../config.md#completion-and-resource-lifetime) owns
+the precise completion and ownership behavior. The proposed decision record is
+[ADR 0008](../adr/0008-complete-on-return-loading.md).
+
+## Public API And Dependency Direction
 
 Keep one small, coherent public surface for the supported lifecycle. Simple
-single-document consumers must not need import, profile, or provider machinery.
+single-document consumers must not need import, overlay, or provider machinery.
 Do not expose parser-specific nodes, errors, or extension hooks through the
 public API. Parser integration belongs behind a private boundary, as recorded
 in [ADR 0002](../adr/0002-own-yaml-semantics.md).
 
+The root `configkit` package is the sole supported consumer import path. Public
+named types stay root-owned and may hold private delegated implementation state;
+their exported signatures, fields, and method sets must not expose internal
+types or acquire internal methods through anonymous embedding. Root production
+code may depend inward on a cohesive engine and its supporting internal packages,
+but internal production packages must not import the root. Explicit forwarding
+and local conversion are acceptable where they preserve type identity,
+ownership, callback lifetime, and inspection behavior. The accepted root-wrapper
+boundary and its migration rationale are recorded in
+[ADR 0006](../adr/0006-public-facade.md); the implemented layout is described in
+the [component overview](../internal/overview.md).
+
 Separate input access, document processing, composition, decoding, metadata, and
 rendering responsibilities without prescribing an interface or package for each.
 Dependencies must preserve those boundaries; package splits and abstractions
 must earn their complexity. Do not impose a full application or hexagonal
 framework on this library.
 
-## Configuration integrity
+## Configuration Integrity
 
-Composition and intentional overlay are distinct operations. Composition must
-not silently become last-wins override through file ordering. The decision and
-alternatives are recorded in [ADR 0001](../adr/0001-separate-composition-and-overlay.md).
+Within a configuration tier, independent contributions use strict composition:
+shared mappings combine recursively, while overlapping non-mapping definitions
+are conflicts, including equal values. Between precedence tiers, intentional
+overlay combines mappings recursively, retains omitted lower-priority children,
+and replaces other present values according to the existing overlay rules.
+Tier precedence is explicit; traversal order within a tier establishes stable
+reporting, not permission to override. The distinction and its rationale are
+recorded in [ADR 0001](../adr/0001-separate-composition-and-overlay.md).
+
+The main document and its imports form a strictly composed tier. Explicit
+underlay groups compose strictly within each group, then combine recursively
+from lowest to highest beneath the main tier. Source acquisition kind does not
+determine its precedence role. Input-specific constraints, including CLI path
+rules and opt-in version ownership, remain part of the configuration contract. Consistent combination
+semantics do not require identical acquisition or lifetime behavior from every
+source kind.
+
+After source precedence is complete, built-in sibling `extends` relationships
+resolve structurally in the same parser-independent representation, using the
+existing recursive overlay rules. This adds neither an acquired source nor a
+consumer registration mechanism. Enclosing relationships precede nested
+destination-local resolution; typed defaults, application resolution, and
+secret lookup retain their existing lifecycle roles. The [configuration
+contract](../config.md#sibling-inheritance) owns the exact syntax and presence
+rules, and [ADR 0009](../adr/0009-sibling-inheritance.md) records the rationale.
 
 ConfigKit must define supported YAML semantics explicitly rather than inherit
 parser defaults. Processing order and diagnostics must be deterministic for the
 same inputs and options. Invalid input must not produce a successful usable
 configuration. Do not run application hooks on invalid typed configuration.
 
-User-controlled precedence is application defaults, composed base, selected
-profile, then explicitly supplied CLI overrides. Applications own flag parsing;
-ConfigKit owns overlay semantics and provenance. Domain resolution follows these
+User-controlled precedence is application defaults, ordered underlays, composed
+main input, selected overlay, then explicitly supplied CLI overrides.
+Applications own flag parsing; ConfigKit owns overlay semantics and provenance.
+Domain resolution follows these
 inputs and must remain recorded, not become a hidden override channel.
 
 Preserve node-based composition until the effective input is ready for typed
@@ -103,14 +194,14 @@ decoding. Preserve presence and source information through processing. Ordinary
 values must not be used to infer whether input was absent. Final configuration,
 metadata, and effective inspection must agree, including application resolution
 changes; see [ADR 0003](../adr/0003-preserve-presence-and-resolution-history.md).
-Safe historical values and an explanation renderer belong to the initial target,
+Safe historical values and an explanation renderer are part of the implemented contract,
 including superseded/deleted paths and effective source attribution. Inspection
 must agree with the final typed snapshot and apply historical sensitivity rules.
 See [ADR 0005](../adr/0005-explicit-overrides-and-safe-explanation.md).
-Detailed syntax and operation tables belong to the target roadmap until their
-current configuration contract is implemented.
+Detailed syntax and operation tables belong to the
+[current configuration contract](../config.md).
 
-## Ownership and confidentiality
+## Ownership And Confidentiality
 
 Returned configuration and metadata must not share mutable state across loads.
 ConfigKit must not mutate a result after returning it. Ordinary exported Go
@@ -131,11 +222,12 @@ forwarded blindly when they can include raw input. Do not log configuration
 implicitly. Applications remain responsible for classifying their secrets and
 for safe messages supplied by their hooks.
 
-## Scope boundaries
+## Scope Boundaries
 
 Do not introduce automatic directory discovery, network providers, arbitrary
 merge strategies, additional configuration languages, or application runtime
 management without concrete consumer evidence and an explicit design decision.
-The roadmap owns the complete deferred-feature inventory. Significant boundary
+The [deferred scope](../roadmap/deferred.md#explicit-non-goals-and-deferred-scope)
+owns the deferred-feature inventory. Significant boundary
 changes require an ADR and corresponding policy/contract updates; implementation
 convenience alone is not a reason to broaden the public API.

docs/policy/documentation.md

@@ -1,126 +1,176 @@
 # Documentation Policy
 
-**Base Policy Version:** 1.0
+**Base Policy Version:** 1.11
 
-**Last Updated:** 2026-09-06
+**Last Updated**: 2026-09-28
+
+**Upstream Source:** [Standard Repository Policies](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/documentation.md)
 
 ## Purpose
 
-Assign each documentation topic one canonical owner so ConfigKit's documentation
-remains accurate and useful to consumers, maintainers, and implementation agents.
+This policy assigns each documentation topic to one canonical owner. Its goal is
+to keep ConfigKit's documentation accurate, concise, discoverable, and resistant
+to drift for consumers, maintainers, developers, and coding agents.
 
-## Core rules
+## Core Rules
 
-### One canonical owner
+### One Canonical Owner
 
-Each authoritative fact belongs in one owning document or Go declaration's
-reference documentation. Other documents may summarize and link to that owner;
-they must not maintain competing definitions of commands, API contracts, YAML
-semantics, defaults, paths, diagnostics, or compatibility guarantees.
+Each authoritative fact belongs in one document. A non-owning document may give
+a short, stable summary for orientation, but it must link to the canonical owner
+for volatile details.
 
-### Policies, current behavior, and future work
+Volatile details include commands, flags, configuration fields and defaults,
+module keys, schemas, file names, paths, status codes, retry behavior, and
+runtime guarantees. If readers could reasonably treat a statement as a
+contract, maintain it only in the owning document.
 
-- Policies state currently binding contributor rules, including constraints on
-  future implementation. They do not imply that features already exist.
-- Current API/configuration contracts, consumer guidance, and component
-  documentation describe implemented behavior only, including partial boundaries.
-- ADRs record accepted decisions and rationale. Acceptance is not evidence of
-  implementation; execution status belongs in roadmaps.
-- Roadmaps own unimplemented targets, deferred work, and execution status.
+### Current And Future Behavior
 
-The initial target and implementation plan have separate owners. Do not put
-staged steps or progress in `docs/roadmap/initial.md`. `docs/roadmap/implementation.md` owns those details.
-As behavior lands, move its normative definition into the current contract and
-replace the roadmap definition with a link. Retire completed roadmap material
-as part of release preparation; ADRs preserve significant decision history.
+Outside `docs/roadmap/`, documentation describes implemented behavior only.
+Partial features may be described only to their implemented boundary.
 
-### Audience and examples
+Architectural constraints may govern future changes. Describe current structure
+from implemented behavior.
 
-Consumer documentation explains how to use the library and what consumers own.
-Internal documents explain mechanisms and dependencies. Keep implementation
-mechanics out of consumer guidance unless they affect a meaningful choice.
+ADRs may record an accepted architectural decision before implementation. The
+roadmap owns implementation status and sequencing until the decision is
+implemented. Current architecture, user, operator, integration, and internal
+documentation are updated when the behavior lands.
 
-Complete copyable artifacts belong in `examples/`; Go API examples may live in
-executable Go example tests beside the relevant package. Prose should use the
-smallest useful excerpt and link to the maintained artifact. Examples must be
-secret-free and checked against implemented behavior. Clearly label illustrative
-future syntax in roadmaps; do not present it as a runnable current example.
+`docs/roadmap/deferred.md` owns deliberate exclusions; task-specific plans
+own execution order and progress. Completed plans retire during release
+preparation.
 
-### Security and privacy
+### Audience And Detail
 
-Do not include real credentials, private keys, environment dumps, sensitive input,
-or private infrastructure details unless intentionally public. Document secret
-handling, not secret values.
+Write for the document's stated audience and include only the detail needed for
+its owned topic. Keep user and operator docs focused on using and operating the
+application. Developer docs should link to user-facing and external contracts
+for their definitions.
 
-## Canonical ownership
+### Examples
 
-| Topic | Owner | Boundary |
-| --- | --- | --- |
-| Product orientation | `README.md` | Current status, purpose, navigation, and a minimal working example once available |
-| Contributor entry point | `docs/development.md` | Reading guide and actual baseline validation commands |
-| Architecture rules | `docs/policy/architecture.md` | Responsibilities, dependency constraints, invariants, and scope boundaries |
-| Documentation rules | `docs/policy/documentation.md` | Ownership and document lifecycle |
-| Testing rules | `docs/policy/testing.md` | Risk-based sufficiency, test boundaries, and maintenance principles |
-| Release rules | `docs/policy/release.md` | Compatibility, integrity, gates, immutability, and exceptions |
-| Release procedure | `docs/release.md`, when operational | Exact maintainer commands, prerequisites, supported targets, and verification |
-| Exported Go API | Go documentation beside declarations | Symbol contracts, errors, ownership, and lifecycle API behavior |
-| YAML and resolution semantics | `docs/config.md`, as behavior lands | Syntax, composition, precedence, conversion, secret references/bootstrap, and explanation semantics; Go reference docs link here for shared rules |
-| Consumer walkthroughs | `docs/consumers/`, when useful | Task-oriented usage and consumer responsibilities, not duplicate API reference |
-| Component inventory | `docs/internal/overview.md` | Implemented components and links to their owners |
-| Component mechanics | Other `docs/internal/` files, when needed | Detailed implementation behavior and change recipes |
-| Architectural decisions | `docs/adr/` | Context, decisions, alternatives, consequences, and supersession history |
-| Initial target | `docs/roadmap/initial.md` | Unimplemented end-state and deferred feature scope |
-| Implementation plan | `docs/roadmap/implementation.md` | Stages, dependencies, acceptance gates, and progress |
-| Release readiness gaps | `docs/roadmap/release-readiness.md` | Outstanding release prerequisites and closure evidence |
-| Historical release notes | `docs/releases/` | Version-specific historical summaries required by release policy |
-| Complete examples | `examples/` and executable Go examples | Maintained artifacts; prose links instead of duplicating full examples |
+Complete copyable files belong in `examples/`. Documentation may use the
+smallest illustrative snippet needed to explain its owned topic, but should link
+to maintained examples for complete copyable files.
 
-A listed future owner is not a requirement to create an empty file now. Create
-API, consumer, example, and component documents when the corresponding behavior
-exists and there is useful content to own. Link only to existing files; use plain
-code paths for planned files. Release prerequisites have the explicit temporary
-exception recorded in the release policy.
+Executable Go API examples may live beside the relevant package.
 
-ConfigKit has no owned HTTP service, application CLI, or runtime operations
-interface. Do not create those reference documents for consuming applications.
+Examples must be valid, secret-free, and tested where practical. Commands and
+configuration used in documentation should match the application.
 
-## Boundary rules
+### Security And Privacy
 
-Architecture owns governing constraints; ADRs explain why; contracts describe
-implemented semantics; internal documentation explains how. A roadmap may link
-to all of them but must not become a second current reference.
+Documentation and examples must not contain real credentials, private keys,
+private environment dumps, sensitive source material, or private infrastructure
+details unless intentionally public. Document secret-handling mechanisms, not
+secret values.
 
-Release policy owns guarantees; the release procedure owns commands. A release
-note cannot redefine a compatibility contract or replace a current-documentation
-update. The note at an immutable tag is that release's historical record.
+## Canonical Ownership
 
-This policy owns what documentation may disclose. Architecture owns security
-invariants. Current configuration and Go API contracts own secret-classification
-and rendering behavior when implemented; internal docs own their mechanisms.
+| Topic | Canonical owner | Owned content | Content owned elsewhere |
+| --- | --- | --- | --- |
+| Product orientation and minimal example | `README.md` | Purpose, current status, shortest useful Go example, and navigation, including licensing and attribution. | Full Go API and configuration contracts, release procedure, and implementation detail. |
+| Contributor entry point | `docs/development.md` | Task-oriented reading guide, contributor orientation, baseline validation commands, and canonical links. | Package inventory, architecture rules, subsystem behavior, detailed change recipes. |
+| Application architecture policy | `docs/policy/architecture.md` | System shape, normative ownership, dependency direction, boundaries, invariants, safety properties, and non-goals. | Concrete package inventory, implementation mechanics, contributor procedures, decision history, future work. |
+| Policy-set provenance and upstream navigation | `docs/policy/meta.md` | Policy-set origin, local authority, adoption baselines, and upstream adoption and update links. | Task-specific reading triggers, detailed adoption procedures, and formal attribution notices. |
+| Agent policy | `docs/policy/agents.md` | Proportionate, idiomatic implementation; rules against inventing requirements, restrictions, guarantees, or policy. | Application contracts, architecture, testing policy, and contributor procedures. |
+| Documentation policy | `docs/policy/documentation.md` | Documentation ownership, audience boundaries, maintenance rules, and ADR/document lifecycle. | Application architecture or product behavior. |
+| Testing policy | `docs/policy/testing.md` | Test philosophy, risk sufficiency, boundaries, doubles, coverage, regressions, and test maintenance. | Subsystem behavior, application contracts, subsystem-specific test inventories, and implementation plans. |
+| Release policy | `docs/policy/release.md` | Versioning, compatibility, release integrity and immutability, release documentation, proportionate gates, publication controls, completion, and required versus optional checks. | Repository-specific commands, product installation guidance, CLI version semantics, historical release summaries, and CI implementation detail. |
+| Open source licensing and attribution policy | `docs/policy/oss.md` | License defaults and author choices, COPYRIGHT and attribution formats, license/notice links, discoverability, maintenance, and concrete exceptions. | Component entries, license texts, release commands, and dependency security review. |
+| Project copyright and license grant | `COPYRIGHT` | Project identity, copyright holders and years, SPDX expression, code grant, separately licensed document scope, warranty disclaimer, and third-party statement. | Complete license texts and upstream component attribution. |
+| Project license texts | `LICENSE` | Complete project and incorporated companion license texts, with required project-specific fields. | General licensing policy and upstream component attribution. |
+| Upstream component attribution | `docs/oss/attribution.md` | House Format entries for dependencies and adapted documents: identity, material scope, copyright, license, notices, and source links. | General policy, exception reasoning, and complete standard license texts. |
+| Standard license texts | `docs/oss/licenses/` | Complete, verbatim standard license texts shared by applicable entries, including copied documentation. | Project-specific upstream notices, attribution prose, and policy interpretation. |
+| Repository-specific release procedure | `docs/release.md` | Maintainer prerequisites, candidate preparation, validation and publication commands and automated guards, asynchronous deliverables, delivery status, optional consumer verification, and recovery. | General release requirements, product installation guidance, historical release summaries, and current compatibility contracts. |
+| Exported Go API | Go documentation beside declarations | Symbol contracts, errors, ownership, and lifecycle behavior. | Shared YAML semantics and complete examples. |
+| Configuration contract | `docs/config.md` | YAML syntax, composition, precedence, schema, defaults, resolution, validation, secrets, and explanation semantics. | Go symbol contracts, complete examples, and implementation detail. |
+| Consumer guidance for the public Go API | `docs/consumers/` | Task-oriented public Go API usage, minimal examples, and consumer responsibilities. | Go symbol contracts, configuration semantics, and internal implementation detail. |
+| Inventory of implemented internal packages | `docs/internal/overview.md` | Implemented packages and components, responsibilities, and links to focused internal docs. | Normative architecture, contributor reading policy, external contracts. |
+| Behavior and architecture of internal packages | Other files under `docs/internal/` | Implementation flow, collaborators, state transitions, package-local guarantees and failures, and relevant tests. | Global architecture invariants, configuration definitions and defaults, external schemas, operator procedures. |
+| Architectural decision records | `docs/adr/` | Significant decisions, context, alternatives, rationale, consequences, and supersession history. | Current behavior reference, implementation status, task sequencing. |
+| Deferred scope | `docs/roadmap/deferred.md` | Deliberate exclusions and conditions for reconsideration. | Task execution and current behavior. |
+| Future implementation plans | Task-specific files under `docs/roadmap/` | Unfinished work, sequencing, acceptance, and progress; completed plans retire during release preparation. | Implemented behavior and ADR rationale. |
+| Release-note history | `docs/releases/` | One checked-in summary per source release under the procedure; the note at its immutable tag is the release record. | Current commands, behavior, contracts, and compatibility definitions. |
+| Complete examples | `examples/` and executable Go examples | Maintained copyable artifacts and Go API examples. | Configuration reference, symbol contracts, and prose explanation. |
 
-## Architectural decision records
+Create supporting documents for existing interfaces and responsibilities when
+substantive content is available.
 
-Use sequential filenames, such as `0001-separate-composition-and-overlay.md`,
-and the lightweight Nygard structure: title, status, date, context, decision,
-alternatives considered, and consequences.
+Do not create empty owners.
 
-Accepted decision content is immutable. A changed decision requires a new ADR
-and a superseded status/link in the old one. Navigation links may be repaired
-when specification ownership moves without rewriting historical rationale.
-Rejected architectural alternatives belong in ADRs; deferred or rejected product
-features belong in roadmaps. Do not create an ADR for every routine choice.
+## Boundary Rules
 
-## Maintenance and verification
+### Orientation
 
-Update the owning current documentation in the same change that implements or
-changes behavior. When ownership moves, remove the old definition and preserve
-useful navigation links.
+Link among orientation, architecture, and internal documents; maintain each
+package or behavior description in its canonical owner.
+
+### Go API And Configuration
+
+Go declaration documentation owns exported symbol behavior. The configuration
+contract owns shared YAML and resolution semantics. Consumer guidance explains
+tasks and links to those contracts.
+
+### Releases
+
+The release policy defines requirements and invariants that every release must
+satisfy. The repository-specific release procedure defines the commands and
+workflow maintainers use to satisfy that policy. Release notes record history
+at immutable tags. Maintain current behavior in its canonical documentation,
+update it with the corresponding behavior changes, and keep release procedures
+consistent with adopted policy.
+
+### Project Licensing And Upstream Attribution
+
+README and release documents link to the canonical licensing and attribution
+materials under the [OSS policy](oss.md). The release procedure owns URL
+construction and publication mechanics.
+
+### Contracts And Implementation
+
+Go API and configuration documents define externally observable behavior.
+Internal documents explain implementation and link to the owning contract.
+
+### Security Topics
+
+This policy owns what documentation and examples may contain. Architecture owns
+application security invariants. The configuration and public API contracts own
+secret-classification, bootstrap, and rendering behavior. Internal docs own
+implementation mechanisms only.
+
+## Architecture Decision Records
+
+Use sequentially numbered ADR filenames such as
+`0001-record-architecture-decisions.md`. Follow the lightweight Nygard format:
+
+1. title;
+2. status;
+3. date;
+4. context;
+5. decision;
+6. alternatives considered;
+7. consequences.
+
+Treat the decision content of an accepted ADR as immutable. When a decision
+changes, create a new ADR and update the earlier ADR's status to superseded.
+Rejected architectural alternatives belong in the ADR; rejected product ideas
+belong in the roadmap. Routine choices need no ADR.
+
+## Maintenance
+
+When behavior changes, update its canonical owner in the same change. If
+ownership moves, remove the old definition and replace it with a link where
+navigation remains useful.
 
 Before completing documentation work:
 
-- verify claims against the implementation or clearly identify future design;
-- check changed local links, paths, fragments, examples, and commands;
-- preserve the distinction between policy, decisions, target behavior, and status;
-- check canonical ownership and remove stale or duplicate definitions;
-- inspect formatting and whitespace;
-- ensure no sensitive data was introduced.
+- verify affected behavior and examples;
+- check commands, flags, fields, defaults, schemas, and paths against their
+  implementation;
+- keep unimplemented behavior in the roadmap, subject to the ADR exception;
+- remove stale references and validate links;
+- confirm that non-owning documents summarize and link rather than redefine;
+- confirm that no secrets or sensitive private data were added.

docs/policy/meta.md

@@ -0,0 +1,27 @@
+# Policy Set Provenance
+
+**Base Policy Version:** 1.0
+
+**Last Updated**: 2026-09-28
+
+**Upstream Source:** [Standard Repository Policies](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/meta.md)
+
+## Origin And Local Authority
+
+This repository's policy set is adapted from
+[Standard Repository Policies](https://gitea.maximumdirect.net/eric/policy).
+The adopted local policies govern work in this repository. Upstream revisions
+become local policy through deliberate adoption, preserving local decisions.
+Each policy's `Upstream Source` identifies its adopted baseline.
+
+## Adoption And Updates
+
+For policy adoption, upstream revision reviews, and updates, consult the
+[upstream adoption and update guide](https://gitea.maximumdirect.net/eric/policy/src/branch/main/docs/adoption.md).
+That guide and the reference example collection are maintained upstream and
+accessed through links. Keep discovery links pointed at the current upstream
+project and guide; keep adopted-source and example links pinned to commits.
+
+The local [developer guide](../development.md) routes tasks to applicable
+policies. Formal credit and licensing notices for the copied policy material
+belong in the local [attribution document](../oss/attribution.md).

docs/policy/oss.md

@@ -0,0 +1,217 @@
+# Open Source Licensing And Attribution Policy
+
+**Base Policy Version:** 1.8
+
+**Last Updated**: 2026-09-28
+
+**Upstream Source:** [Standard Repository Policies](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/oss.md)
+
+## ConfigKit Applicability
+
+ConfigKit's selected grant is LGPL-3.0-or-later, recorded in
+[COPYRIGHT](../../COPYRIGHT), with the complete LGPLv3 and incorporated GPLv3
+texts in [LICENSE](../../LICENSE). The [release procedure](../release.md)
+owns source-only Go module publication through Gitea. No separate hosted release
+object or license asset is required for this channel.
+
+## Purpose And Scope
+
+This policy defines project licensing conventions and a repeatable House Format
+for upstream attribution and license notices. It covers the project's own code
+and upstream components incorporated into or distributed with the application
+or library, including relevant transitive dependencies and copied code,
+documentation, or assets.
+Determine treatment from the component's terms and actual use.
+
+Consulting development guidance or using tooling alone does not require an
+attribution entry. Copying or adapting documentation for inclusion in the
+repository is different: preserve its applicable attribution and license terms.
+A material's role as development guidance does not exempt copied documents.
+Apply any express permissions for attribution-free reuse of example formatting.
+
+The baseline is a publicly available source repository with releases published
+alongside it. The format is independent of language, forge, and build system.
+It does not require attribution for every development tool, establish license
+compatibility, or resolve every obligation arising from use or distribution.
+
+## Canonical Locations
+
+The [documentation policy](documentation.md) assigns ownership:
+
+- `COPYRIGHT`: project name, copyright statements, SPDX expression, grant,
+  warranty disclaimer, and third-party statement.
+- `LICENSE` contains the complete, unmodified project license text, including
+  incorporated companion text. Dependency attribution does not relicense the project.
+- `docs/oss/attribution.md`: canonical component entries.
+- `docs/oss/licenses/`: complete, verbatim standard and applicable companion texts.
+
+Use recognizable license filenames, such as `Apache-2.0.txt` or `LGPL-3.0.txt`.
+A shared standard text may serve multiple entries. Keep explanations outside
+license texts and preserve distinct versions and exceptions.
+
+## Upstream Reference Examples
+
+Use the commit-pinned upstream examples to create actual project notices.
+Retain their links and keep the example collection upstream; keep applicable
+license texts locally as specified above. The
+[standard license-text collection](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/oss/licenses/README.md)
+identifies the available reference texts.
+
+## Project Licensing
+
+Unless the author specifies otherwise, use **GPL version 3 or later**
+(`GPL-3.0-or-later`) for applications and **LGPL version 3 or later**
+(`LGPL-3.0-or-later`) for libraries. An author's explicit choice takes precedence:
+for example, a one-off script may use MIT. Such a choice requires no exception
+rationale, additional approval, or compensating controls under this policy.
+
+These defaults guide new license selection. Adopting this policy does not
+relicense existing code or override third-party terms. Preserve an existing
+license unless the author deliberately changes it. For mixed-purpose projects,
+follow the author's selected scope rather than inferring different licenses for
+individual packages.
+
+Use the upstream [application COPYRIGHT example](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/examples/licensing/application/COPYRIGHT)
+or [library COPYRIGHT example](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/examples/licensing/library/COPYRIGHT)
+to create the project’s root `COPYRIGHT` file.
+Use verified project names, contribution years, and copyright holders.
+For another selected license, adapt the grant, SPDX expression, disclaimer, and
+text references together to reflect the author's selected grant.
+
+For GPLv3 projects, copy the complete GPLv3 text into `LICENSE`. For LGPLv3
+projects, place the complete LGPLv3 text followed by the complete GPLv3 text in
+`LICENSE`; the LGPL incorporates the GPL terms. Keep the texts unmodified and
+place project-specific statements in `COPYRIGHT`. For the default grants, the
+grant and SPDX expression in `COPYRIGHT` must expressly identify `or-later`;
+follow the author’s choice if a different grant is selected.
+
+For other licenses, provide their complete text and any required project-specific
+fields; the standard reference collection remains unchanged. Keep `COPYRIGHT`,
+`LICENSE`, SPDX expressions, and README descriptions consistent with the actual
+grant. This convention introduces no blanket requirement for per-file headers;
+preserve notices or add them where the applicable terms require them.
+
+Identify separately licensed documentation or assets in the project grant, with
+links to their attribution and license information. An application's default
+code license does not override the terms of incorporated documentation.
+
+## Upstream Attribution House Format
+
+Begin `docs/oss/attribution.md` with `# Open Source Attribution Notices`,
+followed directly by component entries. These comprise the complete document.
+
+Each entry presents these five fields in order, with blank lines between them:
+
+1. **Project name** as a level-two heading. An optional identification paragraph
+   may follow, such as `Selected module: MODULE at VERSION.` with the module and
+   version in backticks. For copied documentation, a concise `Material:` sentence
+   may identify the affected files and whether they were adapted or copied
+   without modification. A factual qualifier such as `(transitive dependency)`
+   is permitted. Limit optional identification prose to factual component and
+   material scope.
+2. **Upstream copyright statement or statements**, preserving their wording.
+   Put multiple statements in separate paragraphs. Include this field when the
+   selected upstream source supplies an applicable statement; otherwise, omit it.
+3. **SPDX license identifier or expression**, when applicable, using
+   `SPDX-License-Identifier: EXPRESSION`.
+4. **License and notice links**, beginning `License and notices:`, separated
+   by ` | `, and ending with a period. Label local standard texts by license
+   name, such as `MIT` or `Apache 2.0`. Label upstream files by their actual
+   filenames, such as `COPYRIGHT`, `LICENSE`, `NOTICE`, or `PATENTS`.
+5. **Source repository link**, rendered exactly as `[Source](COMMIT_URL).`.
+
+Use the upstream [attribution example](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/examples/licensing/attribution.md)
+to create the project’s `docs/oss/attribution.md`.
+The example illustrates omitted fields and multiple copyrights and licenses.
+Replace the uppercase placeholders and illustrative URLs with actual component
+information. Local license links are relative to the destination
+`docs/oss/attribution.md`; copy the applicable texts into its `licenses/`
+directory. Do not copy example entries for components the project does not use.
+
+These are five fields, not a line limit. Omit the SPDX field when no applicable
+identifier exists; identify nonstandard terms through the linked text. Preserve
+licensing alternatives and exceptions, and record a selected option when
+relevant through the factual license identification. Do not invent an identifier
+or silently resolve an unsettled licensing choice.
+
+Keep entries factual. Do not add agent-authored explanations of license
+expressions, file-level license scope, research performed, retained source
+notices, or compliance conclusions. Avoid filler such as "none is invented
+here" and embellished link labels such as "upstream LICENSE", "additional
+patent grant", or "at the imported commit". Preserve actual required upstream
+content; this rule excludes editorial additions, not required notices. Policy
+interpretation and exception reasoning belong in the adopted OSS policy or an
+appropriate decision record, not the attribution document.
+
+## License Texts And Upstream Links
+
+Link standard license texts to their local copies. Link project-specific
+notices to their upstream copies. Every upstream repository or notice link must
+identify the exact commit corresponding to the
+imported version, including the selected source revision for copied material.
+
+Classify material according to its contents. An upstream `LICENSE`,
+`COPYING`, or similar file may contain project-specific notices or exceptions
+in addition to standard wording. Link both the local standard text and the
+commit-specific upstream file when needed. Make companion license texts directly
+reachable from the entry.
+
+For project-specific license and attribution material, this policy accepts
+direct links to the applicable upstream texts as satisfying reproduction,
+inclusion, or copy requirements. This is the adopted house interpretation.
+Agents must apply it without adding local-copy requirements or seeking repeated
+approval solely because a license uses those terms.
+
+This interpretation concerns notice reproduction. Concrete obligations such as
+marking modified files or supplying corresponding source receive their own
+applicable treatment. Preserve required notices already present in incorporated
+source files; the central attribution entry does not authorize stripping them.
+
+## Discoverability
+
+End the project's README with two friendly statements linking to its actual
+grant in `COPYRIGHT` and the attribution document. ConfigKit's
+[README](../../README.md) contains the two required statements: one linking to
+the project grant and one linking to attribution.
+
+Each new checked-in release document and its hosted download page must end
+with links whose visible text is `COPYRIGHT | LICENSE | ATTRIBUTION`. Use absolute
+URLs to those files at the release's immutable tag or corresponding immutable source
+revision so the links work in both locations. This release navigation is distinct
+from upstream component links, which must use the imported commit.
+
+Reuse the checked-in release document as the hosted release body where supported.
+The release procedure owns concrete URLs and publication mechanics for delivering
+the links through the selected channel. Do not maintain duplicate notice lists.
+These conventions do not by themselves require separate downloadable license
+assets, source bundles, or a different binary package format.
+
+## Maintenance And Exceptions
+
+Update project licensing statements together when the author changes the grant
+or its scope. Update upstream notices in the change that adds, removes, upgrades,
+copies, or changes the distribution of a relevant component. Check the selected source's license
+and notices rather than assuming they are unchanged. Update affected entries,
+commit links, and texts; retain historical versions through Git.
+
+Check affected statements, faithful standard-text copies, and link destinations
+as part of ordinary change review. For a future release tag, check intended file
+paths against the candidate source; the tag need not resolve remotely before
+publication. Do not add publication-time network checks, CI polling, recurring
+legal sign-offs, mandatory scanners, or a full software bill of materials merely
+to implement this policy.
+
+Use the House Format routinely. Raise an exception only for a concrete obligation
+or unresolved rights question it does not address, including any arising from a
+particular distribution channel. Record the issue and selected treatment in the
+adopted OSS policy or an appropriate decision record. Attribution entries
+contain the resulting factual identification and required material, without
+repeating that reasoning. Resolve the issue before the affected use or
+distribution without reopening settled choices.
+Common ownership of projects is neither required nor a blanket exception.
+
+Apply the formatting convention prospectively. Do not rewrite published tags,
+notes, binaries, or checksums to retrofit it. Address actual omissions deliberately
+under the applicable terms and the [release correction policy](release.md#immutability-and-correction).
+Ordinary attribution maintenance and release links are preparation work, not new
+release approval gates.

docs/policy/release.md

@@ -1,73 +1,97 @@
 # Release Policy
 
-**Base Policy Version:** 0.1.0
+**Base Policy Version:** 1.4
 
-**Last Updated:** 2026-09-06
+**Last Updated**: 2026-09-28
+
+**Upstream Source:** [Standard Repository Policies](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/release.md)
 
 ## Purpose
 
-This policy defines the minimum requirements for selecting, validating,
-publishing, verifying, and correcting releases. Its goal is to make every
-release intentional, reproducible from an exact source revision, documented
-for consumers, and safe from retrospective replacement.
+This policy defines a proportionate workflow for validating and publishing an
+intended source revision under a fresh version. Releases should require little
+routine intervention, avoid repeated work, and preserve published contents.
 
-The repository-specific commands that implement these requirements belong in
-`docs/release.md`. Historical release summaries belong in `docs/releases/`.
-Neither document may weaken this policy.
+The repository-specific commands belong in `docs/release.md`. Historical release
+summaries belong in `docs/releases/`. The procedure must agree with the adopted
+policy and link to it rather than introduce additional release requirements.
 
-## ConfigKit applicability
+## ConfigKit Applicability
 
-ConfigKit adopts a source-only Go module release model. The source tag and
-version-matched release note are the declared deliverables. Standalone binaries,
-container images, and separate binary/package-registry publication are not
-required. This does not waive source compilation, module hygiene, testing, or
-consumer-facing module retrieval and build verification.
+ConfigKit publishes a source-only Go module. Its declared deliverables are the
+immutable annotated source tag and version-matched checked-in release note.
+Standalone binaries, container images, hosted release objects, and separate
+registry publication are not required. Additional channels require a deliberate
+update to the policy and procedure.
 
-The release procedure must define the module path, authoritative remote,
-supported Go versions and operating-system/architecture targets, prerequisite
-dependency acquisition, and the exact verification commands once established.
-The default tests themselves remain deterministic and offline. Additional
-publication channels require documented deliverables and verification before use.
-
-The Go API, documented YAML/resolution semantics, and structured diagnostic
-contracts all participate in compatibility review. A signature-preserving change
+The Go API, documented YAML and resolution semantics, and structured diagnostic
+contracts participate in compatibility review. A signature-preserving change
 can still break consumers. Human diagnostic wording is stable only where a
-contract expressly promises it. Minimum Go version and platform support changes
-also require an explicit compatibility assessment.
+contract expressly promises it. Minimum Go version and platform support
+changes also require an explicit compatibility assessment.
 
-## Release Model
+### Platform Support
 
-A release consists of:
+Linux is the release-validated platform. macOS has best-effort support: keeping
+it working remains desirable, but neither native macOS validation nor Darwin
+cross-builds are release gates. Missing macOS evidence or a macOS-specific failure
+does not by itself block a release. Voluntary checks and fixes are welcome; there
+is no guarantee that each release has been validated on macOS.
 
-- one exact source commit reachable from the repository's primary branch;
-- one immutable version tag identifying that commit;
-- one version-matched, checked-in release note; and
-- every artifact, image, package, registry entry, or other deliverable the
-  repository declares for that release.
+The [release procedure](../release.md#release-identity-and-support) owns target
+architectures and required Linux checks. Historical release notes and their
+validation records remain unchanged.
 
-The repository's primary branch is `main` unless an adopted policy documents
-an exception. A release candidate must be committed and pushed to that branch
-before its release tag is published.
+## Release Model And Completion
 
-The source tag is the authoritative release identity. Published deliverables
-must be traceable to the tagged source and must agree with its version. A
-repository may publish source only. When it publishes additional deliverables,
-its release procedure must enumerate them and define how each is built,
-identified, published, and verified.
+A source release identifies one exact committed source revision through an
+immutable version tag and a version-matched, checked-in release note. The
+primary release branch is `main` unless the adopted policy specifies otherwise.
+The procedure must name the authoritative publication remote.
 
-Release automation may validate or publish a release only when its exact
-responsibility is documented. Automation must not silently change the source
-candidate, move a published tag, replace a published deliverable, or repair a
-release in place.
+A successful push of the intended tag, with its source commit available on the
+authoritative primary branch, completes the release. The source commit may be
+pushed before the tag or published together with it through an atomic push.
+The procedure must choose and document the supported approach.
+
+ConfigKit uses sequential explicit pushes: first the captured candidate to
+authoritative `main`, then the annotated tag. Its
+[release procedure](../release.md) names `origin` and checks that its fetch and
+push destinations resolve to the authoritative URL.
+
+Release commands must finish at successful publication. They must not wait for
+or poll CI, require successful CI status, inspect downloadable artifacts, or
+check consumer installation or Go module availability as completion gates.
+A failed or ambiguous push requires resolving the authoritative remote state
+before declaring success or retrying; successful pushes do not require a
+separate remote read-back gate.
+
+Remote tag read-back and fresh consumer retrieval are optional and non-gating
+after successful publication. A failed push receives one bounded check of the
+authoritative ref; do not poll or blindly retry.
+
+Repositories may publish source only. Additional binaries, images, packages,
+checksums, or other declared deliverables may be published asynchronously from
+the tagged source. The procedure must identify those deliverables and the
+responsibility of their automation. Published deliverables must be traceable
+to that source and identify the same version.
+
+ConfigKit currently declares no additional deliverables. Its source-tag push
+is the completion point.
 
 ## Versioning And Compatibility
 
 Stable releases use Semantic Versioning in the form `vMAJOR.MINOR.PATCH`, with
-no leading zeroes. Each version must be unused locally and in every configured
-remote or publication channel before publication begins.
+no leading zeroes. Prereleases require an explicit adopted policy defining
+their format and use.
 
-Unless an adopted policy explicitly supports and defines prereleases,
-prerelease versions are not permitted.
+ConfigKit does not support prereleases.
+
+The selected version must be unused locally and on the authoritative remote.
+Do not require queries to every configured remote or publication service.
+A version known to have already been published must not be reused, even if the
+normal guards do not inspect that channel. Adding a distribution channel
+requires a deliberate update to the policy and procedure where needed.
 
 For releases at or after `v1.0.0`:
 
@@ -80,159 +104,173 @@ configuration, data, integration, or compatibility contract when the release
 note explains the impact and required consumer action. A patch release must
 not intentionally break those contracts within its minor line.
 
-A repository with additional compatibility promises must define them in its
-adopted policy or canonical contract documentation. A release note may explain
-a compatibility change, but it must not redefine the current compatibility
-contract.
+Additional compatibility promises and deliberate exceptions belong in the
+adopted policy or canonical contract documentation. Release notes explain
+changes; they do not redefine current compatibility contracts.
 
-## Release Documentation
+## Release Documentation And Preparation
 
-Every release made under this policy must include
-`docs/releases/<version>.md` in the tagged source tree. The filename must use
-the complete version tag, and the document must begin with a title containing
-the product name and that exact version.
+Every new release must include `docs/releases/<version>.md` in the tagged
+source tree. Use the complete version tag as the filename and begin with a
+title containing the product name and that exact version.
 
-Every new release note must contain these sections:
+ConfigKit requires the first line `# ConfigKit <version>`.
 
-```markdown
-# <Product> vMAJOR.MINOR.PATCH
+Include a short summary and any relevant compatibility impact or upgrade
+instructions. Choose sections suited to the release and keep the note
+proportionate to the change.
 
-This release ...
+Keep exact current contracts in their canonical documents and update affected
+documentation with the behavior change. Link to those documents from the note
+where useful. If annotated tags are used, derive their summary from the
+checked-in note.
 
-## Summary
+ConfigKit uses the complete checked-in note as the annotated tag message.
 
-## Compatibility
+Include the release footer defined by the [OSS policy](oss.md#discoverability)
+in each new release document. The release procedure defines the concrete URLs
+and publication mechanics. Prepare these links with the release note; they do
+not add a network check or approval gate. If a hosted download page is used in
+a future channel, preserve the footer there.
 
-## Upgrade
+Handle version selection, release-note content, and retirement of completed
+roadmaps during preparation. Preserve planned and deferred work and repair
+affected links when retiring roadmaps. Reuse ordinary change review for
+unintended files, credentials, and private data. Scope release-content review
+to the tagged source.
 
-## Changes
-```
+## Candidate Validation
 
-Use an explicit statement such as "No action required" when a section has no
-substantive content.
+Provide one publication command that validates the final committed candidate,
+checks publication state, and publishes the intended refs. A validation-only
+mode or command may be provided for diagnosis, but must not be a required step
+before publication repeats the same checks.
 
-Release notes are immutable historical summaries. They should link to current
-canonical documentation for exact behavior. Every affected canonical document
-must be updated in the same candidate; a release note must not substitute for
-current documentation or defer required documentation changes.
+ConfigKit uses `./scripts/release.sh vMAJOR.MINOR.PATCH`. The separate
+`scripts/release-check.sh` remains an optional diagnostic command; the
+publication command invokes it once and does not use a persistent candidate
+record.
 
-## Candidate Preparation And Validation
+Run the complete deterministic, offline default test suite once for the final
+candidate, following the [testing policy](testing.md). For repositories that
+publish builds, verify the required build targets. Select those targets for
+the application's actual support commitments; native testing on each platform
+and access to particular hardware are not default release prerequisites.
 
-Each repository must provide one documented release-check command or script
-that exercises the complete set of automated source-candidate gates. The
-repository-specific procedure must state all additional manual gates.
+ConfigKit's one maintained Go 1.25 baseline runs the full suite with the race
+detector and test-time vet disabled. This protects library behavior, ownership,
+and concurrent use; the suite already includes examples, consumer fixtures,
+documentation links, and package boundaries. One full vet pass adds static
+checks beyond the test-time subset. CGO-disabled Linux amd64 and arm64 builds
+cover supported configurations distinct from native race compilation. macOS
+and newer-toolchain checks are optional.
 
-The required gates are:
+Additional gates must address a concrete risk that the existing checks do not
+adequately cover. Do not automatically require linting, race testing, module
+hygiene audits, documentation audits, credential scans, example validation, or
+expanded platform matrices solely because they are possible. Retain such
+checks when their distinct protection justifies their cost. A one-time migration
+check must not silently become a permanent release requirement.
 
-- dependency or module hygiene appropriate to the language and ecosystem;
-- the complete deterministic, offline default test suite;
-- race, concurrency, or equivalent safety checks where the implementation can
-  be meaningfully checked for those risks;
-- static analysis and linting used by the repository;
-- production builds for every supported target that can be built in the
-  release environment;
-- formatting and whitespace checks;
-- validation of maintained examples, configuration, schemas, generated
-  sources, and documentation commands where applicable;
-- review of changed local documentation links;
-- removal of obsolete roadmap documents under `docs/roadmap/` that describe
-  completed work included in the release;
-- review for unintended files, generated output, credentials, private data,
-  and unrelated changes; and
-- any additional security, compatibility, migration, packaging, or platform
-  checks required by the product.
+The selected Go commands use readonly module mode with `GOPROXY=off`; acquire
+the baseline toolchain and dependencies before validation. Formatting and
+whitespace remain ordinary development checks in `scripts/check.sh`.
+Review module tidiness when dependencies change, not as a release gate.
 
-Unavailable tooling or an inapplicable check must be addressed explicitly in
-the adopted policy or release procedure; it must not disappear silently from
-the candidate gates.
+Release tests must not require real credentials, mutable application services,
+paid APIs, provider probes, or inference calls. The procedure may describe dependency
+preparation separately from offline validation.
 
-Run the complete checker while preparing the candidate. Commit the release
-note and all associated code, tests, documentation, and configuration, then
-run the complete checker again against the exact commit intended for release.
-Do not publish a release from uncommitted or unvalidated content.
+Avoid duplicate validation across release phases. Successful checks for the
+same final candidate need not be repeated solely to satisfy another phase;
+any reuse must clearly apply to that exact candidate. Persistent validation
+caches are not required. If the candidate changes, validate the new candidate.
+Cheap publication-state checks may be repeated immediately before pushing
+because local or remote state may have changed during validation.
+
+Automate mechanical guards. Human review gates are strongly disfavored: add one
+only through an explicit project-specific policy decision explaining the
+concrete risk and why ordinary change review or automation is insufficient.
+Do not add routine confirmations for checks the command can perform itself.
+
+Compatibility review, release-note accuracy, completed-roadmap retirement, and
+review for unintended files or credentials remain ordinary preparation. The
+executing agent may perform them without routine human approval or separate
+manual evidence records. Publication itself requires authorization.
 
 ## Publication Guards
 
-Immediately before publication, the maintainer or release automation must
-fetch the current primary branch and tags from the authoritative remote and
-verify all of the following:
+Automate the checks needed to publish the intended source under a fresh version:
 
-- the version has the required format and is not already published;
-- the current branch is the primary release branch;
-- the worktree and index are clean;
-- the current commit is the recorded, validated candidate;
-- the authoritative remote branch points to that same commit;
-- the matching release note exists in that commit and has the required title
-  and sections;
-- all required approvals and automated gates succeeded for that commit; and
-- no local or remote tag already uses the selected version.
+- the version has the adopted format and is unused locally and on the
+  authoritative remote;
+- the worktree and index are clean on the primary release branch;
+- the source being published is the exact candidate that passed validation,
+  including its matching release note;
+- the remote primary branch can be advanced to that candidate without
+  discarding remote history, and is published before the tag; and
+- the tag identifies the validated candidate and only the intended refs are
+  published.
 
-Create the version tag against the guarded commit and verify its target before
-publishing it. Publish only the exact intended ref and deliverables. Broad
-operations such as `git push --tags` are discouraged because they can publish
-unreviewed refs unrelated to the release.
+ConfigKit also checks that `origin` has exactly the authoritative fetch and
+push destination, including configured push URLs. The command checks the
+candidate and unused version again after validation, and checks local state
+before creating the tag. Ignored local files do not block publication.
 
-The repository-specific procedure must make these guards executable or give
-copyable commands for performing them.
+Fetch the authoritative branch and tag state as needed for these checks.
+Do not force branch or tag updates to bypass a failed guard. Publish explicit
+refs rather than all local tags. Do not require CI success, publication-service
+availability checks, or a separate manual confirmation for each guard.
 
 ## Immutability And Correction
 
-Published version tags and published deliverables are immutable. Do not move,
-overwrite, recreate, or delete a published tag. Do not replace an artifact,
-image, package, checksum, signature, provenance statement, or release note
-under an already published version.
+Published version tags and published contents are immutable. Do not move,
+overwrite, recreate, or delete a published tag, or replace a published artifact,
+checksum, signature, provenance statement, or release note under that version.
+The checked-in note at the immutable tag is that release's historical record.
 
-If validation fails before publication, correct the candidate, rerun the
-complete gates, and repeat the publication guards. An unpublished local tag
-may be removed after confirming that it was never published or used by a
-release channel.
+If validation fails before publication, correct and commit the candidate and
+rerun the publication command. If a push fails or its outcome is ambiguous,
+inspect the authoritative remote before retrying. Remove an unpublished local
+tag only after confirming it was never published or used by a release channel.
+An unavailable remote leaves publication status unknown; do not overwrite a tag
+to resolve uncertainty.
 
-If publication or post-publication verification reveals a defect, leave the
-published release intact. Correct the defect on the primary branch, choose a
-new patch version or other semantically appropriate new version, write a new
-matching release note, and perform the complete release procedure again.
+Transient network, authentication, CI, or consumer-availability failures do not
+by themselves require a new version.
 
-A distribution channel's supported yank, deprecation, or advisory mechanism
-may warn consumers away from a defective release, but it must not replace that
-release's contents or reuse its version.
+A defect requiring changes to published source or contents requires a corrected
+commit, a new semantically appropriate version, a matching release note, and
+the release procedure again. Leave the original release intact. A channel's
+yank, deprecation, or advisory mechanism may warn consumers away from a defective
+release without replacing its contents or reusing its version.
 
 ## Repository Release Procedure
 
-Every adopting repository must maintain `docs/release.md` as the canonical
-maintainer runbook for implementing this policy. It must define, in execution
-order:
+Maintain `docs/release.md` as a short, executable maintainer runbook. It must
+identify prerequisites, the primary branch and authoritative remote, version
+and note preparation, one publication command with local checks and guards,
+source-only deliverables, the successful-tag-push completion point, and
+partial or unknown-state recovery.
 
-1. maintainer prerequisites and required access;
-2. version selection and compatibility review;
-3. release-note creation;
-4. candidate preparation and the complete validation command;
-5. candidate commit, push, and exact commit recording;
-6. publication guards;
-7. exact tag and deliverable publication commands;
-8. authoritative remote and consumer-facing verification; and
-9. failure handling and correction.
-
-The procedure should use copyable, fail-fast commands where practical. It must
-name the primary branch, authoritative remote, tag form, published
-deliverables, supported build targets, release automation responsibilities,
-and consumer verification path. It must link to this policy instead of
-restating or redefining its requirements.
+Use copyable commands where practical. Keep optional diagnostics and consumer
+verification clearly optional. The procedure must not turn preparation work,
+ordinary change review, or post-publication investigation into additional
+release gates.
 
 ## Policy Exceptions
 
-### Temporary bootstrap deferral
+The following historical exceptions do not change the current release workflow.
 
-The release procedure (`docs/release.md`) and complete release-check command are
-not yet present because ConfigKit has no Go module or implementation to validate.
-Their creation is temporarily deferred during initial development. This exception
-permits implementation work; it does not permit publishing a release without
-any gate required above.
+For v0.1.1 only, the maintainer approved renaming the reserved `_configkit` key to
+`configkit` as an error-correcting point release because there are no current
+consumers. This intentionally changes the v0.1.0 configuration contract without a
+minor-version increment. The release note must explain the renamed directive,
+the lack of a legacy alias, and the newly reserved application key. This exception
+does not apply to subsequent releases or waive any validation or publication gate.
 
-Compensating controls: no release may be published until the
-[release-readiness gaps](../roadmap/release-readiness.md) are closed, the runbook
-and checker exist, and the exact candidate passes all applicable gates. The
-maintainer preparing the first release owns closure. Remove this temporary
-exception when readiness is verified. Any other exception requires a documented repository constraint, rationale,
-compensating controls, scope, and closure condition here; none is currently
-adopted. Do not silently weaken the base integrity, validation, documentation,
-verification, or immutability guarantees.
+For v0.2.0 only, the maintainer accepted the successful native macOS check at
+`244104f` for the final candidate, provided subsequent changes are documentation
+only. The final candidate still requires the complete Linux release checker.
+This exception waives only repeating the macOS check after those documentation
+changes; it does not waive other publication or verification gates.

docs/policy/testing.md

@@ -1,14 +1,16 @@
 # Testing Policy
 
-**Base Policy Version:** 1.0
+**Base Policy Version:** 1.3
 
-**Last Updated:** 2026-09-06
+**Last Updated**: 2026-09-28
+
+**Upstream Source:** [Standard Repository Policies](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/testing.md)
 
 ## Purpose
 
 Our tests exist to make **incorrect changes expensive and correct changes cheap**.
 
-We do not optimize for test count, line coverage, exhaustive isolation, or the fewest possible tests. We optimize for sufficient confidence in important behavior while imposing as little unnecessary friction as possible on future development.
+We optimize for sufficient confidence in important behavior while minimizing friction on future development.
 
 ## ConfigKit-specific priorities
 
@@ -39,37 +41,24 @@ boundaries. No credential bytes may appear in inspection or failure fixtures'
 expected output; use disposable canaries to prove non-disclosure.
 
 Baseline commands belong in the [development guide](../development.md). Release
-gates belong in the [release policy](release.md) and its eventual runbook. This
+gates belong in the [release policy](release.md) and [maintainer runbook](../release.md). This
 policy does not imply that those tools or tests already exist.
 
 ## Every test has a cost
 
-Testing is not an unqualified good. Every test imposes both an immediate cost and a continuing lifetime cost.
-
-A test must be:
-
-- written and reviewed;
-- understood by future maintainers and coding agents;
-- executed in local and CI workflows;
-- diagnosed when it fails;
-- updated when legitimate behavior changes;
-- maintained as fixtures, APIs, and dependencies evolve; and
-- removed or rewritten when it becomes redundant, brittle, misleading, or obsolete.
-
-Tests also create cognitive and architectural friction. They can constrain refactoring, duplicate policy, slow feedback loops, add noise to failures, and cause harmless implementation changes to require unrelated edits across the suite.
+Every test has an immediate and continuing cost: writing, review, execution,
+diagnosis, fixture maintenance, and updates when legitimate behavior changes.
+Tests can also constrain refactoring, duplicate policy, and add failure noise.
 
 A test is warranted only when the confidence it provides justifies these costs.
-
-Apply this cost-benefit analysis at two levels:
+Evaluate that tradeoff at two levels:
 
 1. **Per test:** What realistic defect does this test detect, how consequential would that defect be, and is that protection worth the test's lifetime cost?
 2. **Across the suite:** Does this collection provide materially more confidence than a smaller, simpler suite would?
 
-The preferred test suite is a **lean suite that provides sufficient confidence in the risks that matter, without redundant or low-value tests**. We seek sufficient confidence with the least unnecessary testing friction, not the fewest possible tests.
+Some friction is intentional. Tests should make dangerous changes—such as breaking compatibility, corrupting data, violating security boundaries, or reintroducing subtle bugs—require deliberate review. Keep ordinary internal changes inexpensive.
 
-Some friction is intentional. Tests should make dangerous changes—such as breaking compatibility, corrupting data, violating security boundaries, or reintroducing subtle bugs—require deliberate review. They should not make ordinary internal changes needlessly expensive.
-
-The cost of a test is not a reason to omit testing by default. Do not cite maintenance cost abstractly. When omitting a plausible test, be able to state why the protected failure is low-risk, already covered, obvious, reversible, or cheaper to detect elsewhere. For consequential, subtle, or difficult-to-observe behavior, the presumption should favor testing.
+Evaluate maintenance cost against the specific failure being protected. When omitting a plausible test, be able to state why the protected failure is low-risk, already covered, obvious, reversible, or cheaper to detect elsewhere. For consequential, subtle, or difficult-to-observe behavior, the presumption should favor testing.
 
 ## Default testing style
 
@@ -81,6 +70,8 @@ Use a **classical/Detroit-style** approach:
 - Prefer package-level behavioral tests over tests coupled to private helpers or internal call sequences.
 - Treat exact collaborator interactions as testable behavior only when the interaction itself is a requirement.
 
+Examples of appropriate seams include clocks, randomness, subprocesses, remote APIs, object storage, email, and paid LLM calls.
+
 For ConfigKit, controlled input readers and filesystem failures are useful seams.
 Prefer actual parsing, composition, and decoding over mocks of their call order.
 
@@ -92,7 +83,7 @@ Control clocks, randomness, environment variables, and other process-global or m
 
 ## What deserves tests
 
-Prioritize tests for:
+To the extent the following features are present in the application, prioritize tests for:
 
 1. Public and package-level contracts.
 2. Domain rules and important invariants.
@@ -102,15 +93,27 @@ Prioritize tests for:
 6. Previously observed or plausible regressions.
 7. Representative integration and end-to-end workflows.
 
-A package-level contract is behavior relied upon by another package or major collaborator, not every observable detail of a package implementation.
+A package-level contract comprises behavior relied upon by another package or major collaborator.
 
-For behavior involving **data integrity, destructive operations, compatibility, security, concurrency, idempotency, or recovery**, presume that durable tests are required unless the behavior is already credibly protected at another layer.
+Choose tests for requested behavior and established contracts. Tests must not
+introduce new restrictions, guarantees, or threat scenarios merely because they
+could be asserted. Follow the [agent policy](agents.md) when deciding whether a
+behavior belongs to the contract; current implementation behavior alone is not
+sufficient authority.
+
+For established behavior involving **data integrity, destructive operations,
+compatibility, security, concurrency, idempotency, or recovery**, favor durable
+tests for realistic failures whose consequences warrant protection. Identify
+the failure and the existing contract it would violate. These categories call
+for attention, not an automatic test inventory or permission to strengthen the
+application's guarantees. Account for protection already provided at other layers.
 
 Do not add tests merely because a function, branch, or line exists. Do not add a test when the same meaningful risk is already adequately protected elsewhere.
 
 ## Choose the right test boundary
 
-Test through the narrowest stable boundary that expresses the behavior clearly.
+Choose the narrowest stable boundary that expresses the behavior clearly and
+provides durable confidence with minimal incidental coupling.
 
 This is often the package API, but it may instead be:
 
@@ -118,28 +121,15 @@ This is often the package API, but it may instead be:
 - a package-level operation when several internal collaborators jointly produce the behavior; or
 - a larger integration boundary when correctness emerges from interaction with a real dependency.
 
-Do not force all behavior through oversized end-to-end tests. Do not test every private helper merely because it exists. Choose the boundary that gives durable confidence with the least incidental coupling.
-
 ## Test behavior, not implementation
 
-A test should protect a decision, contract, or invariant—not memorialize the current implementation.
+A test should protect a selected decision, contract, or invariant.
 
-Before adding or retaining a test, ask:
+A test is suspect when it primarily detects changes to private constants or
+helpers, equivalent operation ordering, incidental formatting, equivalent
+algorithms, or internal structure that preserves behavior.
 
-> What realistic defect would this test catch?
-
-A test is suspect when its main purpose is to detect that someone:
-
-- changed an internal constant;
-- renamed or split a private helper;
-- reordered equivalent internal operations;
-- changed incidental formatting;
-- replaced one correct algorithm with another; or
-- refactored internal object structure without changing behavior.
-
-Refactoring should normally require no test edits unless the refactored structure is itself part of the contract.
-
-A test can be factually correct and still have negative value. Accurately describing current behavior is not enough; the protected behavior must be important enough to justify the future friction.
+Behavioral tests should normally remain stable through internal refactoring that preserves the contract.
 
 ## Expected effects of different changes
 
@@ -156,12 +146,13 @@ A test failing is not the same as a test needing to be edited. Many tests may co
 
 ## Separate mechanism from policy
 
-Configurable thresholds and defaults must not be duplicated throughout the test suite.
+Derive expectations from test-controlled configuration and relationships.
 
-For example, do not encode an internal concurrency limit indirectly:
+For this example, assume the selected contract rejects a request to start more
+processes than a configured limit. Do not encode its production default indirectly:
 
 ```go
-// Production policy:
+// Production default:
 const maxConcurrency = 4
 
 // Brittle test:
@@ -179,25 +170,30 @@ require.NoError(t, runner.Start(limit))
 require.ErrorIs(t, runner.Start(limit+1), ErrTooMuchConcurrency)
 ```
 
-The test should prove:
+For this selected contract, the test should prove:
 
 - the configured limit is accepted; and
 - one beyond the configured limit is rejected.
 
+Rejection is not a general requirement for concurrency control. If the selected
+contract queues excess work or limits active workers while accepting larger
+batches, test that behavior instead. Do not add rejection or a configurable
+limit solely to reproduce this example.
+
 The production default should be tested exactly only when its literal value is itself a public, operational, safety, protocol, or compatibility requirement.
 
-Apply the same rule to limits, timeouts, capacities, retry counts, and ranges: test relationships and behavior, not duplicated literals.
+Apply the same rule to limits, timeouts, capacities, retry counts, and ranges: test relationships and behavior.
 
-For concurrency limits, test both kinds of behavior when relevant:
+For established concurrency limits, distinguish these behaviors where the contract requires them:
 
-1. **Configuration enforcement:** invalid or excessive requested values are handled correctly.
+1. **Configuration handling:** values are accepted or rejected according to the selected contract.
 2. **Runtime enforcement:** observed peak concurrency never exceeds the configured limit.
 
-Use a test-controlled limit and measure the behavior relative to that limit. Do not merely assert today's default value.
+Use a test-controlled limit and measure the behavior relative to that limit.
 
-## Avoid semantic duplication across layers
+## Assign each behavior a test owner
 
-Each behavior should have a clear test owner.
+For ConfigKit, assign ownership as follows:
 
 - YAML boundary tests own syntax and policy enforcement.
 - Composition and overlay tests own their operation semantics.
@@ -209,9 +205,7 @@ Each behavior should have a clear test owner.
 
 These are responsibility boundaries, not a required package layout.
 
-Higher-level tests should not repeat every lower-level case. A single intentional policy change should not require unrelated edits across many test files.
-
-Tests that are individually reasonable may still be collectively redundant. Evaluate the marginal value of each additional test in light of the protection already provided by the rest of the suite.
+Give each layer its distinct responsibility and keep expectation updates localized to the contract being changed.
 
 ## Use test doubles deliberately
 
@@ -232,104 +226,77 @@ Mocks are appropriate when the contract includes facts such as:
 - an expensive API is called no more than once; or
 - a security audit event is emitted.
 
-Do not use mocks merely to isolate every object or reproduce the implementation's call graph.
-
 ## Go-specific guidance
 
-Use:
+Select techniques by behavior and risk:
 
 - table-driven tests for meaningful behavioral categories and boundaries;
 - `t.TempDir()` for real filesystem behavior;
-- fuzz tests for parsers, normalization, path handling, and broad input spaces;
+- `httptest.Server` for realistic HTTP interactions;
+- fuzz tests when exploring broad input spaces, such as parsers or path handling, adds useful protection beyond representative cases;
 - golden files only when the complete output is intentionally stable;
 - integration tests where correctness depends on component interaction; and
-- a small number of representative end-to-end tests.
+- a small number of representative end-to-end tests when assembled workflows expose meaningful risks not adequately covered at narrower boundaries.
 
-Avoid exact error-string assertions unless the wording is itself contractual. Prefer `errors.Is`, `errors.As`, typed errors, or structured error fields.
+Prefer `errors.Is`, `errors.As`, typed errors, or structured error fields. Use exact error-wording assertions only when the wording is contractual.
 
 At the public library boundary, prefer diagnostic codes, paths, and source
 locations over complete message snapshots. Assert wording only when contractual.
 
 Golden-file updates must require an explicit local flag. CI must not update golden files automatically, and reviewers must inspect the semantic diff before accepting an update.
 
-Keep tests readable and direct. Test helpers and fixture frameworks must earn their own maintenance cost; do not build elaborate test infrastructure for small or isolated needs.
+Keep tests readable and direct. Size test helpers and fixture frameworks to the maintenance benefit they provide.
 
 ## Coverage
 
-Coverage is a diagnostic, not a target.
+Use coverage to locate untested critical branches and unexpectedly weak packages. Evaluate test quality through meaningful behavioral protection and choose coverage according to risk.
 
-Use it to find untested critical branches and unexpectedly weak packages. Do not write low-value tests solely to increase a percentage, and do not infer test quality from coverage alone.
-
-Dense configuration semantics will often warrant higher coverage than simple input wiring. Uneven coverage is acceptable when it reflects risk.
-
-Increasing coverage is valuable only when the newly covered behavior protects a meaningful risk at an acceptable cost.
+Pure domain logic will often warrant higher coverage than CLI wiring or external adapters. Uneven coverage is acceptable when it reflects risk.
 
 ## Regression tests
 
 A bug fix should normally include a regression test that fails before the fix and passes afterward.
 
-Retain the test when the defect could realistically recur and its consequences justify the ongoing cost. Prefer the narrowest durable test of the violated contract or invariant; do not preserve accidental implementation details from the original bug.
+Retain the test when the defect could realistically recur and its consequences justify the ongoing cost. Prefer the narrowest durable test of the violated contract or invariant.
 
-Not every historical bug requires a permanent test. If the underlying design has made recurrence impossible, the test has become redundant, or a stronger invariant test now subsumes it, remove or consolidate it.
+Remove or consolidate a test when the underlying design has made recurrence impossible, its protection is redundant, or a stronger invariant test subsumes it.
 
 ## Deleting or rewriting tests
 
-Tests are maintained code, not permanent historical artifacts.
-
-Delete or rewrite a test when its maintenance cost exceeds the confidence it provides.
+Delete or rewrite tests when maintenance cost exceeds their continuing
+protective value.
 
 Strong candidates include tests that:
 
 - require updates after harmless internal changes;
-- directly assert private constants without protecting a real contract;
-- duplicate the same policy across several layers;
+- assert incidental private constants or snapshot large amounts of incidental output;
 - verify mock choreography rather than outcomes;
-- snapshot large amounts of incidental output;
-- test trivial private helpers already exercised through stable package behavior;
-- protect risks already covered more effectively elsewhere;
+- duplicate policy across layers, retest trivial helpers covered by package
+  behavior, or protect risks covered more effectively elsewhere;
 - are flaky, misleading, obsolete, or disproportionately expensive to diagnose; or
 - no longer correspond to a plausible failure mode.
 
-Several brittle tests may encode one genuine requirement. Replace them with one durable behavior-level or invariant test rather than preserving all of them.
-
-Deleting a low-value test can improve the quality of the suite by reducing noise, maintenance burden, and friction around legitimate change.
+Several brittle tests may encode one genuine requirement. Consolidate them into one durable behavior-level or invariant test.
 
 ## Reviewing a proposed test
 
-Use the following questions when the value, boundary, or durability of a proposed test is not self-evident. Significant test additions should be reviewable against them, but written answers are not required for every routine test.
+Use the following questions when a proposed test needs closer evaluation. Significant test additions should be reviewable against them; written answers are optional for routine tests.
 
-1. What realistic defect would it catch?
-2. How likely is that defect?
-3. How consequential would it be?
-4. Is the behavior already protected elsewhere?
-5. At which layer should this behavior be owned?
-6. Does the test assert a durable contract or an incidental implementation detail?
-7. Could the implementation be refactored without changing the behavior and without editing this test?
-8. What should cause this test to fail?
-9. What legitimate changes should not cause this test to fail?
-10. What ongoing maintenance, execution, and diagnostic cost will the test impose?
-11. Is there a smaller or more direct test that protects the same risk?
-
-Do not add the test when its expected lifetime cost exceeds its expected protective value.
-
-When deciding not to test plausible behavior, record or be able to explain why the risk is low, already protected, obvious, reversible, or cheaper to detect elsewhere.
+1. Which requested behavior or established contract does it protect, and what realistic defect would violate it?
+2. How likely and consequential is that defect, and is it already protected elsewhere?
+3. What is the narrowest stable boundary that can test it clearly?
+4. Would a correct internal refactor or a change to an incidental default require test edits?
+5. Does its confidence justify its maintenance, execution, and diagnostic cost, or would a smaller test suffice?
 
 ## Definition of sufficient
 
 A test suite is sufficient when:
 
-- important contracts and invariants are protected;
-- meaningful boundaries and failure modes are exercised;
-- realistic and consequential regressions are credibly protected against silent recurrence;
-- behavior involving data integrity, destructive operations, compatibility, security, concurrency, idempotency, and recovery is credibly protected;
-- important external boundaries have realistic integration coverage;
-- representative complete workflows are tested;
-- failures provide useful signal rather than redundant noise;
-- legitimate internal changes usually do not require test edits; and
+- important requested behavior and established contracts are protected against realistic, consequential failures;
+- boundaries and component interactions have coverage where they introduce meaningful risks not protected elsewhere;
+- failures provide useful, distinct signals;
+- tests usually remain stable through legitimate internal changes; and
 - additional tests would mostly repeat existing protection or preserve inconsequential implementation details.
 
-Sufficiency is a risk judgment, not a coverage percentage or test count. Reassess it as the library, its consumers, and the consequences of failure evolve.
-
-The governing rule is:
-
-> Test heavily where failure is consequential, subtle, or difficult to detect after the fact. Test lightly where failure is obvious, reversible, and inexpensive—and retain no test whose lifetime cost exceeds the confidence it provides.
+Reassess sufficiency as the application, its users, and the consequences of
+failure evolve.

docs/release.md

@@ -0,0 +1,199 @@
+# ConfigKit Release Procedure
+
+This is the maintainer runbook for ConfigKit's [release policy](policy/release.md).
+ConfigKit publishes one source-only Go module. The immutable annotated tag and
+matching checked-in release note are the deliverables; there is no binary,
+container image, generated package, or separate registry publication.
+
+## Release identity and support
+
+- Module: `gitea.maximumdirect.net/eric/ConfigKit`
+- Primary branch: `main`
+- Authoritative remote: `origin`, with fetch and push destination
+  `https://gitea.maximumdirect.net/eric/ConfigKit.git`
+- Tags: stable Semantic Versions such as `v0.5.0`; no prereleases
+- Minimum Go line: Go 1.25, validated with one maintained patch
+- Release-gated targets: Linux amd64 and arm64
+- Best-effort targets: macOS amd64 and arm64, under the
+  [platform support policy](policy/release.md#platform-support)
+
+The checker runs one offline race suite, one full vet pass, and CGO-disabled
+builds for both Linux targets. It reports skipped filesystem cases. macOS checks
+and newer-toolchain tests are optional. CI is never a readiness or completion
+gate; do not wait for or poll it.
+
+## 1. Prepare access and tools
+
+Use a clean checkout with Git, Bash 3.2 or newer, a maintained Go 1.25 patch,
+and a native compiler for race tests. Configure private-host access through the
+normal credential manager. Keep credentials and environment dumps outside the
+repository and command transcript.
+
+Verify access without displaying credentials:
+
+```sh
+git remote get-url origin
+git ls-remote origin HEAD
+```
+
+The fetch URL and all configured push destinations must resolve to the
+authoritative URL above. The publication command checks this again. Acquire the
+selected toolchain and dependencies explicitly before offline validation:
+
+```sh
+export CONFIGKIT_BASELINE_TOOLCHAIN=go1.25.14
+GOTOOLCHAIN="$CONFIGKIT_BASELINE_TOOLCHAIN" go version
+GOTOOLCHAIN="$CONFIGKIT_BASELINE_TOOLCHAIN" go mod download
+```
+
+A maintained patch may replace the example pin. No per-release latest-version
+survey is required. Dependencies must be cached; the checker sets `GOPROXY=off`.
+Publication requires user authorization. Standing authorization for local
+commits does not authorize a push or release.
+
+## 2. Select the version and review compatibility
+
+Choose an unused stable version. Compare the candidate with the previous tag.
+Review exported Go signatures and ownership, YAML and scalar semantics,
+precedence, diagnostic codes, minimum Go version, and platform support. A
+signature-preserving change may still affect consumers. Before `v1.0.0`,
+intentional incompatible minor-release changes need a note explaining impact
+and consumer action; patch releases remain compatible within their minor line.
+Review the maintained consumer examples and migration guide.
+
+When dependencies change, review parser behavior and migration impact as part
+of that change. Module tidiness belongs to dependency-change review, not the
+release checker. Do not repeat a dependency-version survey for every release.
+
+## 3. Write and commit the release note
+
+Create `docs/releases/<version>.md` for the selected version. Its first line
+must be `# ConfigKit <version>`. Give a meaningful summary and include
+compatibility impact or upgrade instructions when applicable. Link to current
+contracts for exact behavior. Review the note and affected canonical documents
+as ordinary preparation, then commit the complete candidate.
+
+End every new note with these links, replacing `VERSION` with the complete tag:
+
+```markdown
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/ConfigKit/src/tag/VERSION/COPYRIGHT) | [LICENSE](https://gitea.maximumdirect.net/eric/ConfigKit/src/tag/VERSION/LICENSE) | [ATTRIBUTION](https://gitea.maximumdirect.net/eric/ConfigKit/src/tag/VERSION/docs/oss/attribution.md)
+```
+
+Confirm the three target files exist in the candidate and review the version in
+the URLs. The future tag need not resolve remotely yet; this review adds no
+network gate. ConfigKit uses checked-in notes without hosted release objects.
+If a hosted page is used later, reuse the note and preserve its footer. Do not
+rewrite historical notes or add downloadable license assets.
+
+## 4. Publish the committed candidate
+
+Before publication, review compatibility, release-note accuracy, and the file
+list for unintended content or credentials. Retire completed roadmaps as part of
+release preparation, preserving unfinished and deferred work and repairing
+links. These are ordinary preparation tasks, not separate human sign-offs.
+
+With the release explicitly authorized, run the one publication command.
+The script resolves the repository root from its own path, so it may be invoked
+from another directory by using its path there. Replace the sample version with
+the selected version:
+
+```sh
+./scripts/release.sh v0.5.0
+```
+
+The command requires `main`, a clean index/worktree, an unused version locally
+and on the authoritative remote, and a matching note in the captured commit.
+Ignored local files do not block it. It checks remote ancestry, runs
+[`release-check.sh`](../scripts/release-check.sh) once against that commit,
+rechecks candidate and version state, pushes only that commit to `main`, then
+creates and pushes one annotated tag. The tag message is the checked-in note.
+It never commits or repairs the checkout.
+
+A successful intended tag push completes publication. The command reports the
+version and commit immediately. No CI, module retrieval, remote read-back, or
+hosted release object is required. The checker may be run separately for
+diagnosis, but it is not a prerequisite: a fresh publication invocation
+validates its candidate once.
+
+## 5. Recover from a failed or uncertain push
+
+The command performs one bounded authoritative-state check after a failed push.
+If the main push failed but authoritative main equals the candidate, it proceeds.
+If the tag push failed but its exact tag object reached the remote, it reports
+success. Otherwise it reports branch-only, conflicting, or unknown state and
+retains any local tag.
+
+Inspect exact refs before any retry. Set `release_version` to the attempted
+version and compare main with the candidate from the command's report:
+
+```sh
+release_version=v0.5.0
+authoritative=https://gitea.maximumdirect.net/eric/ConfigKit.git
+if remote_main=$(git ls-remote --refs --exit-code "$authoritative" refs/heads/main); then
+  printf 'remote main: %s\n' "$remote_main"
+else
+  result=$?
+  if [ "$result" -eq 2 ]; then
+    printf 'authoritative main confirmed absent\n' >&2
+  else
+    printf 'remote main state unknown; inspect before retrying\n' >&2
+  fi
+fi
+ref="refs/tags/$release_version"
+if remote_tag=$(git ls-remote --refs --exit-code "$authoritative" "$ref"); then
+  printf 'remote tag: %s\n' "$remote_tag"
+else
+  result=$?
+  if [ "$result" -eq 2 ]; then
+    printf 'remote tag confirmed absent\n'
+  else
+    printf 'remote tag state unknown; do not reuse the version\n' >&2
+  fi
+fi
+if local_tag=$(git rev-parse --verify "refs/tags/$release_version" 2>/dev/null); then
+  printf 'local tag object: %s\n' "$local_tag"
+else
+  printf 'no local tag object\n'
+fi
+```
+
+A query failure is not proof that the tag is absent. Compare the remote tag
+object ID with the local annotated tag object ID; its peeled commit alone is
+insufficient to establish identical publication. A conflicting published tag
+must not be moved or replaced. If remote main advanced but the tag was not
+published, report that partial progress. Only after confirming the local tag
+was never published or used by another channel may a maintainer remove it:
+
+```sh
+git tag -d "$release_version"
+```
+
+A subsequent invocation revalidates the candidate; a correctly published tag
+needs no rerun. Do not roll back main or automatically delete a tag. Transport
+or authentication failure alone does not require a new version. A defect in
+published source requires a corrected commit, a new semantically appropriate
+version and note, and the release procedure again.
+
+## 6. Optional consumer verification
+
+Only when useful or requested, read back the remote tag or retrieve the exact
+version into a new module without a local `replace` directive. These checks
+are optional and non-gating. Do not poll CI or wait for module propagation.
+Private-host credentials must already be configured. For direct-origin
+verification, set the version to the release just published (replace the sample
+below), then use a temporary consumer module and check the exact module path
+and version reported by `go list -m`:
+
+```sh
+release_version=v0.5.0
+consumer_dir=$(mktemp -d)
+(
+  cd "$consumer_dir"
+  go mod init example.invalid/configkit-release-check
+  GOPRIVATE=gitea.maximumdirect.net GOPROXY=direct go get "gitea.maximumdirect.net/eric/ConfigKit@$release_version"
+  go list -m -f '{{.Path}} {{.Version}}' gitea.maximumdirect.net/eric/ConfigKit
+)
+```
+
+The output should show the exact module path and selected version. Report this
+optional check separately from publication success.

docs/releases/v0.1.0.md

@@ -0,0 +1,72 @@
+# ConfigKit v0.1.0
+
+This is the first source release of ConfigKit, an opinionated Go library for strict,
+explainable YAML configuration loading.
+
+## Summary
+
+ConfigKit provides one typed loading lifecycle for file, byte, reader, and
+defaults-only inputs. It supports bounded explicit imports, strict composition,
+selected profiles, explicit CLI overrides, application-owned defaults and recorded
+resolution, semantic validation, provenance, redacted effective output, and safe
+historical explanation.
+
+Typed environment-name secret references and an explicit secrets-directory bootstrap
+keep credential acquisition separate from ordinary loading. Maintained consumer
+examples demonstrate simple and composed application shapes without exposing the
+private YAML parser dependency.
+
+See the [configuration contract](../config.md) and
+[consumer adoption guide](../consumers/README.md) for current behavior and examples.
+
+## Compatibility
+
+This is the initial public release, so there is no earlier ConfigKit release to
+upgrade from. The module requires Go 1.25 or newer and supports Linux and macOS on
+amd64 and arm64. Candidate validation uses patched Go 1.25 and Go 1.26 toolchains;
+native Linux and macOS evidence is required in addition to cross-builds.
+
+Configuration intentionally uses a strict YAML subset. Duplicate keys, aliases,
+anchors, merge keys, unsupported tags and scalar forms, trailing documents, and
+unknown typed fields are rejected. Composition rejects overlapping non-mapping
+definitions; replacement occurs only through selected profiles, explicit CLI
+overrides, or recorded application resolution.
+
+The private parser dependency remains explicitly pinned to
+`go.yaml.in/yaml/v4 v4.0.0-rc.6`, which was still the newest available v4 release when
+the candidate was prepared. No upstream YAML declarations are part of ConfigKit's
+public API.
+
+## Upgrade
+
+No action is required for an earlier ConfigKit version because this is the first
+release. New consumers can add the module with:
+
+```sh
+go get gitea.maximumdirect.net/eric/ConfigKit@v0.1.0
+```
+
+The authoritative host may require its normal private-module credentials. Consumers
+adapting existing application configuration should review the intentional migration
+differences in the [consumer adoption guide](../consumers/README.md), particularly
+strict YAML, string schema versions, explicit empty/null behavior, canonical module
+objects, `int64` dynamic integers, explicit CLI records, and typed secret references.
+
+## Changes
+
+- Added opaque file, byte, reader, and defaults-only sources with fixed resource
+  limits and safe structured diagnostics.
+- Added an owned strict YAML model, typed schema binding, detached defaults and
+  results, canonical projection, and private parser isolation.
+- Added explicit path/glob imports, deterministic strict composition, canonical
+  source identity and containment, and selected profile overlays.
+- Added layered presence, origins, chronological history, version checks, recorded
+  defaulting and normalization, and read-only semantic validation.
+- Added secret classification, deterministic redacted effective YAML, typed
+  environment references, and bounded explicit secrets-directory bootstrap reports.
+- Added parser-neutral explicit CLI overrides and safe structured/human historical
+  value explanations, including removed and superseded values.
+- Added maintained Narratio-, Notarius-, WeatherReporter-, and Seriatim-shaped
+  examples and migration coverage using only ConfigKit and the standard library.
+- Added race and bounded fuzz coverage plus a two-toolchain, offline, cross-platform
+  source-release checker and maintainer runbook.

docs/releases/v0.1.1.md

@@ -0,0 +1,43 @@
+# ConfigKit v0.1.1
+
+This release corrects the spelling of ConfigKit's reserved configuration key.
+
+## Summary
+
+The reserved directive key is now `configkit` instead of `_configkit`. Import
+declarations continue to use the same `imports` sequence and path/glob syntax.
+See the [configuration contract](../config.md#explicit-imports).
+
+## Compatibility
+
+This is an intentional configuration compatibility change, approved as a one-time
+[patch-release exception](../policy/release.md#policy-exceptions) because there are
+no current consumers. `_configkit` is no longer a directive or a reserved key; it
+is ordinary application data and is subject to normal schema validation. There is
+no legacy alias. `configkit` is now reserved, including in nested mappings, profiles,
+and override paths and values.
+
+The Go API, diagnostic codes, Go minimum version, and supported platforms are
+unchanged. The private YAML dependency remains pinned to
+`go.yaml.in/yaml/v4 v4.0.0-rc.6`, confirmed as the newest available v4 release
+during candidate preparation.
+
+## Upgrade
+
+Rename `_configkit` directive keys to `configkit` in root configuration files and
+imported fragments. Rename any application-owned `configkit` fields to avoid the
+newly reserved key. Update diagnostic-path expectations to the new spelling.
+Files retaining `_configkit` will not load their declared imports.
+
+Consumers can select this release with:
+
+```sh
+go get gitea.maximumdirect.net/eric/ConfigKit@v0.1.1
+```
+
+## Changes
+
+- Renamed the directive key consistently across imports, profiles, and overrides.
+- Updated current configuration documentation and the composed consumer fixture.
+- Updated behavioral tests and added coverage proving the old spelling is not an
+  import alias.

docs/releases/v0.1.2.md

@@ -0,0 +1,50 @@
+# ConfigKit v0.1.2
+
+This release adds safe enumeration of effective and removed metadata paths.
+
+## Summary
+
+`Metadata.HistoricalPaths` returns the semantic paths observed during a load,
+including paths removed by profiles, CLI overrides, or recorded resolution. This
+allows applications to discover hidden declarations and inspect their ownership
+through the existing `Metadata.History` API without reloading configuration or
+resolving unselected credentials.
+
+See the [layered metadata contract](../config.md#layered-metadata) for current
+behavior.
+
+## Compatibility
+
+This is a backward-compatible API addition. Existing APIs, configuration syntax,
+diagnostic codes, minimum Go version, and supported platforms are unchanged.
+Existing consumers do not need to change their code or configuration.
+
+Returned paths are detached, unique by canonical JSON Pointer spelling, and sorted
+by that spelling. The enumeration includes defaults and the root, exposes no
+configuration values, and performs no I/O or secret resolution.
+
+The private YAML dependency remains pinned to
+`go.yaml.in/yaml/v4 v4.0.0-rc.6`, confirmed as the newest available v4 release during
+candidate preparation.
+
+## Upgrade
+
+No action required. Consumers that want historical path discovery can update with:
+
+```sh
+go get gitea.maximumdirect.net/eric/ConfigKit@v0.1.2
+```
+
+Then iterate over `result.Metadata().HistoricalPaths()` and use `History` for
+chronological definitions or `Lookup` to determine whether each path remains
+effective.
+
+## Changes
+
+- Added `Metadata.HistoricalPaths` with detached, deterministic path enumeration.
+- Included effective, default, and removed paths while excluding paths that never
+  existed.
+- Added coverage for parent removal, mapping-to-sequence shape replacement, escaped
+  mapping keys, detached results, zero metadata, composite base ownership, and
+  avoidance of superseded secret lookup.
+- Documented historical path enumeration in the current configuration contract.

docs/releases/v0.2.0.md

@@ -0,0 +1,58 @@
+# ConfigKit v0.2.0
+
+This release adds integer schema-version input and consistent canonical sequence
+path handling.
+
+## Summary
+
+Applications can retain YAML such as `version: 4` while storing and checking their
+version as a Go string. The exception applies only to the path designated by
+`VersionRule`; unrelated fields keep strict decoding. See the
+[configuration contract](../config.md#application-schema-versions).
+
+## Compatibility
+
+This minor release intentionally changes integer schema-version input from a
+`version.type` rejection to invoking the application checker with its decimal text.
+Plain string destinations at that path now accept it. Public Go API shapes,
+minimum Go version, and supported platforms are unchanged.
+
+Parsed sequence indices now require canonical nonnegative decimal spelling.
+Signed tokens such as `+0` and `-0`, previously accepted by some traversal paths,
+no longer identify sequence elements. They remain valid literal mapping keys.
+Version checking, decoding, and metadata matching now agree on this boundary.
+
+The private YAML dependency remains pinned to `go.yaml.in/yaml/v4 v4.0.0-rc.6`,
+confirmed as the newest available v4 release during candidate preparation. Linux
+candidate checks use Go 1.25.5 and Go 1.26.7. The maintainer confirmed native macOS
+checks at `244104f` and approved carrying that result across the documentation-only
+candidate changes under the [recorded exception](../policy/release.md#policy-exceptions).
+
+## Upgrade
+
+```sh
+go get gitea.maximumdirect.net/eric/ConfigKit@v0.2.0
+```
+
+Existing string schema versions need no configuration changes. Applications using
+integer YAML versions can retain them and use a plain string field plus a
+`VersionRule`. Review the application checker: it now receives integer identifiers
+as text, and remains responsible for rejecting unsupported versions. Fractions,
+exponents, booleans, and containers remain invalid version kinds.
+
+Replace signed sequence-index tokens in configured paths with canonical indices
+(for example, `/versions/+0` becomes `/versions/0`). Do not change signed mapping
+keys. Literal integers elsewhere still do not decode into strings, and numeric
+destinations retain their existing range checks.
+
+## Changes
+
+- Added load-local, path-scoped integer-to-string schema-version decoding without
+  mutating original input or introducing general scalar coercion.
+- Preserved numeric historical input, string effective output, decoding
+  reconciliation, source attribution, and secret redaction.
+- Unified sequence path interpretation and added regression coverage for signed
+  tokens, literal mapping keys, and explicit key/index distinctions.
+- Updated maintained Notarius-shaped fixtures and migration guidance for quoted
+  and integer version forms.
+- Retired completed implementation and remediation roadmaps to Git history.

docs/releases/v0.3.0.md

@@ -0,0 +1,70 @@
+# ConfigKit v0.3.0
+
+This release adds source provenance during application resolution, separates the
+public API from its internal engine, and moves macOS to best-effort support.
+
+## Summary
+
+Resolvers can query fixed entry-state metadata and already-acquired sources using
+`Resolution.InputInfo` and `Resolution.Source`. This supports application-owned
+decisions such as resolving relative paths against their declaring configuration
+files. See the [resolution contract](../config.md#recorded-application-resolution)
+and the maintained [source-aware path example](../consumers/README.md#source-aware-application-path-policy).
+
+The root `configkit` package now owns public types and explicit wrappers around a
+single private engine. Internal changes no longer automatically expand public
+method sets through shared type aliases. See the [component overview](../internal/overview.md)
+and [facade decision](../adr/0006-public-facade.md).
+
+## Compatibility
+
+Existing consumer imports, exported API signatures, configuration syntax,
+precedence, secret handling, callback lifetime, and ownership behavior are
+preserved. The two resolution query methods are additive and available only
+during an active resolution callback; returned records remain detached. The
+library supplies provenance, not a new filesystem normalization policy.
+
+macOS on amd64 and arm64 is now best-effort rather than release-validated.
+Neither native macOS evidence nor Darwin cross-builds are required for publication,
+and macOS-specific failures do not by themselves block a release. Linux on amd64
+and arm64 retains release-gated builds and native Linux validation. See the
+[platform support policy](../policy/release.md#platform-support).
+
+The module still requires Go 1.25 or newer. The private YAML dependency remains
+pinned to `go.yaml.in/yaml/v4 v4.0.0-rc.6`, confirmed as the newest available v4
+release during preparation. It is still a prerelease dependency, isolated behind
+the existing private parser boundary; no dependency upgrade is included.
+
+Linux candidate validation uses Go 1.25.14 and Go 1.26.8, including the complete
+release checker, race tests, consumer examples, filesystem fixtures, and Linux
+cross-builds. No native macOS validation is claimed for this candidate.
+
+## Upgrade
+
+```sh
+go get gitea.maximumdirect.net/eric/ConfigKit@v0.3.0
+```
+
+No code or configuration migration is required for the facade refactor. Adopt the
+new provenance queries only if your resolver needs them. Applications retain
+ownership of relative-path bases and fallback/error behavior.
+
+macOS consumers should account for the reduced validation commitment and perform
+their own application checks when upgrading if macOS behavior is important to
+their deployment.
+
+## Changes
+
+- Added callback-scoped, fixed entry metadata and source lookup without additional
+  filesystem access or credential resolution.
+- Added a maintained Notarius-shaped path-normalization example with provenance,
+  frozen effective output, and explanation coverage.
+- Moved loading, schema, resolution, provenance/history, secret, and rendering
+  machinery into one internal engine while keeping public named types root-owned.
+- Added exact-type secret and callback adapters, with regression coverage for
+  missing version checkers and nil/zero closed-context failures.
+- Added type-aware public-boundary checks covering aliases, collections, generic
+  constraints, and exported method sets; restored public reference documentation.
+- Removed macOS release gates and retained required Linux validation.
+- Retired completed feature, implementation, and remediation documents to Git
+  history and repaired navigation to current contract and component owners.

docs/releases/v0.3.1.md

@@ -0,0 +1,43 @@
+# ConfigKit v0.3.1
+
+This release fixes secrets-directory bootstrap when the directory contains Git
+metadata or other dot-prefixed entries.
+
+## Summary
+
+`LoadSecretsDir` now ignores dot-prefixed files, directories, and symlinks,
+including `.git`, `.gitignore`, and `.DS_Store`. These entries no longer prevent
+otherwise valid secrets from loading and are omitted from the bootstrap report.
+See the [bootstrap contract](../config.md#explicit-secrets-directory-bootstrap).
+
+## Compatibility
+
+This is a backward-compatible bug fix for previously rejected directory contents.
+There are no Go API signature changes or migrations for previously accepted
+inputs. Validation of non-hidden entries, existing-environment precedence, and
+the existing enumeration and content limits remain unchanged. Hidden entries
+still count toward the directory enumeration limit.
+
+The minimum Go version remains 1.25. Linux remains release-validated and macOS
+remains best-effort. The explicitly pinned YAML dependency remains
+`go.yaml.in/yaml/v4 v4.0.0-rc.6`; reassessment found no newer published version.
+Retaining this prerelease pin avoids unrelated parser changes in this patch.
+
+## Upgrade
+
+Update the module dependency and rebuild the consuming application:
+
+```sh
+go get gitea.maximumdirect.net/eric/ConfigKit@v0.3.1
+```
+
+No configuration migration is required. A secrets directory can retain its
+dot-prefixed metadata without treating those entries as secret candidates.
+
+## Changes
+
+- Filter hidden entries before filename and metadata validation and reporting.
+- Cover hidden-only and mixed directories, including Git metadata and a dangling
+  hidden symlink, with regression tests.
+- Update public API comments and the canonical bootstrap contract.
+- Stop tracking local codebase-memory tooling artifacts and ignore their directory.

docs/releases/v0.4.0.md

@@ -0,0 +1,56 @@
+# ConfigKit v0.4.0
+
+This release renames selected configuration profiles to overlays, intentionally
+breaking the previous naming contract without compatibility aliases or fallback.
+
+## Summary
+
+Selected configuration now uses `Options.Overlay` and `overlays/<name>.yml`.
+Selection, merge rules, input precedence, and lifecycle behavior are unchanged.
+See the [selected-overlay contract](../config.md#selected-overlays).
+
+## Compatibility
+
+This is a breaking minor release before v1.0.0. Four surfaces change:
+
+- Go API: `Options.Profile` becomes `Options.Overlay`, `LayerProfile` becomes
+  `LayerOverlay`, and all seven `CodeProfile*` constants become `CodeOverlay*`.
+- Selected files: `profiles/<name>.yml` becomes `overlays/<name>.yml`; there is
+  no legacy-directory fallback.
+- Provenance: the layer string changes from `profile` to `overlay`.
+- Structured diagnostics: the `profile.*` code prefix becomes `overlay.*`.
+
+The old Go identifiers are removed. Application-owned concepts such as
+`ModelProfile` and `model_profile` are unchanged. Ordinary explicit imports from
+a directory named `profiles` remain valid base inputs.
+
+The minimum Go version remains 1.25. Linux remains release-validated and macOS
+remains best-effort. The YAML dependency remains pinned to
+`go.yaml.in/yaml/v4 v4.0.0-rc.6`; this release does not change parser dependencies.
+
+## Upgrade
+
+Update the dependency:
+
+```sh
+go get gitea.maximumdirect.net/eric/ConfigKit@v0.4.0
+```
+
+Rename the affected Go identifiers, move selected files into `overlays/`, update
+any handling of provenance-layer and diagnostic-code strings, and rebuild.
+The maintained example helper is now `LoadNarratioOverlay` rather than
+`LoadNarratioProfile`. Application CLI flag names remain application-owned;
+ConfigKit does not require renaming domain-specific profile concepts.
+See the [migration guide](../consumers/README.md#selected-overlay-migration).
+
+## Changes
+
+- Rename the selected feature consistently across the public facade, internal
+  engine, diagnostics, source labels, examples, and current documentation.
+- Add regression coverage for the new directory, absence of legacy fallback,
+  public values, explanations, and preservation of application profile fields.
+- Align contributor policies with the current shared standard.
+- Simplify release validation to one local minimum-toolchain check. CI is not a
+  release gate; successful publication of the intended tag completes the
+  source-only release. See the [release procedure](../release.md).
+- Retire completed overlay and release-workflow planning documents to Git history.

docs/releases/v0.4.1.md

@@ -0,0 +1,42 @@
+# ConfigKit v0.4.1
+
+This release formalizes ConfigKit's licensing and upstream attribution
+documentation without changing library behavior.
+
+## Summary
+
+ConfigKit now includes an explicit LGPL-3.0-or-later grant in COPYRIGHT,
+complete LGPLv3 and incorporated GPLv3 license texts, and centralized upstream
+attribution. README and release guidance provide navigation to those materials.
+
+## Compatibility
+
+No Go code, public API, configuration semantics, diagnostic behavior, or
+dependencies changed from v0.4.0. The minimum Go version remains 1.25, Linux
+remains release-validated, and macOS remains best-effort. The YAML dependency
+remains `go.yaml.in/yaml/v4 v4.0.0-rc.6`.
+
+The project grant is explicitly LGPL-3.0-or-later. Third-party material remains
+subject to its respective terms, recorded in the attribution document below.
+Published earlier releases are unchanged.
+
+## Upgrade
+
+Update the module dependency and rebuild to select this release:
+
+```sh
+go get gitea.maximumdirect.net/eric/ConfigKit@v0.4.1
+```
+
+No application-code or configuration migration is required from v0.4.0.
+
+## Changes
+
+- Add the project COPYRIGHT statement and complete standard project license texts.
+- Document go-yaml attribution with exact upstream revision links and local
+  Apache-2.0 and MIT license texts.
+- Adopt the house OSS policy and connect licensing ownership and contributor guidance.
+- Add license and attribution navigation to README and future release documents,
+  without adding release gates or changing publication mechanics.
+
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/ConfigKit/src/tag/v0.4.1/COPYRIGHT) | [LICENSE](https://gitea.maximumdirect.net/eric/ConfigKit/src/tag/v0.4.1/LICENSE) | [ATTRIBUTION](https://gitea.maximumdirect.net/eric/ConfigKit/src/tag/v0.4.1/docs/oss/attribution.md)

docs/releases/v0.4.2.md

@@ -0,0 +1,45 @@
+# ConfigKit v0.4.2
+
+This patch release simplifies and safeguards source publication and aligns
+maintainer policy and licensing guidance. Library behavior is unchanged.
+
+## Summary
+
+Maintainers can now publish a prepared release with one guarded command. It
+validates the exact committed candidate, checks the authoritative destination,
+and pushes only the candidate on `main` and its annotated version tag. The
+[release procedure](../release.md) explains preparation and partial-publication
+recovery; successful tag publication completes the source-only release without
+waiting for CI or consumer retrieval.
+
+## Compatibility
+
+No Go code, public API, configuration semantics, diagnostic behavior, or
+dependencies changed from v0.4.1. The minimum Go version remains 1.25. Linux
+amd64 and arm64 remain release-validated; macOS remains best-effort. The YAML
+dependency remains `go.yaml.in/yaml/v4 v4.0.0-rc.6`.
+
+## Upgrade
+
+Select this version and rebuild:
+
+```sh
+go get gitea.maximumdirect.net/eric/ConfigKit@v0.4.2
+```
+
+No application-code or configuration migration is required from v0.4.1.
+
+## Changes
+
+- Add guarded single-command publication with exact candidate, version, and
+  remote checks; note-derived annotated tags; and bounded failed-push recovery.
+- Keep one offline race suite, one full vet pass, and Linux amd64/arm64 builds
+  as release gates. Formatting and whitespace remain development checks;
+  dependency tidiness is reviewed when dependencies change.
+- Align adopted policies and contributor guidance with their pinned upstream
+  revision, and include the CC BY-SA 4.0 license text and attribution for
+  adapted policy material. The project grant remains LGPL-3.0-or-later.
+- Retire completed release-workflow and policy-alignment planning records while
+  preserving their history in Git. Deferred scope remains documented.
+
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/ConfigKit/src/tag/v0.4.2/COPYRIGHT) | [LICENSE](https://gitea.maximumdirect.net/eric/ConfigKit/src/tag/v0.4.2/LICENSE) | [ATTRIBUTION](https://gitea.maximumdirect.net/eric/ConfigKit/src/tag/v0.4.2/docs/oss/attribution.md)

docs/releases/v0.5.0.md

@@ -0,0 +1,53 @@
+# ConfigKit v0.5.0
+
+This minor release adds source-backed layered configuration and built-in sibling
+inheritance, so applications can load one complete configuration while retaining
+presence, source context, and explainable derivation.
+
+## Summary
+
+- `LoadLayered` combines ordered underlay groups beneath the main input, selected
+  overlay, and explicit CLI overrides. Inputs within a group still compose
+  strictly; precedence tiers combine mappings recursively. The main input
+  remains the owner of the optional schema-version check.
+- `NewFilesystem(...).File(...)` accepts caller-owned `fs.FS` sources, and
+  `Mapping(...)` snapshots supported built-in values as a labeled source.
+  `Result.SourceContext` and `Resolution.SourceContext` expose passive resource
+  contexts for values from file-backed sources.
+- `extends` now resolves a mapping against one named sibling after source
+  precedence and before typed decoding. Inherited values count as explicit
+  input. Origins, history, explanations, and redacted rendering retain the
+  source and the structural path by which a value reached its destination.
+  Review corrections preserve immutable nested-history evidence and bounded
+  expansion work.
+
+See the [configuration contract](../config.md#layered-loading),
+[inheritance rules](../config.md#sibling-inheritance), and
+[consumer examples](../consumers/README.md) for current behavior.
+
+## Compatibility and upgrade
+
+This is an intentional pre-v1 incompatible minor release for configurations
+that use `extends` as ordinary data. That key is now reserved wherever an input
+mapping occurs; it is consumed before decoding. Rename any such YAML key and
+corresponding Go field, then rebuild. No collection registration or opt-in flag
+is available. Configurations without `extends` retain their existing meaning.
+
+Applications adopting the new features may move source-backed defaults into
+explicit `Underlay` groups, use `SourceContext` for relative resources, or
+replace application-owned sibling merging with one `extends` relationship per
+mapping. Adoption is optional. The maintained
+[named-preset example](../consumers/README.md#named-sibling-inheritance)
+shows inherited `false` and destination-local nested resolution.
+
+Select the new module version:
+
+```sh
+go get gitea.maximumdirect.net/eric/ConfigKit@v0.5.0
+```
+
+The minimum Go line remains 1.25. Linux amd64 and arm64 remain the
+release-validated targets; macOS remains best-effort. The YAML dependency is
+unchanged at `go.yaml.in/yaml/v4 v4.0.0-rc.6`.
+
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/ConfigKit/src/tag/v0.5.0/COPYRIGHT) | [LICENSE](https://gitea.maximumdirect.net/eric/ConfigKit/src/tag/v0.5.0/LICENSE) | [ATTRIBUTION](https://gitea.maximumdirect.net/eric/ConfigKit/src/tag/v0.5.0/docs/oss/attribution.md)

docs/roadmap/deferred.md

@@ -0,0 +1,34 @@
+# Deferred Scope
+
+This document owns intentionally excluded features, not a committed delivery plan.
+The [architecture policy](../policy/architecture.md) governs changes to these
+boundaries. Implemented behavior belongs in the [configuration contract](../config.md)
+and consumer adoption in the [consumer guide](../consumers/README.md).
+
+## Explicit non-goals and deferred scope
+
+General environment-variable configuration overlays are not supported. Typed secret
+references and explicit directory bootstrap are the environment convention. Literal
+credential configuration and implicit secret-directory discovery are unsupported.
+
+The following remain deliberately excluded:
+
+- automatic `conf.d` discovery;
+- remote imports, arbitrary providers, and additional configuration formats;
+- custom merge strategies, sequence merging, reset operators, multiple-parent
+  inheritance, and cross-scope references;
+- named overlay inheritance;
+- parser-specific or custom structural-decoding extension APIs;
+- generic dynamic-subtree conversion and module-registry APIs;
+- automatic schema migrations;
+- hot reload, runtime resource replacement, and remote resource validation;
+- a bundled CLI framework or application commands; and
+- configuration diffs and fingerprints.
+
+Applications may build their own validate, effective-value, source, bootstrap, and
+explanation commands around the library. Broadening these boundaries requires
+concrete consumer evidence, compatibility review, and an explicit design change.
+
+Built-in sibling inheritance using `extends` is implemented as described in the
+[configuration contract](../config.md#sibling-inheritance). It is distinct from
+inheritance between selected overlay files, which remains excluded above.

docs/roadmap/release-readiness.md

@@ -1,25 +0,0 @@
-# Release Readiness
-
-## Status and ownership
-
-ConfigKit is not release-ready. This document tracks outstanding release
-prerequisites under the [temporary bootstrap exception](../policy/release.md#temporary-bootstrap-deferral).
-It is not the library implementation plan and does not assign implementation
-stages. The maintainer preparing the first release owns closure.
-
-## Outstanding prerequisites
-
-| Gap | Evidence required to close |
-| --- | --- |
-| No Go module or declared support matrix | Established module path, supported Go versions and platform targets documented in the release procedure |
-| No release runbook | `docs/release.md` exists with the prerequisites, commands, publication guards, and verification required by release policy |
-| No complete release checker | A documented command exists and exercises every applicable automated candidate gate; manual gates and inapplicable checks are explicit |
-| No consumer verification procedure | Runbook verifies retrieval of the exact released module version and a representative consumer build without local replacement directives |
-| No verified secret/precedence/explanation contracts | Current contracts and passing bootstrap skip/partial-failure, secret isolation, CLI precedence, and safe historical-value regressions; representative consumer examples |
-| No validated release candidate | Version-matched release note, current contracts/examples, and complete checks against the exact committed candidate |
-
-No release can proceed while these prerequisites remain open. Close items only
-on evidence from actual files and checks, not proposed commands. Record closure
-evidence here while this roadmap remains active. Once all gaps are closed,
-remove the bootstrap exception and retire this document in favor of the
-operational runbook and normal release records.

documentation_test.go

@@ -0,0 +1,151 @@
+package configkit
+
+import (
+	"bufio"
+	"fmt"
+	"net/url"
+	"os"
+	"path/filepath"
+	"regexp"
+	"strings"
+	"testing"
+	"unicode"
+)
+
+var markdownLinkPattern = regexp.MustCompile(`(?m)(?:^|[[:space:]])\[[^\]]*\]\(([^)[:space:]]+)`)
+
+func TestLocalDocumentationLinks(t *testing.T) {
+	repository, err := filepath.Abs(".")
+	if err != nil {
+		t.Fatal(err)
+	}
+	var failures []string
+	err = filepath.WalkDir(repository, func(path string, entry os.DirEntry, walkErr error) error {
+		if walkErr != nil {
+			return walkErr
+		}
+		if entry.IsDir() {
+			if entry.Name() == ".git" {
+				return filepath.SkipDir
+			}
+			return nil
+		}
+		if filepath.Ext(path) != ".md" {
+			return nil
+		}
+		content, readErr := os.ReadFile(path)
+		if readErr != nil {
+			return readErr
+		}
+		for _, match := range markdownLinkPattern.FindAllStringSubmatch(string(content), -1) {
+			target := strings.Trim(match[1], "<>")
+			if strings.Contains(target, "://") || strings.HasPrefix(target, "mailto:") {
+				continue
+			}
+			filePart, fragment, _ := strings.Cut(target, "#")
+			decoded, decodeErr := url.PathUnescape(filePart)
+			if decodeErr != nil {
+				failures = append(failures, fmt.Sprintf("%s: invalid escaped link %q", relativePath(repository, path), target))
+				continue
+			}
+			linked := path
+			if decoded != "" {
+				linked = filepath.Clean(filepath.Join(filepath.Dir(path), filepath.FromSlash(decoded)))
+			}
+			_, statErr := os.Stat(linked)
+			outside := linked != repository && !strings.HasPrefix(linked, repository+string(filepath.Separator))
+			if os.IsNotExist(statErr) && outside && optionalSiblingSource(repository, linked) {
+				continue // Recorded sibling-source links are optional in isolated clones.
+			}
+			if statErr != nil {
+				failures = append(failures, fmt.Sprintf("%s: missing local link %q", relativePath(repository, path), target))
+				continue
+			}
+			if fragment != "" && filepath.Ext(linked) == ".md" && !markdownHasFragment(linked, fragment) {
+				failures = append(failures, fmt.Sprintf("%s: missing fragment in %q", relativePath(repository, path), target))
+			}
+		}
+		return nil
+	})
+	if err != nil {
+		t.Fatal(err)
+	}
+	if len(failures) != 0 {
+		t.Fatalf("documentation link failures:\n%s", strings.Join(failures, "\n"))
+	}
+}
+
+func optionalSiblingSource(repository, linked string) bool {
+	relative, err := filepath.Rel(filepath.Dir(repository), linked)
+	if err != nil || relative == "." || filepath.IsAbs(relative) {
+		return false
+	}
+	parts := strings.Split(filepath.ToSlash(relative), "/")
+	if len(parts) == 0 {
+		return false
+	}
+	switch strings.ToLower(parts[0]) {
+	case "narratio", "notarius", "weatherreporter", "seriatim":
+		return true
+	default:
+		return false
+	}
+}
+
+func markdownHasFragment(path, wanted string) bool {
+	file, err := os.Open(path)
+	if err != nil {
+		return false
+	}
+	defer file.Close()
+	wanted, err = url.PathUnescape(wanted)
+	if err != nil {
+		return false
+	}
+	seen := make(map[string]int)
+	scanner := bufio.NewScanner(file)
+	for scanner.Scan() {
+		line := strings.TrimSpace(scanner.Text())
+		if !strings.HasPrefix(line, "#") {
+			continue
+		}
+		heading := strings.TrimSpace(strings.TrimLeft(line, "#"))
+		base := markdownFragment(heading)
+		count := seen[base]
+		seen[base]++
+		fragment := base
+		if count > 0 {
+			fragment = fmt.Sprintf("%s-%d", base, count)
+		}
+		if fragment == wanted {
+			return true
+		}
+	}
+	return false
+}
+
+func markdownFragment(heading string) string {
+	var result strings.Builder
+	previousSpace := false
+	for _, character := range strings.ToLower(heading) {
+		switch {
+		case unicode.IsLetter(character), unicode.IsDigit(character), character == '_', character == '-':
+			result.WriteRune(character)
+			previousSpace = false
+		case unicode.IsSpace(character):
+			if result.Len() > 0 && !previousSpace {
+				result.WriteByte('-')
+				previousSpace = true
+			}
+		}
+	}
+	return strings.TrimRight(result.String(), "-")
+}
+
+func relativePath(root, path string) string {
+	relative, err := filepath.Rel(root, path)
+	if err != nil {
+		return path
+	}
+	return filepath.ToSlash(relative)
+}

example_test.go

@@ -0,0 +1,150 @@
+package configkit_test
+
+import (
+	"errors"
+	"fmt"
+	"os"
+	"strings"
+
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+)
+
+func ExampleLoad() {
+	type Config struct {
+		Enabled bool `yaml:"enabled"`
+		Workers int  `yaml:"workers"`
+	}
+	result, err := configkit.Load[Config](configkit.Bytes("example.yml", []byte("enabled: true\nworkers: 3\n")))
+	fmt.Println(result.Config, err)
+	// Output: {true 3} <nil>
+}
+
+func ExampleNoSource() {
+	type Config struct {
+		Workers int `yaml:"workers"`
+	}
+	result, err := configkit.Load(configkit.NoSource(), configkit.Options[Config]{
+		Definition: configkit.Definition[Config]{Defaults: func() Config { return Config{Workers: 4} }},
+	})
+	fmt.Println(result.Config.Workers, len(result.Sources()), err)
+	// Output: 4 0 <nil>
+}
+
+func ExampleValidation_Error() {
+	type Config struct {
+		First  string `yaml:"first"`
+		Second string `yaml:"second"`
+	}
+	_, err := configkit.Load(configkit.Bytes("duplicates.yml", []byte("first: same\nsecond: same\n")), configkit.Options[Config]{
+		Definition: configkit.Definition[Config]{Validate: func(configuration *Config, validation *configkit.Validation) {
+			if configuration.First == configuration.Second {
+				validation.Error(configkit.Keys("second"), "must differ from first", configkit.Keys("first"))
+			}
+		}},
+	})
+	var loadError *configkit.LoadError
+	errors.As(err, &loadError)
+	diagnostic := loadError.Diagnostics()[0]
+	fmt.Println(diagnostic.Code, diagnostic.Path, len(diagnostic.Related))
+	// Output: validate.error /second 1
+}
+
+func ExampleVersionRule() {
+	type Config struct {
+		Version string `yaml:"version"`
+	}
+	_, err := configkit.Load(configkit.Bytes("version.yml", []byte("version: old\n")), configkit.Options[Config]{
+		Definition: configkit.Definition[Config]{Version: &configkit.VersionRule{
+			Path: configkit.Keys("version"),
+			Check: func(version configkit.Version, validation *configkit.Validation) error {
+				if version.Text != "v1" {
+					validation.Error(configkit.Keys("version"), "unsupported version; migrate using the application guide")
+				}
+				return nil
+			},
+		}},
+	})
+	var loadError *configkit.LoadError
+	errors.As(err, &loadError)
+	fmt.Println(loadError.Diagnostics()[0].Message)
+	// Output: unsupported version; migrate using the application guide
+}
+
+func ExampleResolution() {
+	type Config struct {
+		Input   int `yaml:"input"`
+		Derived int `yaml:"derived"`
+	}
+	var order []string
+	result, err := configkit.Load(configkit.Bytes("resolved.yml", []byte("input: 3\n")), configkit.Options[Config]{
+		Definition: configkit.Definition[Config]{
+			Resolve: func(configuration *Config, resolution *configkit.Resolution) error {
+				order = append(order, "resolve")
+				configkit.Default(resolution, configkit.Keys("derived"), &configuration.Derived,
+					configuration.Input*2, "derived from input", configkit.Keys("input"))
+				return nil
+			},
+			Validate: func(configuration *Config, validation *configkit.Validation) {
+				order = append(order, "validate")
+				if configuration.Derived < configuration.Input {
+					validation.Error(configkit.Keys("derived"), "must not be less than input")
+				}
+			},
+		},
+	})
+	fmt.Println(strings.Join(order, " then "), result.Config.Derived, err)
+	// Output: resolve then validate 6 <nil>
+}
+
+func ExampleSecretEnv() {
+	const name = "CONFIGKIT_EXAMPLE_API_KEY"
+	previous, present := os.LookupEnv(name)
+	_ = os.Setenv(name, "disposable-example-value")
+	defer func() {
+		if present {
+			_ = os.Setenv(name, previous)
+		} else {
+			_ = os.Unsetenv(name)
+		}
+	}()
+
+	type Config struct {
+		APIKey configkit.Secret `yaml:"api_key"`
+	}
+	result, err := configkit.Load[Config](configkit.Bytes("secret.yml", []byte("api_key: "+name+"\n")))
+	fmt.Println(result.Config.APIKey.EnvName(), result.Config.APIKey.IsResolved(), err)
+	// Output: CONFIGKIT_EXAMPLE_API_KEY true <nil>
+}
+
+func ExampleOverride() {
+	type Config struct {
+		Workers int `yaml:"workers"`
+	}
+	workers, workersWasSet := 0, true // Supplied by the application's CLI parser.
+	var overrides []configkit.Override
+	if workersWasSet {
+		overrides = append(overrides, configkit.Override{
+			Path: configkit.Keys("workers"), Value: workers, Flag: "--workers",
+		})
+	}
+	result, err := configkit.Load(configkit.NoSource(), configkit.Options[Config]{
+		Definition: configkit.Definition[Config]{Defaults: func() Config { return Config{Workers: 4} }},
+		Overrides:  overrides,
+	})
+	fmt.Println(result.Config.Workers, result.Sources()[0].Label, err)
+	// Output: 0 --workers <nil>
+}
+
+func ExampleResult_Explain() {
+	type Config struct {
+		Workers int `yaml:"workers"`
+	}
+	result, err := configkit.Load(configkit.Bytes("config.yml", []byte("workers: 8\n")), configkit.Options[Config]{
+		Definition: configkit.Definition[Config]{Defaults: func() Config { return Config{Workers: 4} }},
+	})
+	explanation, ok := result.Explain(configkit.Keys("workers"))
+	fmt.Printf("%s -> %s known=%t error=%v\n",
+		strings.TrimSpace(explanation.History[0].After.YAML),
+		strings.TrimSpace(explanation.Effective.YAML), ok, err)
+	// Output: 4 -> 8 known=true error=<nil>
+}

examples/consumers/consumers.go

@@ -0,0 +1,395 @@
+// Package consumers contains small, maintained application shapes that exercise
+// ConfigKit without making consumer domain policy part of the library API.
+package consumers
+
+import (
+	"math"
+	"path/filepath"
+	"strconv"
+	"strings"
+	"time"
+
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+)
+
+// Artifact is a Narratio-shaped generated output declaration.
+type Artifact struct {
+	Output  string        `yaml:"output"`
+	Timeout time.Duration `yaml:"timeout"`
+}
+
+// NarratioConfig demonstrates application defaults, partial imports, and
+// application-owned model-profile and artifact semantics.
+type NarratioConfig struct {
+	PollInterval time.Duration       `yaml:"poll_interval"`
+	Timeout      time.Duration       `yaml:"timeout"`
+	ModelProfile string              `yaml:"model_profile"`
+	Artifacts    map[string]Artifact `yaml:"artifacts"`
+}
+
+// LoadNarratio loads the maintained import fixture with Narratio-shaped rules.
+func LoadNarratio(path string) (*configkit.Result[NarratioConfig], error) {
+	return LoadNarratioOverlay(path, "")
+}
+
+// LoadNarratioOverlay selects a ConfigKit configuration overlay independently
+// from the application's ModelProfile field.
+func LoadNarratioOverlay(path, overlay string) (*configkit.Result[NarratioConfig], error) {
+	return configkit.Load(configkit.File(path), configkit.Options[NarratioConfig]{
+		Imports: true, Overlay: overlay,
+		Definition: configkit.Definition[NarratioConfig]{
+			Defaults: func() NarratioConfig { return NarratioConfig{PollInterval: time.Minute} },
+			Resolve:  resolveNarratio,
+			Validate: validateNarratio,
+		},
+	})
+}
+
+func resolveNarratio(configuration *NarratioConfig, resolution *configkit.Resolution) error {
+	configkit.Default(resolution, configkit.Keys("timeout"), &configuration.Timeout,
+		configuration.PollInterval/10, "derived from poll interval", configkit.Keys("poll_interval"))
+	for name, artifact := range configuration.Artifacts {
+		path := configkit.Keys("artifacts", name)
+		configkit.Default(resolution, path.Key("timeout"), &artifact.Timeout,
+			configuration.Timeout, "inherited pipeline timeout", configkit.Keys("timeout"))
+		configkit.Normalize(resolution, path.Key("output"), &artifact.Output,
+			strings.TrimSpace(artifact.Output), "trimmed artifact output")
+		configuration.Artifacts[name] = artifact
+	}
+	return nil
+}
+
+func validateNarratio(configuration *NarratioConfig, validation *configkit.Validation) {
+	if configuration.PollInterval <= 0 {
+		validation.Error(configkit.Keys("poll_interval"), "must be positive")
+	}
+	if configuration.Timeout <= 0 {
+		validation.Error(configkit.Keys("timeout"), "must be positive")
+	}
+	for name, artifact := range configuration.Artifacts {
+		path := configkit.Keys("artifacts", name)
+		if artifact.Output == "" {
+			validation.Error(path.Key("output"), "must be nonempty")
+		}
+		if artifact.Timeout <= 0 {
+			validation.Error(path.Key("timeout"), "must be positive")
+		}
+	}
+}
+
+// ObjectBinding is a Notarius-shaped canonical object binding. Options remain
+// dynamic because the application catalog selects their schema at runtime.
+type ObjectBinding struct {
+	Object  string         `yaml:"object"`
+	Options map[string]any `yaml:"options"`
+}
+
+// NotariusConfig demonstrates string-backed versions and dynamic catalog options.
+type NotariusConfig struct {
+	Version  string          `yaml:"version"`
+	Bindings []ObjectBinding `yaml:"bindings"`
+}
+
+// LoadNotarius loads a Notarius-shaped configuration.
+func LoadNotarius(path string) (*configkit.Result[NotariusConfig], error) {
+	return configkit.Load(configkit.File(path), configkit.Options[NotariusConfig]{
+		Definition: configkit.Definition[NotariusConfig]{
+			Version:  &configkit.VersionRule{Path: configkit.Keys("version"), Check: requireVersion("4")},
+			Validate: validateNotarius,
+		},
+	})
+}
+
+func requireVersion(expected string) func(configkit.Version, *configkit.Validation) error {
+	return func(version configkit.Version, validation *configkit.Validation) error {
+		if !version.Present || version.Null || version.Text != expected {
+			validation.Error(configkit.Keys("version"), "unsupported configuration version")
+		}
+		return nil
+	}
+}
+
+func validateNotarius(configuration *NotariusConfig, validation *configkit.Validation) {
+	for index, binding := range configuration.Bindings {
+		path := configkit.Keys("bindings").Index(index)
+		if binding.Object != "summary" && binding.Object != "registry" {
+			validation.Error(path.Key("object"), "unsupported object binding")
+		}
+		for key, value := range binding.Options {
+			optionPath := path.Key("options").Key(key)
+			switch key {
+			case "window_units":
+				units, ok := value.(int64)
+				if !ok || units < 1 {
+					validation.Error(optionPath, "must be a positive integer")
+				}
+			case "format":
+				if _, ok := value.(string); !ok {
+					validation.Error(optionPath, "must be a string")
+				}
+			default:
+				validation.Error(optionPath, "unsupported object option")
+			}
+		}
+	}
+}
+
+// NotariusWindow converts ConfigKit's portable dynamic integer only at the
+// application runtime boundary.
+func NotariusWindow(configuration NotariusConfig, binding int) (int, bool) {
+	if binding < 0 || binding >= len(configuration.Bindings) {
+		return 0, false
+	}
+	value, ok := configuration.Bindings[binding].Options["window_units"].(int64)
+	if !ok || value < 1 || (strconv.IntSize == 32 && value > math.MaxInt32) {
+		return 0, false
+	}
+	return int(value), true
+}
+
+// NotariusPathConfig demonstrates application-owned interpretation of a
+// path-valued configuration field. ConfigKit supplies provenance; this example
+// selects its own relative-path bases.
+type NotariusPathConfig struct {
+	Reference string `yaml:"reference"`
+	Sensitive string `yaml:"sensitive"`
+}
+
+// LoadNotariusPaths loads the path-bearing Notarius-shaped example. InvocationDir
+// is the application-supplied base for relative CLI overrides; it is never read
+// from the process working directory.
+func LoadNotariusPaths(path, invocationDir string, overrides ...configkit.Override) (*configkit.Result[NotariusPathConfig], error) {
+	return configkit.Load(configkit.File(path), configkit.Options[NotariusPathConfig]{
+		Imports: true, Overrides: overrides,
+		Definition: configkit.Definition[NotariusPathConfig]{
+			Defaults: func() NotariusPathConfig { return NotariusPathConfig{Reference: "defaults/reference.txt"} },
+			Resolve: func(configuration *NotariusPathConfig, resolution *configkit.Resolution) error {
+				resolveNotariusReference(configuration, resolution, invocationDir)
+				return nil
+			},
+			Secret: func(path configkit.Path) bool { return path.String() == "/sensitive" },
+		},
+	})
+}
+
+func resolveNotariusReference(configuration *NotariusPathConfig, resolution *configkit.Resolution, invocationDir string) {
+	path := configkit.Keys("reference")
+	if configuration.Reference == "" || filepath.IsAbs(configuration.Reference) {
+		return
+	}
+	info, found := resolution.InputInfo(path)
+	if !found {
+		resolution.Warning(path, "relative reference has no entry provenance")
+		return
+	}
+
+	base := ""
+	if info.Origin.Layer == configkit.LayerCLI {
+		base = invocationDir
+		if base == "" {
+			resolution.Warning(path, "relative CLI reference has no invocation directory")
+			return
+		}
+	} else {
+		sourceID := "source-1" // ConfigKit's primary-source identity convention.
+		if info.Origin.Layer != configkit.LayerDefault {
+			if len(info.Origin.Locations) != 1 {
+				resolution.Warning(path, "relative reference has no unambiguous declaring source")
+				return
+			}
+			sourceID = info.Origin.Locations[0].SourceID
+		}
+		source, exists := resolution.Source(sourceID)
+		if !exists || source.Path == "" {
+			resolution.Warning(path, "relative reference has no declaring file")
+			return
+		}
+		base = filepath.Dir(source.Path)
+	}
+	configkit.Normalize(resolution, path, &configuration.Reference,
+		filepath.Join(base, configuration.Reference), "resolved relative reference from entry source")
+}
+
+// ModuleOptions is a WeatherReporter-shaped union of known module option fields.
+type ModuleOptions struct {
+	WindowUnits *int     `yaml:"window_units"`
+	Sections    []string `yaml:"sections"`
+}
+
+// ModuleSpec uses the canonical object form instead of a string shorthand.
+type ModuleSpec struct {
+	Module  string        `yaml:"module"`
+	Options ModuleOptions `yaml:"options"`
+}
+
+// ReportConfig keeps report-specific lists application-owned.
+type ReportConfig struct {
+	Modules       []ModuleSpec `yaml:"modules"`
+	PathTemplates []string     `yaml:"path_templates"`
+}
+
+// WeatherConfig demonstrates simple defaults, reports, module options, and an
+// optional typed secret reference.
+type WeatherConfig struct {
+	Units   string                  `yaml:"units"`
+	Reports map[string]ReportConfig `yaml:"reports"`
+	Token   *configkit.Secret       `yaml:"token"`
+}
+
+// LoadWeather loads a WeatherReporter-shaped source and explicit CLI records.
+func LoadWeather(source configkit.Source, overrides ...configkit.Override) (*configkit.Result[WeatherConfig], error) {
+	return configkit.Load(source, configkit.Options[WeatherConfig]{
+		Overrides: overrides,
+		Definition: weatherDefinition(func() WeatherConfig {
+			return WeatherConfig{Units: "metric"}
+		}),
+	})
+}
+
+// LoadConstructedWeather runs the same rules over a detached constructed value.
+func LoadConstructedWeather(configuration WeatherConfig) (*configkit.Result[WeatherConfig], error) {
+	return configkit.Load(configkit.NoSource(), configkit.Options[WeatherConfig]{
+		Definition: weatherDefinition(func() WeatherConfig { return configuration }),
+	})
+}
+
+func weatherDefinition(defaults func() WeatherConfig) configkit.Definition[WeatherConfig] {
+	return configkit.Definition[WeatherConfig]{
+		Defaults: defaults,
+		Resolve: func(configuration *WeatherConfig, resolution *configkit.Resolution) error {
+			for reportName, report := range configuration.Reports {
+				var modules []ModuleSpec
+				if report.Modules != nil {
+					modules = append(make([]ModuleSpec, 0, len(report.Modules)), report.Modules...)
+				}
+				for index, module := range modules {
+					if module.Options.Sections != nil {
+						sections := append([]string(nil), module.Options.Sections...)
+						for position := range sections {
+							sections[position] = strings.TrimSpace(sections[position])
+						}
+						module.Options.Sections = sections
+					}
+					modules[index] = module
+				}
+				configkit.Normalize(resolution, configkit.Keys("reports", reportName, "modules"),
+					&report.Modules, modules, "normalized module options")
+				configuration.Reports[reportName] = report
+			}
+			return nil
+		},
+		Validate: validateWeather,
+	}
+}
+
+func validateWeather(configuration *WeatherConfig, validation *configkit.Validation) {
+	if configuration.Units != "metric" && configuration.Units != "us" {
+		validation.Error(configkit.Keys("units"), "must be metric or us")
+	}
+	for reportName, report := range configuration.Reports {
+		path := configkit.Keys("reports", reportName)
+		if report.Modules != nil && len(report.Modules) == 0 {
+			validation.Error(path.Key("modules"), "must contain at least one module")
+		}
+		if report.PathTemplates != nil && len(report.PathTemplates) == 0 {
+			validation.Error(path.Key("path_templates"), "must contain at least one template")
+		}
+		for index, module := range report.Modules {
+			modulePath := path.Key("modules").Index(index)
+			switch module.Module {
+			case "chunker":
+				if module.Options.WindowUnits == nil || *module.Options.WindowUnits < 1 {
+					validation.Error(modulePath.Key("options").Key("window_units"), "must be a positive integer")
+				}
+				if module.Options.Sections != nil {
+					validation.Error(modulePath.Key("options").Key("sections"), "not supported by this module")
+				}
+			case "discussion":
+				if module.Options.WindowUnits != nil {
+					validation.Error(modulePath.Key("options").Key("window_units"), "not supported by this module")
+				}
+				if len(module.Options.Sections) == 0 {
+					validation.Error(modulePath.Key("options").Key("sections"), "must contain at least one section")
+				}
+			default:
+				validation.Error(modulePath.Key("module"), "unsupported module")
+			}
+		}
+	}
+}
+
+// SpeakerRule and SpeakerRules preserve declaration order for application matching.
+type SpeakerRule struct {
+	Prefix string `yaml:"prefix"`
+	Name   string `yaml:"name"`
+}
+
+type SpeakerRules struct {
+	Rules []SpeakerRule `yaml:"rules"`
+}
+
+// AutocorrectRule and AutocorrectRules preserve replacement order.
+type AutocorrectRule struct {
+	Find    string `yaml:"find"`
+	Replace string `yaml:"replace"`
+}
+
+type AutocorrectRules struct {
+	Rules []AutocorrectRule `yaml:"rules"`
+}
+
+// LoadSpeakerRules loads one independent Seriatim-shaped rule file.
+func LoadSpeakerRules(path string) (*configkit.Result[SpeakerRules], error) {
+	return configkit.Load(configkit.File(path), configkit.Options[SpeakerRules]{
+		Definition: configkit.Definition[SpeakerRules]{Validate: validateSpeakerRules},
+	})
+}
+
+// LoadAutocorrectRules loads another independent ordered rule file.
+func LoadAutocorrectRules(path string) (*configkit.Result[AutocorrectRules], error) {
+	return configkit.Load(configkit.File(path), configkit.Options[AutocorrectRules]{
+		Definition: configkit.Definition[AutocorrectRules]{Validate: validateAutocorrectRules},
+	})
+}
+
+func validateSpeakerRules(configuration *SpeakerRules, validation *configkit.Validation) {
+	seen := make(map[string]int)
+	for index, rule := range configuration.Rules {
+		path := configkit.Keys("rules").Index(index)
+		if rule.Prefix == "" {
+			validation.Error(path.Key("prefix"), "must be nonempty")
+		}
+		if previous, ok := seen[rule.Prefix]; ok {
+			validation.Error(path.Key("prefix"), "prefix must be unique",
+				configkit.Keys("rules").Index(previous).Key("prefix"))
+		}
+		seen[rule.Prefix] = index
+	}
+}
+
+func validateAutocorrectRules(configuration *AutocorrectRules, validation *configkit.Validation) {
+	for index, rule := range configuration.Rules {
+		path := configkit.Keys("rules").Index(index)
+		if rule.Find == "" {
+			validation.Error(path.Key("find"), "must be nonempty")
+		}
+	}
+}
+
+// SpeakerName is application runtime matching, not configuration infrastructure.
+func SpeakerName(rules SpeakerRules, input string) (string, bool) {
+	for _, rule := range rules.Rules {
+		if strings.HasPrefix(input, rule.Prefix) {
+			return rule.Name, true
+		}
+	}
+	return "", false
+}
+
+// ApplyAutocorrect is application runtime replacement in declared order.
+func ApplyAutocorrect(rules AutocorrectRules, input string) string {
+	for _, rule := range rules.Rules {
+		input = strings.ReplaceAll(input, rule.Find, rule.Replace)
+	}
+	return input
+}

examples/consumers/consumers_test.go

@@ -0,0 +1,369 @@
+package consumers_test
+
+import (
+	"bytes"
+	"errors"
+	"fmt"
+	"os"
+	"path/filepath"
+	"reflect"
+	"runtime"
+	"strings"
+	"testing"
+
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+	"gitea.maximumdirect.net/eric/ConfigKit/examples/consumers"
+)
+
+func Example_narratio() {
+	result, err := consumers.LoadNarratio(fixture("narratio", "pipeline.yml"))
+	artifact := result.Config.Artifacts["transcript"]
+	fmt.Println(result.Config.ModelProfile, artifact.Output, result.Config.Timeout, artifact.Timeout, err)
+	// Output: concise transcript.txt 6s 6s <nil>
+}
+
+func Example_notarius() {
+	result, err := consumers.LoadNotarius(fixture("notarius", "config.yml"))
+	window, ok := consumers.NotariusWindow(result.Config, 0)
+	fmt.Println(result.Config.Version, result.Config.Bindings[0].Object, window, ok, err)
+	// Output: 4 summary 12 true <nil>
+}
+
+func Example_notariusPaths() {
+	result, err := consumers.LoadNotariusPaths(fixture("notarius-paths", "main.yml"), "/invocation")
+	fmt.Println(filepath.Base(result.Config.Reference), err)
+	// Output: imported.txt <nil>
+}
+
+func Example_weatherReporter() {
+	defaults, defaultsErr := consumers.LoadWeather(configkit.NoSource())
+	result, err := consumers.LoadWeather(configkit.File(fixture("weather", "config.yml")))
+	discussion := result.Config.Reports["daily"].Modules[1]
+	fmt.Println(defaults.Config.Units, result.Config.Units, discussion.Options.Sections[0], defaultsErr, err)
+	// Output: metric us short_term <nil> <nil>
+}
+
+func Example_seriatim() {
+	speakers, speakerErr := consumers.LoadSpeakerRules(fixture("seriatim", "speakers.yml"))
+	autocorrect, autocorrectErr := consumers.LoadAutocorrectRules(fixture("seriatim", "autocorrect.yml"))
+	name, found := consumers.SpeakerName(speakers.Config, "Guest: teh event occured")
+	text := consumers.ApplyAutocorrect(autocorrect.Config, "teh event occured")
+	fmt.Println(name, found, text, speakerErr, autocorrectErr)
+	// Output: visitor true the event occurred <nil> <nil>
+}
+
+func Example_inheritedPresets() {
+	result, err := consumers.LoadPresets(configkit.File(fixture("inheritance", "presets.yml")))
+	if err != nil {
+		fmt.Println(err)
+		return
+	}
+	path := configkit.Keys("presets", "custom", "enabled")
+	info, _ := result.Metadata().Lookup(path)
+	custom := result.Config.Presets["custom"]
+	fmt.Println(custom.Enabled, result.Metadata().IsExplicit(path), custom.Settings["secondary"]["width"])
+	fmt.Println(info.Origin.Locations[0].SourceID, info.Origin.Inheritance[0].From)
+	// Output:
+	// false true 20
+	// source-1 /presets/base/enabled
+}
+
+func Example_weatherStartup() {
+	const blockedName = "CONFIGKIT_WEATHER_EXAMPLE_BLOCKED"
+	const tokenName = "CONFIGKIT_WEATHER_EXAMPLE_TOKEN"
+	restoreBlocked := preserveEnvironment(blockedName)
+	restoreToken := preserveEnvironment(tokenName)
+	defer restoreBlocked()
+	defer restoreToken()
+	_ = os.Setenv(blockedName, "")
+	_ = os.Unsetenv(tokenName)
+
+	directory, _ := os.MkdirTemp("", "configkit-weather-example-")
+	defer os.RemoveAll(directory)
+	_ = os.WriteFile(filepath.Join(directory, blockedName), []byte("unused-example-value\n"), 0o600)
+	_ = os.WriteFile(filepath.Join(directory, tokenName), []byte("disposable-example-credential\n"), 0o600)
+	report, bootstrapErr := configkit.LoadSecretsDir(directory)
+	var reportOutput bytes.Buffer
+	_, reportWriteErr := report.WriteTo(&reportOutput)
+
+	result, loadErr := consumers.LoadWeather(configkit.Bytes("weather.yml", []byte("units: metric\ntoken: "+tokenName+"\n")),
+		configkit.Override{Path: configkit.Keys("units"), Value: "us", Flag: "--units"})
+	var explanation bytes.Buffer
+	explainErr := result.WriteExplanation(&explanation, configkit.Keys("units"))
+	blocked, loaded := secretStatus(report, blockedName), secretStatus(report, tokenName)
+	value, present := os.LookupEnv(tokenName)
+	fmt.Printf("blocked=%s loaded=%s report=%t reference=%s explained=%t unchanged=%t errors=%t\n",
+		blocked, loaded, reportOutput.Len() > 0, result.Config.Token.EnvName(),
+		strings.Contains(explanation.String(), "--units"), present && value == "disposable-example-credential",
+		bootstrapErr != nil || reportWriteErr != nil || loadErr != nil || explainErr != nil)
+	// Output: blocked=skipped_existing loaded=loaded report=true reference=CONFIGKIT_WEATHER_EXAMPLE_TOKEN explained=true unchanged=true errors=false
+}
+
+func TestMaintainedConsumerFixturesPreserveDomainOutcomes(t *testing.T) {
+	narratio, err := consumers.LoadNarratio(fixture("narratio", "pipeline.yml"))
+	if err != nil || narratio.Config.Artifacts["transcript"].Output != "transcript.txt" ||
+		narratio.Config.ModelProfile != "concise" || len(narratio.Sources()) != 2 {
+		t.Fatalf("Narratio shape = %#v, %v", narratio, err)
+	}
+	if origin, ok := narratio.Metadata().Lookup(configkit.Keys("artifacts", "transcript", "output")); !ok || origin.Origin.Layer != configkit.LayerResolution {
+		t.Fatalf("artifact origin = %#v, %v", origin, ok)
+	}
+	overlaid, err := consumers.LoadNarratioOverlay(fixture("narratio", "pipeline.yml"), "testing")
+	if err != nil || overlaid.Config.PollInterval.String() != "2m0s" ||
+		overlaid.Config.ModelProfile != "concise" || len(overlaid.Sources()) != 3 {
+		t.Fatalf("configuration overlay and application model profile = %#v, %v", overlaid, err)
+	}
+	if source := overlaid.Sources()[2]; source.Label != "overlays/testing.yml" || source.Layer != configkit.LayerOverlay {
+		t.Fatalf("Narratio overlay source = %#v", source)
+	}
+
+	notarius, err := consumers.LoadNotarius(fixture("notarius", "config.yml"))
+	window, converted := consumers.NotariusWindow(notarius.Config, 0)
+	if err != nil || !converted || window != 12 {
+		t.Fatalf("Notarius shape = %#v, %v, %v", notarius, converted, err)
+	}
+	if _, ok := notarius.Config.Bindings[0].Options["window_units"].(int64); !ok {
+		t.Fatalf("dynamic integer type = %T", notarius.Config.Bindings[0].Options["window_units"])
+	}
+	integerNotarius, err := consumers.LoadNotarius(fixture("notarius", "integer-version.yml"))
+	if err != nil || integerNotarius.Config.Version != notarius.Config.Version || integerNotarius.Config.Version != "4" {
+		t.Fatalf("Notarius version forms = %#v / %#v, %v", notarius.Config, integerNotarius, err)
+	}
+
+	weather, err := consumers.LoadWeather(configkit.File(fixture("weather", "config.yml")))
+	if err != nil || weather.Config.Reports["daily"].Modules[1].Options.Sections[0] != "short_term" {
+		t.Fatalf("WeatherReporter shape = %#v, %v", weather, err)
+	}
+
+	speakers, err := consumers.LoadSpeakerRules(fixture("seriatim", "speakers.yml"))
+	if err != nil {
+		t.Fatal(err)
+	}
+	name, ok := consumers.SpeakerName(speakers.Config, "Host: introduction")
+	if !ok || name != "narrator" || speakers.Config.Rules[0].Prefix != "Host:" {
+		t.Fatalf("ordered speaker rules = %#v, %q, %v", speakers.Config.Rules, name, ok)
+	}
+}
+
+func TestMigrationFixturesFailWithStableCodesAndPaths(t *testing.T) {
+	tests := []struct {
+		name string
+		load func() error
+		code configkit.Code
+		path string
+	}{
+		{
+			name: "unsupported application version",
+			load: func() error {
+				_, err := consumers.LoadNotarius(fixture("notarius", "unsupported-version.yml"))
+				return err
+			},
+			code: configkit.CodeVersionError, path: "/version",
+		},
+		{
+			name: "non-integer numeric version",
+			load: func() error {
+				_, err := consumers.LoadNotarius(fixture("notarius", "noninteger-version.yml"))
+				return err
+			},
+			code: configkit.CodeVersionType, path: "/version",
+		},
+		{
+			name: "module shorthand",
+			load: func() error {
+				_, err := consumers.LoadWeather(configkit.File(fixture("weather", "shorthand-module.yml")))
+				return err
+			},
+			code: configkit.CodeDecodeType, path: "/reports/daily/modules/0",
+		},
+		{
+			name: "explicit empty modules",
+			load: func() error {
+				_, err := consumers.LoadWeather(configkit.File(fixture("weather", "empty-modules.yml")))
+				return err
+			},
+			code: configkit.CodeValidateError, path: "/reports/daily/modules",
+		},
+		{
+			name: "explicit empty path templates",
+			load: func() error {
+				_, err := consumers.LoadWeather(configkit.File(fixture("weather", "empty-paths.yml")))
+				return err
+			},
+			code: configkit.CodeValidateError, path: "/reports/daily/path_templates",
+		},
+		{
+			name: "explicit null required option",
+			load: func() error {
+				_, err := consumers.LoadWeather(configkit.File(fixture("weather", "null-window.yml")))
+				return err
+			},
+			code: configkit.CodeValidateError, path: "/reports/daily/modules/0/options/window_units",
+		},
+		{
+			name: "strict unknown rule field",
+			load: func() error {
+				_, err := consumers.LoadSpeakerRules(fixture("seriatim", "unknown-field.yml"))
+				return err
+			},
+			code: configkit.CodeDecodeUnknownField, path: "/rules/0/color",
+		},
+	}
+	for _, test := range tests {
+		t.Run(test.name, func(t *testing.T) {
+			var loadError *configkit.LoadError
+			if err := test.load(); !errors.As(err, &loadError) {
+				t.Fatalf("error = %T %v", err, err)
+			}
+			diagnostics := loadError.Diagnostics()
+			if len(diagnostics) == 0 || diagnostics[0].Code != test.code || diagnostics[0].Path.String() != test.path {
+				t.Fatalf("diagnostics = %#v", diagnostics)
+			}
+			if strings.Contains(diagnostics[0].Message, "wrong-before-overlay") {
+				t.Fatalf("diagnostic exposed raw parser input: %#v", diagnostics[0])
+			}
+		})
+	}
+}
+
+func TestWeatherLoadedAndConstructedRulesAgreeWithoutMutation(t *testing.T) {
+	loaded, err := consumers.LoadWeather(configkit.File(fixture("weather", "config.yml")))
+	if err != nil {
+		t.Fatal(err)
+	}
+	reconstructed, err := consumers.LoadConstructedWeather(loaded.Config)
+	if err != nil || !reflect.DeepEqual(reconstructed.Config, loaded.Config) {
+		t.Fatalf("loaded/constructed outcomes differ: %#v, %v", reconstructed, err)
+	}
+	constructed := consumers.WeatherConfig{Units: loaded.Config.Units, Reports: map[string]consumers.ReportConfig{}}
+	constructed.Reports["daily"] = consumers.ReportConfig{
+		Modules:       []consumers.ModuleSpec{{Module: "discussion", Options: consumers.ModuleOptions{Sections: []string{" short_term "}}}},
+		PathTemplates: []string{"daily/{date}.md"},
+	}
+	wantInput := constructed.Reports["daily"].Modules[0].Options.Sections[0]
+	result, err := consumers.LoadConstructedWeather(constructed)
+	if err != nil {
+		t.Fatal(err)
+	}
+	if got := constructed.Reports["daily"].Modules[0].Options.Sections[0]; got != wantInput {
+		t.Fatalf("constructed options mutated from %q to %q", wantInput, got)
+	}
+	if result.Config.Reports["daily"].Modules[0].Options.Sections[0] != "short_term" {
+		t.Fatalf("normalized result = %#v", result.Config.Reports["daily"])
+	}
+
+	empty := consumers.WeatherConfig{Units: "metric", Reports: map[string]consumers.ReportConfig{
+		"daily": {Modules: []consumers.ModuleSpec{}},
+	}}
+	_, err = consumers.LoadConstructedWeather(empty)
+	var loadError *configkit.LoadError
+	if !errors.As(err, &loadError) || loadError.Diagnostics()[0].Code != configkit.CodeValidateError {
+		t.Fatalf("constructed empty modules error = %v", err)
+	}
+	if !reflect.DeepEqual(empty.Reports["daily"].Modules, []consumers.ModuleSpec{}) {
+		t.Fatal("constructed empty module input was mutated")
+	}
+}
+
+func TestNotariusPathExampleUsesEntryProvenance(t *testing.T) {
+	main := fixture("notarius-paths", "main.yml")
+	declared := fixture("notarius-paths", "declarations", "path.yml")
+	declaredCanonical := canonicalFixture(t, declared)
+	wantImported := filepath.Join(filepath.Dir(declaredCanonical), "..", "assets", "imported.txt")
+	result, err := consumers.LoadNotariusPaths(main, filepath.Join(t.TempDir(), "invocation"))
+	if err != nil || result.Config.Reference != wantImported {
+		t.Fatalf("imported reference = %#v, %v", result, err)
+	}
+	var effective bytes.Buffer
+	if err := result.WriteEffective(&effective); err != nil || !strings.Contains(effective.String(), wantImported) ||
+		strings.Contains(effective.String(), "PATH_REFERENCE_SECRET_CANARY") {
+		t.Fatalf("effective output = %q, %v", effective.String(), err)
+	}
+	explanation, found := result.Explain(configkit.Keys("reference"))
+	if !found || len(explanation.History) == 0 || explanation.History[len(explanation.History)-1].Before.YAML != "../assets/imported.txt\n" ||
+		len(explanation.History[len(explanation.History)-1].Reasons) != 1 || explanation.History[len(explanation.History)-1].Reasons[0] != "resolved relative reference from entry source" {
+		t.Fatalf("reference explanation = %#v, %v", explanation, found)
+	}
+	sensitive, found := result.Explain(configkit.Keys("sensitive"))
+	var rendered bytes.Buffer
+	writeErr := result.WriteExplanation(&rendered, configkit.Keys("sensitive"))
+	if !found || !sensitive.Effective.Redacted || writeErr != nil ||
+		strings.Contains(fmt.Sprintf("%#v %s", sensitive, rendered.String()), "PATH_REFERENCE_SECRET_CANARY") {
+		t.Fatalf("sensitive inspection = %#v, %q, %v", sensitive, rendered.String(), writeErr)
+	}
+
+	defaults := fixture("notarius-paths", "defaults.yml")
+	defaultCanonical := canonicalFixture(t, defaults)
+	defaultResult, err := consumers.LoadNotariusPaths(defaults, filepath.Join(t.TempDir(), "invocation"))
+	wantDefault := filepath.Join(filepath.Dir(defaultCanonical), "defaults", "reference.txt")
+	if err != nil || defaultResult.Config.Reference != wantDefault {
+		t.Fatalf("default reference = %#v, %v", defaultResult, err)
+	}
+
+	invocation := filepath.Join(t.TempDir(), "caller")
+	cliResult, err := consumers.LoadNotariusPaths(main, invocation,
+		configkit.Override{Path: configkit.Keys("reference"), Value: "cli/reference.txt", Flag: "--reference"})
+	wantCLI := filepath.Join(invocation, "cli", "reference.txt")
+	if err != nil || cliResult.Config.Reference != wantCLI {
+		t.Fatalf("CLI reference = %#v, %v", cliResult, err)
+	}
+	missingBase, err := consumers.LoadNotariusPaths(main, "",
+		configkit.Override{Path: configkit.Keys("reference"), Value: "cli/reference.txt", Flag: "--reference"})
+	if err != nil || missingBase.Config.Reference != "cli/reference.txt" || len(missingBase.Diagnostics()) != 1 ||
+		missingBase.Diagnostics()[0].Code != configkit.CodeResolveWarning {
+		t.Fatalf("missing CLI base = %#v, %v", missingBase, err)
+	}
+	absolute := filepath.Join(t.TempDir(), "absolute.txt")
+	absoluteResult, err := consumers.LoadNotariusPaths(main, invocation,
+		configkit.Override{Path: configkit.Keys("reference"), Value: absolute, Flag: "--reference"})
+	if err != nil || absoluteResult.Config.Reference != absolute {
+		t.Fatalf("absolute reference = %#v, %v", absoluteResult, err)
+	}
+
+	target := fixture("notarius-paths", "symlink-target.yml")
+	link := filepath.Join(t.TempDir(), "linked-config.yml")
+	if err := os.Symlink(target, link); err != nil {
+		t.Skipf("symlink fixture unavailable: %v", err)
+	}
+	symlinkResult, err := consumers.LoadNotariusPaths(link, invocation)
+	targetCanonical := canonicalFixture(t, target)
+	wantSymlink := filepath.Join(filepath.Dir(targetCanonical), "..", "assets", "target.txt")
+	if err != nil || symlinkResult.Config.Reference != wantSymlink {
+		t.Fatalf("symlink reference = %#v, %v", symlinkResult, err)
+	}
+}
+
+func fixture(parts ...string) string {
+	_, file, _, _ := runtime.Caller(0)
+	values := append([]string{filepath.Dir(file), "testdata"}, parts...)
+	return filepath.Join(values...)
+}
+
+func canonicalFixture(t *testing.T, path string) string {
+	t.Helper()
+	canonical, err := filepath.EvalSymlinks(path)
+	if err != nil {
+		t.Fatal(err)
+	}
+	return canonical
+}
+
+func preserveEnvironment(name string) func() {
+	value, present := os.LookupEnv(name)
+	return func() {
+		if present {
+			_ = os.Setenv(name, value)
+		} else {
+			_ = os.Unsetenv(name)
+		}
+	}
+}
+
+func secretStatus(report *configkit.SecretsReport, name string) configkit.SecretFileStatus {
+	for _, entry := range report.Entries() {
+		if entry.Name == name {
+			return entry.Status
+		}
+	}
+	return "missing"
+}

examples/consumers/inheritance.go

@@ -0,0 +1,20 @@
+package consumers
+
+import configkit "gitea.maximumdirect.net/eric/ConfigKit"
+
+// PresetCatalog is ordinary application data; no inheritance fields or
+// registration hooks are required in the typed configuration.
+type PresetCatalog struct {
+	Presets map[string]Preset `yaml:"presets"`
+}
+
+type Preset struct {
+	Enabled  bool                      `yaml:"enabled"`
+	Settings map[string]map[string]int `yaml:"settings"`
+}
+
+// LoadPresets performs one load; callers may inspect inherited presence and
+// source origins on the returned result before choosing a preset to execute.
+func LoadPresets(source configkit.Source) (*configkit.Result[PresetCatalog], error) {
+	return configkit.Load[PresetCatalog](source)
+}

examples/consumers/inheritance_test.go

@@ -0,0 +1,35 @@
+package consumers_test
+
+import (
+	"testing"
+
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+	"gitea.maximumdirect.net/eric/ConfigKit/examples/consumers"
+)
+
+func TestPresetCatalogOneLoadAndDerivation(t *testing.T) {
+	result, err := consumers.LoadPresets(configkit.File(fixture("inheritance", "presets.yml")))
+	if err != nil {
+		t.Fatal(err)
+	}
+	if result.Config.Presets["base"].Settings["secondary"]["width"] != 10 ||
+		result.Config.Presets["custom"].Settings["secondary"]["width"] != 20 ||
+		result.Config.Presets["custom"].Enabled {
+		t.Fatalf("expanded presets = %#v", result.Config.Presets)
+	}
+	enabled := configkit.Keys("presets", "custom", "enabled")
+	if !result.Metadata().IsExplicit(enabled) {
+		t.Fatal("inherited false lost explicit presence")
+	}
+	info, found := result.Metadata().Lookup(enabled)
+	if !found || info.Origin.Locations[0].SourceID != "source-1" ||
+		len(info.Origin.Inheritance) != 1 || info.Origin.Inheritance[0].From.String() != "/presets/base/enabled" {
+		t.Fatalf("origin and derivation = %#v, %v", info, found)
+	}
+	nested := configkit.Keys("presets", "custom", "settings", "secondary", "width")
+	info, found = result.Metadata().Lookup(nested)
+	if !found || len(info.Origin.Inheritance) != 1 ||
+		info.Origin.Inheritance[0].From.String() != "/presets/custom/settings/primary/width" {
+		t.Fatalf("destination-local derivation = %#v, %v", info, found)
+	}
+}

examples/consumers/layered.go

@@ -0,0 +1,95 @@
+package consumers
+
+import (
+	"embed"
+	"errors"
+	"io/fs"
+	"path"
+
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+)
+
+//go:embed testdata/native-source testdata/layered-bundle
+var bundledFiles embed.FS
+
+// BundledConfig is a small configuration loaded directly from an embedded file.
+type BundledConfig struct {
+	Name    string `yaml:"name"`
+	Enabled bool   `yaml:"enabled"`
+}
+
+// LoadBundled demonstrates a native filesystem source without layered options.
+func LoadBundled() (*configkit.Result[BundledConfig], error) {
+	files, err := fs.Sub(bundledFiles, "testdata/native-source")
+	if err != nil {
+		return nil, err
+	}
+	return configkit.Load[BundledConfig](configkit.NewFilesystem("bundled", files).File("config.yml"))
+}
+
+// CatalogConfig keeps resource names and domain rules in the application.
+type CatalogConfig struct {
+	Mode      string            `yaml:"mode"`
+	Enabled   bool              `yaml:"enabled"`
+	Workers   int               `yaml:"workers"`
+	Templates map[string]string `yaml:"templates"`
+	Labels    map[string]string `yaml:"labels"`
+}
+
+// LoadCatalog combines two underlay tiers beneath an independently located
+// host main file. ConfigKit assembles and validates the complete result once.
+func LoadCatalog(mainPath string) (*configkit.Result[CatalogConfig], error) {
+	files, err := fs.Sub(bundledFiles, "testdata/layered-bundle")
+	if err != nil {
+		return nil, err
+	}
+	bundle := configkit.NewFilesystem("catalog bundle", files)
+	return configkit.LoadLayered(configkit.Input{Source: configkit.File(mainPath)},
+		configkit.LayeredOptions[CatalogConfig]{
+			Underlays: []configkit.Underlay{
+				{Inputs: []configkit.Input{{Source: bundle.File("defaults/config.yml"), Imports: true}}},
+				{Inputs: []configkit.Input{{Source: configkit.Mapping("local policy", map[string]any{
+					"workers": 2,
+					"labels":  map[string]any{"tenant": "example"},
+				})}}},
+			},
+			Definition: configkit.Definition[CatalogConfig]{
+				Defaults: func() CatalogConfig { return CatalogConfig{Mode: "demo"} },
+				Validate: validateCatalog,
+			},
+		})
+}
+
+func validateCatalog(configuration *CatalogConfig, validation *configkit.Validation) {
+	if configuration.Mode != "demo" && configuration.Mode != "production" {
+		validation.Error(configkit.Keys("mode"), "must be demo or production")
+	}
+	if configuration.Workers < 0 {
+		validation.Error(configkit.Keys("workers"), "must be nonnegative")
+	}
+	if name := configuration.Templates["welcome"]; name == "." || !fs.ValidPath(name) {
+		validation.Error(configkit.Keys("templates", "welcome"), "must be a relative resource name")
+	}
+}
+
+// ReadWelcome follows the effective template field's one declaring source to
+// its retained resource context. Opening and interpreting the resource remain
+// application work; this does not reopen configuration or change metadata.
+func ReadWelcome(result *configkit.Result[CatalogConfig]) (string, error) {
+	if result == nil {
+		return "", errors.New("catalog result is nil")
+	}
+	info, found := result.Metadata().Lookup(configkit.Keys("templates", "welcome"))
+	if !found || len(info.Origin.Locations) != 1 {
+		return "", errors.New("welcome template has no single declaring source")
+	}
+	context, found := result.SourceContext(info.Origin.Locations[0].SourceID)
+	if !found {
+		return "", errors.New("welcome template has no resource context")
+	}
+	data, err := fs.ReadFile(context.FS, path.Join(context.BaseDir, result.Config.Templates["welcome"]))
+	if err != nil {
+		return "", err
+	}
+	return string(data), nil
+}

examples/consumers/layered_test.go

@@ -0,0 +1,71 @@
+package consumers_test
+
+import (
+	"errors"
+	"fmt"
+	"strings"
+	"testing"
+
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+	"gitea.maximumdirect.net/eric/ConfigKit/examples/consumers"
+)
+
+func Example_nativeFilesystem() {
+	result, err := consumers.LoadBundled()
+	if err != nil {
+		fmt.Println(err)
+		return
+	}
+	fmt.Println(result.Config.Name, result.Config.Enabled)
+	// Output: embedded false
+}
+
+func Example_layeredCatalog() {
+	result, err := consumers.LoadCatalog(fixture("layered-main", "config.yml"))
+	if err != nil {
+		fmt.Println(err)
+		return
+	}
+	welcome, err := consumers.ReadWelcome(result)
+	fmt.Println(result.Config.Mode, result.Config.Enabled, result.Config.Workers,
+		result.Config.Labels["origin"], result.Config.Labels["tenant"], strings.TrimSpace(welcome), err)
+	// Output: production false 0 bundle example Welcome from the bundle. <nil>
+}
+
+func TestCatalogRetainsPresenceAndSourceContext(t *testing.T) {
+	result, err := consumers.LoadCatalog(fixture("layered-main", "config.yml"))
+	if err != nil {
+		t.Fatal(err)
+	}
+	for _, key := range []string{"enabled", "workers"} {
+		info, found := result.Metadata().Lookup(configkit.Keys(key))
+		if !found || !info.Explicit || info.Origin.Layer != configkit.LayerBase {
+			t.Fatalf("%s presence = %#v, %v", key, info, found)
+		}
+	}
+	info, found := result.Metadata().Lookup(configkit.Keys("templates", "welcome"))
+	if !found || info.Origin.Layer != configkit.LayerUnderlay || len(info.Origin.Locations) != 1 {
+		t.Fatalf("welcome origin = %#v, %v", info, found)
+	}
+	context, found := result.SourceContext(info.Origin.Locations[0].SourceID)
+	if !found || context.BaseDir != "defaults" {
+		t.Fatalf("welcome context = %#v, %v", context, found)
+	}
+	welcome, err := consumers.ReadWelcome(result)
+	if err != nil || strings.TrimSpace(welcome) != "Welcome from the bundle." {
+		t.Fatalf("welcome = %q, %v", welcome, err)
+	}
+	if result.Config.Labels["tenant"] != "example" || result.Config.Labels["origin"] != "bundle" {
+		t.Fatalf("recursive underlay labels = %#v", result.Config.Labels)
+	}
+}
+
+func TestCatalogValidationRejectsInvalidMode(t *testing.T) {
+	_, err := consumers.LoadCatalog(fixture("layered-main", "invalid.yml"))
+	var loadError *configkit.LoadError
+	if !errors.As(err, &loadError) || len(loadError.Diagnostics()) == 0 ||
+		loadError.Diagnostics()[0].Code != configkit.CodeValidateError ||
+		loadError.Diagnostics()[0].Path.String() != "/mode" {
+		t.Fatalf("invalid mode error = %v", err)
+	}
+}

examples/consumers/testdata/inheritance/presets.yml

@@ -0,0 +1,10 @@
+presets:
+  base:
+    enabled: false
+    settings:
+      primary: {width: 10}
+      secondary: {extends: primary}
+  custom:
+    extends: base
+    settings:
+      primary: {width: 20}

examples/consumers/testdata/layered-bundle/defaults/config.yml

@@ -0,0 +1,7 @@
+configkit:
+  imports:
+    - path: ../shared.yml
+enabled: true
+workers: 4
+templates:
+  welcome: messages/welcome.txt

examples/consumers/testdata/layered-bundle/defaults/messages/welcome.txt

@@ -0,0 +1 @@
+Welcome from the bundle.

examples/consumers/testdata/layered-bundle/shared.yml

@@ -0,0 +1,2 @@
+labels:
+  origin: bundle

examples/consumers/testdata/layered-main/config.yml

@@ -0,0 +1,3 @@
+mode: production
+enabled: false
+workers: 0

examples/consumers/testdata/layered-main/invalid.yml

@@ -0,0 +1 @@
+mode: unsupported

examples/consumers/testdata/narratio/artifacts.yml

@@ -0,0 +1,3 @@
+artifacts:
+  transcript:
+    output: ' transcript.txt '

examples/consumers/testdata/narratio/overlays/testing.yml

@@ -0,0 +1 @@
+poll_interval: 2m

examples/consumers/testdata/narratio/pipeline.yml

@@ -0,0 +1,5 @@
+configkit:
+  imports:
+    - path: artifacts.yml
+poll_interval: 1m
+model_profile: concise

examples/consumers/testdata/native-source/config.yml

@@ -0,0 +1,2 @@
+name: embedded
+enabled: false

examples/consumers/testdata/notarius-paths/declarations/path.yml

@@ -0,0 +1 @@
+reference: ../assets/imported.txt

examples/consumers/testdata/notarius-paths/defaults.yml

@@ -0,0 +1 @@
+sensitive: PATH_REFERENCE_SECRET_CANARY

examples/consumers/testdata/notarius-paths/main.yml

@@ -0,0 +1,4 @@
+configkit:
+  imports:
+    - path: declarations/path.yml
+sensitive: PATH_REFERENCE_SECRET_CANARY

examples/consumers/testdata/notarius-paths/symlink-target.yml

@@ -0,0 +1,2 @@
+reference: ../assets/target.txt
+sensitive: PATH_REFERENCE_SECRET_CANARY

examples/consumers/testdata/notarius/config.yml

@@ -0,0 +1,6 @@
+version: "4"
+bindings:
+  - object: summary
+    options:
+      window_units: 12
+      format: markdown

examples/consumers/testdata/notarius/integer-version.yml

@@ -0,0 +1,6 @@
+version: 4
+bindings:
+  - object: summary
+    options:
+      window_units: 12
+      format: markdown

examples/consumers/testdata/notarius/noninteger-version.yml

@@ -0,0 +1,2 @@
+version: 4.0
+bindings: []

examples/consumers/testdata/notarius/unsupported-version.yml

@@ -0,0 +1,2 @@
+version: 5
+bindings: []

examples/consumers/testdata/seriatim/autocorrect.yml

@@ -0,0 +1,5 @@
+rules:
+  - find: teh
+    replace: the
+  - find: occured
+    replace: occurred

examples/consumers/testdata/seriatim/speakers.yml

@@ -0,0 +1,5 @@
+rules:
+  - prefix: 'Host:'
+    name: narrator
+  - prefix: 'Guest:'
+    name: visitor

examples/consumers/testdata/seriatim/unknown-field.yml

@@ -0,0 +1,4 @@
+rules:
+  - prefix: 'Host:'
+    name: narrator
+    color: blue

examples/consumers/testdata/weather/config.yml

@@ -0,0 +1,11 @@
+units: us
+reports:
+  daily:
+    modules:
+      - module: chunker
+        options:
+          window_units: 12
+      - module: discussion
+        options:
+          sections: [' short_term ']
+    path_templates: ['daily/{date}.md']

examples/consumers/testdata/weather/empty-modules.yml

@@ -0,0 +1,3 @@
+reports:
+  daily:
+    modules: []

examples/consumers/testdata/weather/empty-paths.yml

@@ -0,0 +1,3 @@
+reports:
+  daily:
+    path_templates: []

examples/consumers/testdata/weather/null-window.yml

@@ -0,0 +1,6 @@
+reports:
+  daily:
+    modules:
+      - module: chunker
+        options:
+          window_units: null

examples/consumers/testdata/weather/shorthand-module.yml

@@ -0,0 +1,3 @@
+reports:
+  daily:
+    modules: [chunker]

facade_candidate_test.go

@@ -0,0 +1,275 @@
+package configkit_test
+
+import (
+	"bytes"
+	"encoding/json"
+	"errors"
+	"fmt"
+	"io"
+	"os"
+	"reflect"
+	"strings"
+	"testing"
+
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+)
+
+var (
+	_ error          = (*configkit.LoadError)(nil)
+	_ fmt.Formatter  = configkit.Secret{}
+	_ fmt.Stringer   = configkit.Path{}
+	_ json.Marshaler = configkit.Secret{}
+)
+
+func TestFacadeValuesRemainRootOwned(t *testing.T) {
+	t.Parallel()
+	const packagePath = "gitea.maximumdirect.net/eric/ConfigKit"
+	for _, candidate := range []reflect.Type{
+		reflect.TypeFor[configkit.Path](), reflect.TypeFor[configkit.Source](),
+		reflect.TypeFor[configkit.Secret](), reflect.TypeFor[configkit.Diagnostic](),
+		reflect.TypeFor[configkit.LoadError](), reflect.TypeFor[configkit.Metadata](),
+		reflect.TypeFor[configkit.Resolution](), reflect.TypeFor[configkit.Validation](),
+		reflect.TypeFor[configkit.Version](), reflect.TypeFor[configkit.VersionRule](),
+		reflect.TypeFor[configkit.FilesystemContext](), reflect.TypeFor[configkit.Override](),
+		reflect.TypeFor[configkit.Filesystem](), reflect.TypeFor[configkit.ResourceContext](),
+		reflect.TypeFor[configkit.Input](), reflect.TypeFor[configkit.Underlay](),
+		reflect.TypeFor[configkit.LayeredOptions[struct{}]](),
+		reflect.TypeFor[configkit.Definition[struct{}]](), reflect.TypeFor[configkit.Options[struct{}]](),
+		reflect.TypeFor[configkit.Result[struct{}]](),
+		reflect.TypeFor[configkit.ValueSnapshot](), reflect.TypeFor[configkit.ValueChange](),
+		reflect.TypeFor[configkit.SecretReferenceInfo](), reflect.TypeFor[configkit.Explanation](),
+		reflect.TypeFor[configkit.SecretFileResult](), reflect.TypeFor[configkit.SecretsReport](),
+		reflect.TypeFor[configkit.SecretsError](),
+	} {
+		if candidate.PkgPath() != packagePath {
+			t.Fatalf("type %s belongs to %q", candidate, candidate.PkgPath())
+		}
+	}
+	secret := configkit.SecretEnv("SAFE_NAME")
+	formatted := fmt.Sprintf("%#v", secret)
+	encoded, err := json.Marshal(secret)
+	if formatted == "" || err != nil || string(encoded) != `"SAFE_NAME"` {
+		t.Fatalf("secret rendering = %q, %s, %v", formatted, encoded, err)
+	}
+	if got := configkit.Keys("a/b~").Index(0).String(); got != "/a~1b~0/0" {
+		t.Fatalf("path = %q", got)
+	}
+	if got := (&configkit.LoadError{}).Error(); got != "configkit: configuration load failed" {
+		t.Fatalf("zero LoadError = %q", got)
+	}
+}
+
+func TestFacadeInspectionUsesFrozenState(t *testing.T) {
+	t.Setenv("FACADE_INSPECTION_SECRET", "credential")
+
+	type configuration struct {
+		Value  string           `yaml:"value"`
+		Secret configkit.Secret `yaml:"secret"`
+	}
+	result, err := configkit.Load[configuration](configkit.Bytes("inspection.yml", []byte("value: original\nsecret: FACADE_INSPECTION_SECRET\n")))
+	if err != nil {
+		t.Fatal(err)
+	}
+	if !result.Config.Secret.IsResolved() || result.Config.Secret.Value() != "credential" {
+		t.Fatalf("secret = %#v", result.Config.Secret)
+	}
+	explanation, ok := result.Explain(configkit.Keys("value"))
+	if !ok || explanation.Effective.YAML != "original\n" {
+		t.Fatalf("explanation = %#v, %v", explanation, ok)
+	}
+	explanation.Effective.YAML = "mutated\n"
+	result.Config.Value = "mutated"
+	var effective bytes.Buffer
+	if err := result.WriteEffective(&effective); err != nil || !strings.Contains(effective.String(), "value: original\n") || strings.Contains(effective.String(), "credential") {
+		t.Fatalf("effective = %q, %v", effective.String(), err)
+	}
+	again, ok := result.Explain(configkit.Keys("value"))
+	if !ok || again.Effective.YAML != "original\n" {
+		t.Fatalf("inspection changed = %#v, %v", again, ok)
+	}
+	secret, ok := result.Explain(configkit.Keys("secret"))
+	if !ok || secret.SecretReference == nil || secret.SecretReference.Name != "FACADE_INSPECTION_SECRET" {
+		t.Fatalf("secret explanation = %#v, %v", secret, ok)
+	}
+	var explanationOutput bytes.Buffer
+	if err := result.WriteExplanation(&explanationOutput, configkit.Keys("value")); err != nil || !strings.Contains(explanationOutput.String(), `path: "/value"`) {
+		t.Fatalf("explanation output = %q, %v", explanationOutput.String(), err)
+	}
+
+	unknown := bytes.NewBufferString("unchanged")
+	if err := result.WriteExplanation(unknown, configkit.Keys("unknown")); err == nil || unknown.String() != "unchanged" {
+		t.Fatalf("unknown explanation = %q, %v", unknown.String(), err)
+	}
+	var nilResult *configkit.Result[configuration]
+	if _, ok := nilResult.Explain(configkit.Keys("value")); ok {
+		t.Fatal("nil result explained a path")
+	}
+	if err := nilResult.WriteEffective(io.Discard); err == nil {
+		t.Fatal("nil result rendered effective configuration")
+	}
+}
+
+func TestFacadeSecretsBootstrapUsesFacadeRecords(t *testing.T) {
+	const (
+		loadedName   = "FACADE_BOOTSTRAP_LOADED"
+		existingName = "FACADE_BOOTSTRAP_EXISTING"
+	)
+	restore := func(name string) {
+		value, present := os.LookupEnv(name)
+		t.Cleanup(func() {
+			if present {
+				_ = os.Setenv(name, value)
+			} else {
+				_ = os.Unsetenv(name)
+			}
+		})
+	}
+	restore(loadedName)
+	restore(existingName)
+	if err := os.Unsetenv(loadedName); err != nil {
+		t.Fatal(err)
+	}
+	if err := os.Setenv(existingName, ""); err != nil {
+		t.Fatal(err)
+	}
+	directory := t.TempDir()
+	if err := os.WriteFile(directory+"/"+loadedName, []byte("bootstrap\n"), 0o600); err != nil {
+		t.Fatal(err)
+	}
+	if err := os.WriteFile(directory+"/"+existingName, []byte("ignored\n"), 0o600); err != nil {
+		t.Fatal(err)
+	}
+
+	report, err := configkit.LoadSecretsDir(directory)
+	if err != nil {
+		t.Fatal(err)
+	}
+	entries := report.Entries()
+	if len(entries) != 2 || os.Getenv(loadedName) != "bootstrap" {
+		t.Fatalf("entries/environment = %#v / %q", entries, os.Getenv(loadedName))
+	}
+	status := map[string]configkit.SecretFileResult{}
+	for _, entry := range entries {
+		status[entry.Name] = entry
+	}
+	if status[loadedName].Status != configkit.SecretFileLoaded || status[existingName].Status != configkit.SecretFileSkippedExisting || !status[existingName].ExistingEmpty {
+		t.Fatalf("statuses = %#v", status)
+	}
+	entries[0].Name = "mutated"
+	if report.Entries()[0].Name == "mutated" {
+		t.Fatal("report entries share mutable state")
+	}
+	var rendered bytes.Buffer
+	if _, err := report.WriteTo(&rendered); err != nil || strings.Contains(rendered.String(), "bootstrap") || strings.Contains(rendered.String(), "ignored") {
+		t.Fatalf("report rendering = %q, %v", rendered.String(), err)
+	}
+
+	failedReport, err := configkit.LoadSecretsDir("")
+	var secretsError *configkit.SecretsError
+	if failedReport == nil || !errors.As(err, &secretsError) || len(secretsError.Diagnostics()) != 1 || secretsError.Diagnostics()[0].Code != configkit.CodeSecretsInvalidPath {
+		t.Fatalf("bootstrap failure = %#v / %#v", failedReport, err)
+	}
+}
+
+func TestFacadeLoadBridgesLifecycleCallbacks(t *testing.T) {
+	t.Setenv("FACADE_SECRET_NAME", "credential")
+
+	type configuration struct {
+		Version string            `yaml:"version"`
+		Input   int               `yaml:"input"`
+		Derived int               `yaml:"derived"`
+		Secret  configkit.Secret  `yaml:"secret"`
+		Labels  map[string]string `yaml:"labels"`
+	}
+	var retainedResolution *configkit.Resolution
+	var retainedValidation *configkit.Validation
+	versionCalls, defaultsCalls, resolveCalls, validateCalls := 0, 0, 0, 0
+	definition := configkit.Definition[configuration]{
+		Version: &configkit.VersionRule{Path: configkit.Keys("version"), Check: func(version configkit.Version, validation *configkit.Validation) error {
+			versionCalls++
+			retainedValidation = validation
+			if !version.Present || version.Text != "1" {
+				validation.Error(configkit.Keys("version"), "unsupported version")
+			}
+			return nil
+		}},
+		Defaults: func() configuration {
+			defaultsCalls++
+			return configuration{Derived: 1, Labels: map[string]string{"default": "kept"}}
+		},
+		Resolve: func(configuration *configuration, resolution *configkit.Resolution) error {
+			resolveCalls++
+			retainedResolution = resolution
+			if !resolution.IsExplicit(configkit.Keys("input")) {
+				resolution.Error(configkit.Keys("input"), "input is required")
+			}
+			input, ok := resolution.InputInfo(configkit.Keys("input"))
+			if !ok || !input.Explicit {
+				resolution.Error(configkit.Keys("input"), "missing input provenance")
+			}
+			source, ok := resolution.Source("source-1")
+			if !ok || source.Label != "facade.yml" {
+				resolution.Error(configkit.Keys("input"), "missing source")
+			}
+			configkit.Default(resolution, configkit.Keys("derived"), &configuration.Derived, configuration.Input*2, "derived from input", configkit.Keys("input"))
+			return nil
+		},
+		Validate: func(configuration *configuration, validation *configkit.Validation) {
+			validateCalls++
+			retainedValidation = validation
+			if !configuration.Secret.IsResolved() || configuration.Secret.Value() != "credential" {
+				validation.Error(configkit.Keys("secret"), "secret did not resolve")
+			}
+		},
+	}
+	if versionCalls != 0 || defaultsCalls != 0 || resolveCalls != 0 || validateCalls != 0 {
+		t.Fatal("callbacks ran while constructing options")
+	}
+
+	result, err := configkit.Load(configkit.Bytes("facade.yml", []byte("version: 1\ninput: 3\nsecret: FACADE_SECRET_NAME\n")), configkit.Options[configuration]{Definition: definition})
+	if err != nil {
+		t.Fatal(err)
+	}
+	if versionCalls != 1 || defaultsCalls != 1 || resolveCalls != 1 || validateCalls != 1 || result.Config.Derived != 6 {
+		t.Fatalf("callback counts/configuration = %d/%d/%d/%d %#v", versionCalls, defaultsCalls, resolveCalls, validateCalls, result.Config)
+	}
+	derived, ok := result.Metadata().Lookup(configkit.Keys("derived"))
+	if !ok || derived.Explicit || derived.Origin.Operation != configkit.ChangeDerivedDefault {
+		t.Fatalf("derived metadata = %#v, %v", derived, ok)
+	}
+	if sources := result.Sources(); len(sources) != 1 || sources[0].Label != "facade.yml" {
+		t.Fatalf("sources = %#v", sources)
+	}
+	if result.Diagnostics() != nil {
+		t.Fatalf("diagnostics = %#v", result.Diagnostics())
+	}
+	for _, context := range []func(){
+		func() { retainedResolution.IsExplicit(configkit.Keys("input")) },
+		func() { retainedValidation.Warning(configkit.Keys("input"), "too late") },
+	} {
+		func() {
+			defer func() {
+				if recover() == nil {
+					t.Fatal("retained callback context remained active")
+				}
+			}()
+			context()
+		}()
+	}
+}
+
+func TestFacadeLoadReturnsFacadeLoadError(t *testing.T) {
+	t.Parallel()
+
+	type configuration struct {
+		Value int `yaml:"value"`
+	}
+	result, err := configkit.Load[configuration](configkit.Bytes("invalid.yml", []byte("value: wrong\n")))
+	if result != nil || err == nil {
+		t.Fatalf("result, err = %#v, %v", result, err)
+	}
+	var loadError *configkit.LoadError
+	if !errors.As(err, &loadError) || len(loadError.Diagnostics()) != 1 || loadError.Diagnostics()[0].Code != configkit.CodeDecodeType {
+		t.Fatalf("facade error = %#v", err)
+	}
+}

facade_compatibility_test.go

@@ -0,0 +1,85 @@
+package configkit_test
+
+import (
+	"encoding/json"
+	"errors"
+	"fmt"
+	"io"
+	"reflect"
+	"testing"
+
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+)
+
+var (
+	_ error          = (*configkit.LoadError)(nil)
+	_ fmt.Formatter  = configkit.Secret{}
+	_ fmt.Stringer   = configkit.Path{}
+	_ json.Marshaler = configkit.Secret{}
+	_ io.WriterTo    = (*configkit.SecretsReport)(nil)
+)
+
+type facadeCompatibilityConfig struct {
+	Value   string `yaml:"value"`
+	Derived string `yaml:"derived"`
+}
+
+func TestFacadeCompatibility(t *testing.T) {
+	t.Parallel()
+
+	const packagePath = "gitea.maximumdirect.net/eric/ConfigKit"
+	for _, candidate := range []struct {
+		name  string
+		type_ reflect.Type
+	}{
+		{"Path", reflect.TypeFor[configkit.Path]()},
+		{"Source", reflect.TypeFor[configkit.Source]()},
+		{"Secret", reflect.TypeFor[configkit.Secret]()},
+		{"Definition", reflect.TypeFor[configkit.Definition[facadeCompatibilityConfig]]()},
+		{"Options", reflect.TypeFor[configkit.Options[facadeCompatibilityConfig]]()},
+		{"Result", reflect.TypeFor[configkit.Result[facadeCompatibilityConfig]]()},
+	} {
+		if candidate.type_.PkgPath() != packagePath {
+			t.Errorf("%s belongs to %q, want %q", candidate.name, candidate.type_.PkgPath(), packagePath)
+		}
+	}
+
+	constructed := configkit.Options[facadeCompatibilityConfig]{
+		Definition: configkit.Definition[facadeCompatibilityConfig]{},
+		Filesystem: &configkit.FilesystemContext{BaseDir: "configs", Root: "configs"},
+		Overrides: []configkit.Override{{
+			Path:  configkit.Keys("value"),
+			Value: "override",
+			Flag:  "--value",
+		}},
+	}
+	if got := constructed.Overrides[0].Path.String(); got != "/value" {
+		t.Fatalf("constructed override path = %q, want /value", got)
+	}
+	publicResult := configkit.Result[facadeCompatibilityConfig]{Config: facadeCompatibilityConfig{Value: "constructed"}}
+	if publicResult.Config.Value != "constructed" {
+		t.Fatal("constructed result lost its public configuration")
+	}
+
+	result, err := configkit.Load(configkit.Bytes("facade.yml", []byte("value: input\n")), configkit.Options[facadeCompatibilityConfig]{
+		Definition: configkit.Definition[facadeCompatibilityConfig]{
+			Resolve: func(configuration *facadeCompatibilityConfig, resolution *configkit.Resolution) error {
+				configkit.Default(resolution, configkit.Keys("derived"), &configuration.Derived, configuration.Value+" default", "derive value")
+				configkit.Normalize(resolution, configkit.Keys("value"), &configuration.Value, "normalized "+configuration.Value, "normalize value")
+				return nil
+			},
+		},
+	})
+	if err != nil {
+		t.Fatalf("Load() error = %v", err)
+	}
+	if result.Config != (facadeCompatibilityConfig{Value: "normalized input", Derived: "input default"}) {
+		t.Fatalf("Load() Config = %#v", result.Config)
+	}
+
+	_, err = configkit.Load[facadeCompatibilityConfig](configkit.Bytes("invalid.yml", []byte("value: [\n")))
+	var loadError *configkit.LoadError
+	if !errors.As(err, &loadError) {
+		t.Fatalf("Load() error = %T, want *configkit.LoadError", err)
+	}
+}

facade_context_test.go

@@ -0,0 +1,52 @@
+package configkit_test
+
+import (
+	"testing"
+
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+)
+
+func TestFacadeInactiveContextsPreserveClosedFailure(t *testing.T) {
+	t.Parallel()
+	for _, state := range []struct {
+		name       string
+		resolution *configkit.Resolution
+		validation *configkit.Validation
+	}{
+		{name: "nil"},
+		{name: "zero", resolution: &configkit.Resolution{}, validation: &configkit.Validation{}},
+	} {
+		t.Run(state.name, func(t *testing.T) {
+			path := configkit.Keys("value")
+			var target int
+			for _, operation := range []struct {
+				name string
+				call func()
+			}{
+				{"IsExplicit", func() { state.resolution.IsExplicit(path) }},
+				{"InputInfo", func() { state.resolution.InputInfo(path) }},
+				{"Source", func() { state.resolution.Source("source") }},
+				{"SourceContext", func() { state.resolution.SourceContext("source") }},
+				{"Record", func() { state.resolution.Record(path, configkit.ChangeNormalization, "reason") }},
+				{"Resolution.Error", func() { state.resolution.Error(path, "message") }},
+				{"Resolution.Warning", func() { state.resolution.Warning(path, "message") }},
+				{"Default", func() { configkit.Default(state.resolution, path, &target, 1, "reason") }},
+				{"Normalize", func() { configkit.Normalize(state.resolution, path, &target, 1, "reason") }},
+				{"Validation.Error", func() { state.validation.Error(path, "message") }},
+				{"Validation.Warning", func() { state.validation.Warning(path, "message") }},
+			} {
+				t.Run(operation.name, func(t *testing.T) {
+					defer func() {
+						if got := recover(); got != "configkit: callback context is no longer active" {
+							t.Errorf("panic = %v; want fixed closed-context failure", got)
+						}
+						if target != 0 {
+							t.Error("inactive helper changed target")
+						}
+					}()
+					operation.call()
+				})
+			}
+		})
+	}
+}

facade_equivalence_test.go

@@ -0,0 +1,164 @@
+package configkit_test
+
+import (
+	"bytes"
+	"os"
+	"path/filepath"
+	"reflect"
+	"strings"
+	"testing"
+	"testing/fstest"
+
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+)
+
+type equivalentConfig struct {
+	Version  uint64   `yaml:"version"`
+	Name     string   `yaml:"name"`
+	Enabled  bool     `yaml:"enabled"`
+	Count    int      `yaml:"count"`
+	Items    []string `yaml:"items"`
+	Optional *string  `yaml:"optional"`
+}
+
+func TestEquivalentSourceFormsPreserveInputSemantics(t *testing.T) {
+	const yaml = "version: 1\nname: retained\nenabled: false\ncount: 0\nitems: []\noptional: null\n"
+	hostPath := filepath.Join(t.TempDir(), "main.yml")
+	if err := os.WriteFile(hostPath, []byte(yaml), 0o600); err != nil {
+		t.Fatal(err)
+	}
+	namespace := configkit.NewFilesystem("bundle", fstest.MapFS{"main.yml": &fstest.MapFile{Data: []byte(yaml)}})
+	context := &configkit.FilesystemContext{Root: ".", BaseDir: ".", FS: &namespace}
+	for _, test := range []struct {
+		name    string
+		source  configkit.Source
+		context *configkit.FilesystemContext
+		kind    configkit.SourceKind
+	}{
+		{"host", configkit.File(hostPath), nil, configkit.SourceKindFile},
+		{"native", namespace.File("main.yml"), nil, configkit.SourceKindFilesystem},
+		{"bytes", configkit.Bytes("memory", []byte(yaml)), context, configkit.SourceKindBytes},
+		{"reader", configkit.Reader("stream", strings.NewReader(yaml)), context, configkit.SourceKindReader},
+		{"mapping", configkit.Mapping("programmatic", map[string]any{
+			"version": uint64(1), "name": "retained", "enabled": false, "count": 0,
+			"items": []any{}, "optional": nil,
+		}), context, configkit.SourceKindMapping},
+	} {
+		t.Run(test.name, func(t *testing.T) {
+			checks := 0
+			result, err := configkit.LoadLayered(configkit.Input{Source: test.source, Filesystem: test.context}, configkit.LayeredOptions[equivalentConfig]{
+				Definition: configkit.Definition[equivalentConfig]{Version: &configkit.VersionRule{
+					Path: configkit.Keys("version"), Check: func(version configkit.Version, validation *configkit.Validation) error {
+						checks++
+						if !version.Present || version.Text != "1" {
+							t.Errorf("version = %#v", version)
+						}
+						return nil
+					},
+				}},
+			})
+			if err != nil {
+				t.Fatal(err)
+			}
+			want := equivalentConfig{Version: 1, Name: "retained", Items: []string{}}
+			if !reflect.DeepEqual(result.Config, want) || checks != 1 {
+				t.Fatalf("config = %#v, checks %d", result.Config, checks)
+			}
+			for _, field := range []string{"version", "name", "enabled", "count", "items", "optional"} {
+				info, ok := result.Metadata().Lookup(configkit.Keys(field))
+				if !ok || !info.Explicit || info.Origin.Layer != configkit.LayerBase || info.Null != (field == "optional") {
+					t.Errorf("%s input info = %#v, %v", field, info, ok)
+				}
+			}
+			sources := result.Sources()
+			if len(sources) != 1 || sources[0].Kind != test.kind || sources[0].ID != "source-1" || sources[0].UnderlayIndex != 0 {
+				t.Fatalf("sources = %#v", sources)
+			}
+			resource, ok := result.SourceContext("source-1")
+			if !ok || resource.BaseDir != "." || resource.FS == nil {
+				t.Fatalf("source context = %#v, %v", resource, ok)
+			}
+		})
+	}
+}
+
+func TestRepeatedImportsAcrossTiersAndReaderConsumption(t *testing.T) {
+	namespace := configkit.NewFilesystem("bundle", fstest.MapFS{
+		"left.yml":   &fstest.MapFile{Data: []byte("configkit: {imports: [{path: shared.yml}]}\n")},
+		"right.yml":  &fstest.MapFile{Data: []byte("configkit: {imports: [{path: shared.yml}]}\n")},
+		"shared.yml": &fstest.MapFile{Data: []byte("name: retained\n")},
+	})
+	type config struct {
+		Name string `yaml:"name"`
+	}
+	left := configkit.Input{Source: namespace.File("left.yml"), Imports: true}
+	right := configkit.Input{Source: namespace.File("right.yml"), Imports: true}
+	_, err := configkit.LoadLayered(configkit.Input{Source: configkit.NoSource()}, configkit.LayeredOptions[config]{
+		Underlays: []configkit.Underlay{{Inputs: []configkit.Input{left, right}}},
+	})
+	if got := layeredErrorCode(t, err); got != configkit.CodeImportRepeated {
+		t.Fatalf("same-tier repeated import = %s", got)
+	}
+	result, err := configkit.LoadLayered(configkit.Input{Source: configkit.NoSource()}, configkit.LayeredOptions[config]{
+		Underlays: []configkit.Underlay{{Inputs: []configkit.Input{left}}, {Inputs: []configkit.Input{right}}},
+	})
+	if err != nil || result.Config.Name != "retained" || len(result.Sources()) != 4 {
+		t.Fatalf("cross-tier repeated import = %#v, %v", result, err)
+	}
+	reader := configkit.Reader("single-use", strings.NewReader("name: retained\n"))
+	_, err = configkit.LoadLayered(configkit.Input{Source: configkit.NoSource()}, configkit.LayeredOptions[config]{
+		Underlays: []configkit.Underlay{{Inputs: []configkit.Input{{Source: reader}}}, {Inputs: []configkit.Input{{Source: reader}}}},
+	})
+	if got := layeredErrorCode(t, err); got != configkit.CodeSourceReaderUsed {
+		t.Fatalf("reader re-consumption = %s", got)
+	}
+}
+
+func TestReplacedSecretRemainsAbsentFromSafeOutput(t *testing.T) {
+	type config struct {
+		Secret string `yaml:"secret"`
+	}
+	result, err := configkit.LoadLayered(configkit.Input{Source: configkit.Bytes("main", []byte("secret: new-secret-canary\n"))}, configkit.LayeredOptions[config]{
+		Underlays:  []configkit.Underlay{{Inputs: []configkit.Input{{Source: configkit.Mapping("lower", map[string]any{"secret": "old-secret-canary"})}}}},
+		Definition: configkit.Definition[config]{Secret: func(path configkit.Path) bool { return path.String() == "/secret" }},
+	})
+	if err != nil || result.Config.Secret != "new-secret-canary" {
+		t.Fatalf("secret load = %#v, %v", result, err)
+	}
+	var effective, history bytes.Buffer
+	if err := result.WriteEffective(&effective); err != nil {
+		t.Fatal(err)
+	}
+	if err := result.WriteExplanation(&history, configkit.Keys("secret")); err != nil {
+		t.Fatal(err)
+	}
+	if strings.Contains(effective.String()+history.String(), "old-secret-canary") || strings.Contains(effective.String()+history.String(), "new-secret-canary") {
+		t.Fatalf("secret output leaked: %q %q", effective.String(), history.String())
+	}
+	_, err = configkit.LoadLayered(configkit.Input{Source: configkit.Bytes("main", []byte("secret: new-secret-canary\n"))}, configkit.LayeredOptions[config]{
+		Underlays: []configkit.Underlay{{Inputs: []configkit.Input{{Source: configkit.Mapping("lower", map[string]any{"secret": "old-secret-canary"})}}}},
+		Definition: configkit.Definition[config]{Validate: func(config *config, validation *configkit.Validation) {
+			validation.Error(configkit.Keys("secret"), "invalid secret")
+		}},
+	})
+	loadError, ok := err.(*configkit.LoadError)
+	if !ok {
+		t.Fatalf("validation error = %#v", err)
+	}
+	var diagnostics bytes.Buffer
+	if err := configkit.WriteDiagnostics(&diagnostics, loadError.Diagnostics()); err != nil {
+		t.Fatal(err)
+	}
+	if strings.Contains(diagnostics.String(), "secret-canary") {
+		t.Fatalf("diagnostic leaked secret: %q", diagnostics.String())
+	}
+}
+
+func layeredErrorCode(t *testing.T, err error) configkit.Code {
+	t.Helper()
+	loadError, ok := err.(*configkit.LoadError)
+	if !ok || len(loadError.Diagnostics()) == 0 {
+		t.Fatalf("load error = %#v", err)
+	}
+	return loadError.Diagnostics()[0].Code
+}

facade_filesystem_test.go

@@ -0,0 +1,142 @@
+package configkit_test
+
+import (
+	"embed"
+	"io/fs"
+	"reflect"
+	"strconv"
+	"strings"
+	"testing"
+	"testing/fstest"
+
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+)
+
+//go:embed testdata/filesystem
+var filesystemFixtures embed.FS
+
+type filesystemFacadeConfig struct {
+	Items map[string]string `yaml:"items"`
+}
+
+func TestFacadeFilesystemSourceImportsOverlayAndReuse(t *testing.T) {
+	fixture, err := fs.Sub(filesystemFixtures, "testdata/filesystem")
+	if err != nil {
+		t.Fatal(err)
+	}
+	namespace := configkit.NewFilesystem("embedded", fixture)
+	copyOfNamespace := namespace
+	source := namespace.File("config/main.yml")
+	for range 2 {
+		result, err := configkit.Load(source, configkit.Options[filesystemFacadeConfig]{
+			Imports: true, Overlay: "testing", Filesystem: &configkit.FilesystemContext{FS: &copyOfNamespace},
+		})
+		if err != nil {
+			t.Fatal(err)
+		}
+		if want := (map[string]string{"main": "selected", "shared": "default"}); !reflect.DeepEqual(result.Config.Items, want) {
+			t.Fatalf("items = %#v, want %#v", result.Config.Items, want)
+		}
+		sources := result.Sources()
+		if len(sources) != 3 {
+			t.Fatalf("sources = %#v", sources)
+		}
+		for index, want := range []string{"config/main.yml", "shared.yml", "overlays/testing.yml"} {
+			if sources[index].ID != "source-"+strconv.Itoa(index+1) || sources[index].Path != want || sources[index].Kind != configkit.SourceKindFilesystem {
+				t.Errorf("source %d = %#v", index, sources[index])
+			}
+			if sources[index].Label != "embedded/"+want {
+				t.Errorf("source label = %q", sources[index].Label)
+			}
+		}
+		if sources[1].ImportedFrom == nil || sources[1].ImportedFrom.SourceID != sources[0].ID || sources[1].ImportedFrom.Line == 0 {
+			t.Fatalf("import location = %#v", sources[1].ImportedFrom)
+		}
+	}
+}
+
+func TestFacadeFilesystemContextsAndIdentity(t *testing.T) {
+	first := configkit.NewFilesystem("same", fstest.MapFS{
+		"root/config/main.yml":      &fstest.MapFile{Data: []byte("configkit: {imports: [{path: ../shared.yml}]}\n")},
+		"root/shared.yml":           &fstest.MapFile{Data: []byte("items: {value: first}\n")},
+		"root/overlays/testing.yml": &fstest.MapFile{Data: []byte("items: {overlay: first}\n")},
+	})
+	second := configkit.NewFilesystem("same", fstest.MapFS{
+		"root/config/main.yml": &fstest.MapFile{Data: []byte("items: {value: second}\n")},
+	})
+	context := &configkit.FilesystemContext{Root: "root", FS: &first}
+	result, err := configkit.Load(first.File("root/config/main.yml"), configkit.Options[filesystemFacadeConfig]{Imports: true, Overlay: "testing", Filesystem: context})
+	if err != nil || result.Config.Items["value"] != "first" || result.Config.Items["overlay"] != "first" {
+		t.Fatalf("contained load = %#v, %v", result, err)
+	}
+	result, err = configkit.Load[filesystemFacadeConfig](second.File("root/config/main.yml"))
+	if err != nil || result.Config.Items["value"] != "second" {
+		t.Fatalf("same-label independent namespace = %#v, %v", result, err)
+	}
+	checkCode(t, second.File("root/config/main.yml"), configkit.Options[filesystemFacadeConfig]{Filesystem: context}, configkit.CodeOptionsInvalid)
+	checkCode(t, first.File("root/config/main.yml"), configkit.Options[filesystemFacadeConfig]{Filesystem: &configkit.FilesystemContext{Root: "root/config", FS: &first}, Imports: true}, configkit.CodeImportOutsideRoot)
+	checkCode(t, configkit.File("testdata/filesystem/config/main.yml"), configkit.Options[filesystemFacadeConfig]{Filesystem: context}, configkit.CodeOptionsInvalid)
+
+	for _, input := range []struct {
+		name   string
+		source configkit.Source
+		kind   configkit.SourceKind
+	}{
+		{"bytes", configkit.Bytes("memory", []byte("configkit: {imports: [{path: shared.yml}]}\n")), configkit.SourceKindBytes},
+		{"reader", configkit.Reader("stream", strings.NewReader("configkit: {imports: [{path: shared.yml}]}\n")), configkit.SourceKindReader},
+	} {
+		t.Run(input.name, func(t *testing.T) {
+			result, err := configkit.Load(input.source, configkit.Options[filesystemFacadeConfig]{Imports: true, Filesystem: &configkit.FilesystemContext{Root: "root", BaseDir: "root", FS: &first}})
+			if err != nil || result.Config.Items["value"] != "first" {
+				t.Fatalf("synthetic import = %#v, %v", result, err)
+			}
+			if got := result.Sources(); len(got) != 2 || got[0].Kind != input.kind || got[0].Path != "" || got[1].Kind != configkit.SourceKindFilesystem {
+				t.Fatalf("sources = %#v", got)
+			}
+		})
+	}
+	checkCode(t, configkit.Bytes("memory", []byte("items: {}\n")), configkit.Options[filesystemFacadeConfig]{Filesystem: &configkit.FilesystemContext{Root: "root", BaseDir: ".", FS: &first}}, configkit.CodeImportOutsideRoot)
+	result, err = configkit.Load(configkit.Bytes("memory", []byte("items: {value: main}\n")), configkit.Options[filesystemFacadeConfig]{
+		Overlay: "testing", Filesystem: &configkit.FilesystemContext{Root: "root", BaseDir: "root", FS: &first},
+	})
+	if err != nil || result.Config.Items["value"] != "main" || result.Config.Items["overlay"] != "first" {
+		t.Fatalf("synthetic selected overlay = %#v, %v", result, err)
+	}
+}
+
+func TestFacadeSourceKindsIncludeHostAndCLI(t *testing.T) {
+	result, err := configkit.Load(configkit.File("testdata/filesystem/shared.yml"), configkit.Options[filesystemFacadeConfig]{
+		Overrides: []configkit.Override{{Path: configkit.Keys("items", "shared"), Value: "changed", Flag: "--shared"}},
+	})
+	if err != nil {
+		t.Fatal(err)
+	}
+	sources := result.Sources()
+	if len(sources) != 2 || sources[0].Kind != configkit.SourceKindFile || sources[0].Path == "" || sources[1].Kind != configkit.SourceKindCLI || sources[1].Path != "" {
+		t.Fatalf("host and CLI sources = %#v", sources)
+	}
+}
+
+func TestFacadeFilesystemConstructorDiagnostics(t *testing.T) {
+	var nilFilesystem fs.FS
+	var zero configkit.Filesystem
+	for _, source := range []configkit.Source{
+		zero.File("main.yml"),
+		configkit.NewFilesystem("", fstest.MapFS{}).File("main.yml"),
+		configkit.NewFilesystem("bad\nlabel", fstest.MapFS{}).File("main.yml"),
+		configkit.NewFilesystem("good", nilFilesystem).File("main.yml"),
+		configkit.NewFilesystem("good", fstest.MapFS{}).File("."),
+		configkit.NewFilesystem("good", fstest.MapFS{}).File("../outside.yml"),
+	} {
+		checkCode(t, source, configkit.Options[filesystemFacadeConfig]{}, configkit.CodeSourceInvalid)
+	}
+}
+
+func checkCode(t *testing.T, source configkit.Source, options configkit.Options[filesystemFacadeConfig], want configkit.Code) {
+	t.Helper()
+	_, err := configkit.Load(source, options)
+	loadError, ok := err.(*configkit.LoadError)
+	if !ok || len(loadError.Diagnostics()) == 0 || loadError.Diagnostics()[0].Code != want {
+		t.Fatalf("error = %#v, want %s", err, want)
+	}
+}

facade_inheritance_test.go

@@ -0,0 +1,284 @@
+package configkit_test
+
+import (
+	"bytes"
+	"io/fs"
+	"reflect"
+	"strings"
+	"testing"
+	"testing/fstest"
+
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+)
+
+type inheritedEntry struct {
+	Enabled  bool                         `yaml:"enabled"`
+	Count    int                          `yaml:"count"`
+	Resource string                       `yaml:"resource"`
+	Settings map[string]map[string]string `yaml:"settings"`
+}
+
+type inheritedConfiguration struct {
+	Version string                    `yaml:"version"`
+	Entries map[string]inheritedEntry `yaml:"entries"`
+}
+
+func TestFacadeInheritancePreservesPresenceOriginsAndHistory(t *testing.T) {
+	input := []byte(`entries:
+  parent:
+    enabled: false
+    count: 0
+    settings:
+      primary: {value: original}
+      secondary: {extends: primary}
+  child:
+    extends: parent
+    settings:
+      primary: {value: custom}
+`)
+	defaultRan := false
+	result, err := configkit.Load(configkit.Bytes("config.yml", input), configkit.Options[inheritedConfiguration]{Definition: configkit.Definition[inheritedConfiguration]{
+		Resolve: func(config *inheritedConfiguration, resolution *configkit.Resolution) error {
+			if !resolution.IsExplicit(configkit.Keys("entries", "child", "enabled")) {
+				t.Error("inherited false is not explicit")
+			}
+			info, found := resolution.InputInfo(configkit.Keys("entries", "child", "enabled"))
+			if !found || len(info.Origin.Inheritance) != 1 {
+				t.Errorf("resolver inherited origin = %#v, %v", info, found)
+			}
+			child := config.Entries["child"]
+			configkit.Default(resolution, configkit.Keys("entries", "child", "enabled"), &child.Enabled, true, "use fallback")
+			defaultRan = child.Enabled
+			config.Entries["child"] = child
+			return nil
+		},
+	}})
+	if err != nil {
+		t.Fatal(err)
+	}
+	child := result.Config.Entries["child"]
+	if defaultRan || child.Enabled || child.Count != 0 || child.Settings["secondary"]["value"] != "custom" {
+		t.Fatalf("inherited values = %#v, default ran %v", child, defaultRan)
+	}
+	path := configkit.Keys("entries", "child", "settings", "secondary", "value")
+	info, found := result.Metadata().Lookup(path)
+	if !found || !info.Explicit || len(info.Origin.Inheritance) != 1 ||
+		info.Origin.Inheritance[0].From.String() != "/entries/child/settings/primary/value" ||
+		info.Origin.Inheritance[0].To.String() != path.String() {
+		t.Fatalf("nested destination origin = %#v, %v", info, found)
+	}
+	info.Origin.Inheritance[0].Locations[0].SourceID = "mutated"
+	info, _ = result.Metadata().Lookup(path)
+	if info.Origin.Inheritance[0].Locations[0].SourceID == "mutated" {
+		t.Fatal("public inheritance record aliases inspection state")
+	}
+	if _, found := result.Metadata().Lookup(configkit.Keys("entries", "child", "extends")); found {
+		t.Fatal("consumed directive remained effective")
+	}
+	control, found := result.Explain(configkit.Keys("entries", "child", "extends"))
+	if !found || control.Effective.Present || len(control.History) < 2 ||
+		control.History[len(control.History)-1].Origin.Operation != configkit.ChangeInheritance {
+		t.Fatalf("consumed directive = %#v, %v", control, found)
+	}
+	explanation, found := result.Explain(path)
+	if !found || explanation.Effective.YAML != "custom\n" {
+		t.Fatalf("nested explanation = %#v, %v", explanation, found)
+	}
+	for _, change := range explanation.History {
+		if change.Origin.Operation == configkit.ChangeDecoding {
+			t.Fatalf("inherited value attributed to decoding: %#v", explanation.History)
+		}
+	}
+}
+
+func TestFacadeInheritanceLayeredPrecedenceAndSourceContext(t *testing.T) {
+	filesystem := configkit.NewFilesystem("bundle", fstest.MapFS{
+		"config/main.yml":          &fstest.MapFile{Data: []byte("entries: {child: {extends: parent}}\n")},
+		"shared/parent.yml":        &fstest.MapFile{Data: []byte("entries: {parent: {resource: icon.txt, count: 1}}\n")},
+		"shared/flags.yml":         &fstest.MapFile{Data: []byte("entries: {parent: {enabled: false}}\n")},
+		"shared/icon.txt":          &fstest.MapFile{Data: []byte("parent-resource")},
+		"config/overlays/test.yml": &fstest.MapFile{Data: []byte("entries: {parent: {count: 2}}\n")},
+	})
+	result, err := configkit.LoadLayered(configkit.Input{Source: filesystem.File("config/main.yml")}, configkit.LayeredOptions[inheritedConfiguration]{
+		Underlays: []configkit.Underlay{
+			{Inputs: []configkit.Input{{Source: filesystem.File("shared/parent.yml")}}},
+			{Inputs: []configkit.Input{{Source: filesystem.File("shared/flags.yml")}}},
+		},
+		Overlay: "test", OverlayFilesystem: &configkit.FilesystemContext{Root: "config", BaseDir: "config", FS: &filesystem},
+		Overrides: []configkit.Override{{Path: configkit.Keys("entries", "child", "count"), Value: 3, Flag: "--count"}},
+	})
+	if err != nil {
+		t.Fatal(err)
+	}
+	child := result.Config.Entries["child"]
+	if child.Count != 3 || child.Resource != "icon.txt" {
+		t.Fatalf("layered inheritance = %#v", child)
+	}
+	info, found := result.Metadata().Lookup(configkit.Keys("entries", "child", "resource"))
+	if !found || len(info.Origin.Inheritance) != 1 || len(info.Origin.Locations) != 1 {
+		t.Fatalf("resource origin = %#v, %v", info, found)
+	}
+	context, found := result.SourceContext(info.Origin.Locations[0].SourceID)
+	if !found || context.BaseDir != "shared" || context.FS == nil {
+		t.Fatalf("source context = %#v, %v", context, found)
+	}
+	data, err := fs.ReadFile(context.FS, context.BaseDir+"/"+child.Resource)
+	if err != nil || string(data) != "parent-resource" {
+		t.Fatalf("source-relative resource = %q, %v", data, err)
+	}
+	count, found := result.Metadata().Lookup(configkit.Keys("entries", "child", "count"))
+	if !found || count.Origin.Layer != configkit.LayerCLI || len(count.Origin.Inheritance) != 0 {
+		t.Fatalf("CLI replacement origin = %#v, %v", count, found)
+	}
+	var rendered bytes.Buffer
+	if err := result.WriteEffective(&rendered); err != nil || strings.Contains(rendered.String(), "extends:") {
+		t.Fatalf("effective rendering = %q, %v", rendered.String(), err)
+	}
+}
+
+func TestFacadeInheritanceMappingMatchesBytes(t *testing.T) {
+	values := map[string]any{"entries": map[string]any{
+		"parent": map[string]any{"enabled": false, "count": 0},
+		"child":  map[string]any{"extends": "parent"},
+	}}
+	mapped, err := configkit.Load[inheritedConfiguration](configkit.Mapping("mapping", values))
+	if err != nil {
+		t.Fatal(err)
+	}
+	fromYAML, err := configkit.Load[inheritedConfiguration](configkit.Bytes("config.yml", []byte("entries: {parent: {enabled: false, count: 0}, child: {extends: parent}}\n")))
+	if err != nil || !reflect.DeepEqual(mapped.Config, fromYAML.Config) {
+		t.Fatalf("mapping and bytes differ: %#v, %#v, %v", mapped, fromYAML, err)
+	}
+}
+
+func TestFacadeInheritanceProtectsVersionOwnership(t *testing.T) {
+	for _, test := range []struct {
+		name, input string
+		path        configkit.Path
+		wantFailure bool
+	}{
+		{"inherited version", "entries: {parent: {count: 1}, child: {extends: parent}}\n", configkit.Keys("entries", "child", "count"), true},
+		{"overridden version", "entries: {parent: {count: 1}, child: {extends: parent, count: 1}}\n", configkit.Keys("entries", "child", "count"), true},
+		{"direct unchanged version", "entries: {parent: {enabled: false}, child: {extends: parent, count: 1}}\n", configkit.Keys("entries", "child", "count"), false},
+		{"consumed checked directive", "entries: {parent: {count: 1}, child: {extends: parent}}\n", configkit.Keys("entries", "child", "extends"), true},
+		{"independent top-level version", "version: v1\nentries: {parent: {count: 1}, child: {extends: parent}}\n", configkit.Keys("version"), false},
+	} {
+		t.Run(test.name, func(t *testing.T) {
+			checks := struct{ version, defaults, resolution, validation int }{}
+			result, err := configkit.Load(configkit.Bytes("version.yml", []byte(test.input)), configkit.Options[inheritedConfiguration]{Definition: configkit.Definition[inheritedConfiguration]{
+				Version: &configkit.VersionRule{Path: test.path, Check: func(configkit.Version, *configkit.Validation) error {
+					checks.version++
+					return nil
+				}},
+				Defaults: func() inheritedConfiguration { checks.defaults++; return inheritedConfiguration{} },
+				Resolve:  func(*inheritedConfiguration, *configkit.Resolution) error { checks.resolution++; return nil },
+				Validate: func(*inheritedConfiguration, *configkit.Validation) { checks.validation++ },
+			}})
+			if test.wantFailure {
+				if result != nil || err == nil {
+					t.Fatalf("protected version = %#v, %v", result, err)
+				}
+				loadError, ok := err.(*configkit.LoadError)
+				if !ok || len(loadError.Diagnostics()) == 0 || loadError.Diagnostics()[0].Code != configkit.CodeInheritanceVersion ||
+					checks != (struct{ version, defaults, resolution, validation int }{version: 1}) {
+					t.Fatalf("version failure = %v, callbacks %#v", err, checks)
+				}
+			} else if err != nil || result == nil || checks != (struct{ version, defaults, resolution, validation int }{1, 1, 1, 1}) {
+				t.Fatalf("unchanged version = %#v, %v, callbacks %#v", result, err, checks)
+			}
+		})
+	}
+}
+
+func TestFacadeInheritanceFailureStopsLaterCallbacks(t *testing.T) {
+	checks := struct{ defaults, resolution, validation int }{}
+	result, err := configkit.Load(configkit.Bytes("invalid.yml", []byte("entries: {child: {extends: PRIVATE-REFERENCE-CANARY}}\n")), configkit.Options[inheritedConfiguration]{Definition: configkit.Definition[inheritedConfiguration]{
+		Defaults: func() inheritedConfiguration { checks.defaults++; return inheritedConfiguration{} },
+		Resolve:  func(*inheritedConfiguration, *configkit.Resolution) error { checks.resolution++; return nil },
+		Validate: func(*inheritedConfiguration, *configkit.Validation) { checks.validation++ },
+	}})
+	if result != nil || err == nil || checks != (struct{ defaults, resolution, validation int }{}) || strings.Contains(err.Error(), "PRIVATE-REFERENCE-CANARY") {
+		t.Fatalf("invalid inheritance = %#v, %v, callbacks %#v", result, err, checks)
+	}
+	loadError, ok := err.(*configkit.LoadError)
+	if !ok || len(loadError.Diagnostics()) == 0 || loadError.Diagnostics()[0].Code != configkit.CodeInheritanceMissing {
+		t.Fatalf("missing reference diagnostics = %v", err)
+	}
+}
+
+func TestFacadeInheritanceResolvesAfterImportsAndCLIReferenceChange(t *testing.T) {
+	filesystem := configkit.NewFilesystem("bundle", fstest.MapFS{
+		"main.yml":   &fstest.MapFile{Data: []byte("configkit: {imports: [{path: parent.yml}]}\nentries: {child: {extends: first}}\n")},
+		"parent.yml": &fstest.MapFile{Data: []byte("entries: {first: {count: 1}, second: {count: 2}}\n")},
+	})
+	result, err := configkit.Load(filesystem.File("main.yml"), configkit.Options[inheritedConfiguration]{
+		Imports: true, Overrides: []configkit.Override{{Path: configkit.Keys("entries", "child", "extends"), Value: "second", Flag: "--extends"}},
+	})
+	if err != nil || result.Config.Entries["child"].Count != 2 {
+		t.Fatalf("import and CLI reference = %#v, %v", result, err)
+	}
+	history := result.Metadata().History(configkit.Keys("entries", "child", "extends"))
+	if len(history) < 3 || history[len(history)-1].Origin.Operation != configkit.ChangeInheritance {
+		t.Fatalf("superseded reference history = %#v", history)
+	}
+	conflicting := configkit.NewFilesystem("bundle", fstest.MapFS{
+		"main.yml":   &fstest.MapFile{Data: []byte("configkit: {imports: [{path: parent.yml}]}\nentries: {child: {extends: first}, first: {count: 3}}\n")},
+		"parent.yml": &fstest.MapFile{Data: []byte("entries: {first: {count: 1}}\n")},
+	})
+	_, err = configkit.Load[inheritedConfiguration](conflicting.File("main.yml"), configkit.Options[inheritedConfiguration]{Imports: true})
+	loadError, ok := err.(*configkit.LoadError)
+	if !ok || len(loadError.Diagnostics()) == 0 || loadError.Diagnostics()[0].Code != configkit.CodeComposeConflict {
+		t.Fatalf("strict conflict before expansion = %v", err)
+	}
+}
+
+func TestFacadeInheritanceSelectedOverlayCancelsRelationship(t *testing.T) {
+	filesystem := configkit.NewFilesystem("bundle", fstest.MapFS{
+		"main.yml":          &fstest.MapFile{Data: []byte("entries: {parent: {count: 7}, child: {extends: parent, enabled: false}}\n")},
+		"overlays/test.yml": &fstest.MapFile{Data: []byte("entries: {child: {extends: null}}\n")},
+	})
+	result, err := configkit.Load(filesystem.File("main.yml"), configkit.Options[inheritedConfiguration]{
+		Overlay: "test", Filesystem: &configkit.FilesystemContext{Root: ".", FS: &filesystem},
+	})
+	if err != nil || result.Config.Entries["child"].Count != 0 || result.Config.Entries["child"].Enabled {
+		if loadError, ok := err.(*configkit.LoadError); ok {
+			t.Fatalf("cancelled relationship = %#v, %v, diagnostics %#v", result, err, loadError.Diagnostics())
+		}
+		t.Fatalf("cancelled relationship = %#v, %v", result, err)
+	}
+	history := result.Metadata().History(configkit.Keys("entries", "child", "extends"))
+	if len(history) < 3 || history[len(history)-1].Origin.Operation != configkit.ChangeInheritance {
+		t.Fatalf("cancellation history = %#v", history)
+	}
+}
+
+func TestFacadeInheritedSecretsStayRedactedAfterLookup(t *testing.T) {
+	const canary = "INHERITED-RELEASE-TEST-CREDENTIAL"
+	t.Setenv("CONFIGKIT_INHERITED_TEST_SECRET", canary)
+	type entry struct {
+		Credential configkit.Secret `yaml:"credential"`
+		Plain      string           `yaml:"plain"`
+	}
+	type configuration struct {
+		Entries map[string]entry `yaml:"entries"`
+	}
+	result, err := configkit.Load[configuration](configkit.Bytes("secret.yml", []byte("entries: {parent: {credential: CONFIGKIT_INHERITED_TEST_SECRET, plain: visible}, child: {extends: parent}}\n")), configkit.Options[configuration]{Definition: configkit.Definition[configuration]{
+		Secret: func(path configkit.Path) bool { return path.String() == "/entries/parent/credential" },
+	}})
+	if err != nil || result.Config.Entries["child"].Credential.Value() != canary {
+		t.Fatalf("inherited credential = %#v, %v", result, err)
+	}
+	path := configkit.Keys("entries", "child", "credential")
+	explanation, found := result.Explain(path)
+	if !found || !explanation.Effective.Redacted || strings.Contains(explanation.Effective.YAML, canary) {
+		t.Fatalf("credential explanation = %#v, %v", explanation, found)
+	}
+	var rendered bytes.Buffer
+	if err := result.WriteEffective(&rendered); err != nil || strings.Contains(rendered.String(), canary) || !strings.Contains(rendered.String(), "visible") {
+		t.Fatalf("effective secret rendering = %q, %v", rendered.String(), err)
+	}
+	rendered.Reset()
+	if err := result.WriteExplanation(&rendered, path); err != nil || strings.Contains(rendered.String(), canary) {
+		t.Fatalf("historical secret rendering = %q, %v", rendered.String(), err)
+	}
+}

facade_internal_test.go

@@ -0,0 +1,52 @@
+package configkit
+
+import (
+	"errors"
+	"reflect"
+	"strings"
+	"testing"
+
+	"gitea.maximumdirect.net/eric/ConfigKit/internal/engine"
+)
+
+func TestWrappedSourcesPreserveEngineOwnership(t *testing.T) {
+	t.Parallel()
+
+	type config struct {
+		Value string `yaml:"value"`
+	}
+	data := []byte("value: retained\n")
+	source := Bytes("snapshot.yml", data)
+	data[7] = 'X'
+	result, err := engine.Load[config](source.toEngine(), engine.SecretBinding{})
+	if err != nil || result.Config.Value != "retained" {
+		t.Fatalf("snapshotted source = %#v, %v", result, err)
+	}
+
+	readerSource := Reader("reader.yml", strings.NewReader("value: once\n"))
+	first := readerSource
+	if _, err := engine.Load[config](first.toEngine(), engine.SecretBinding{}); err != nil {
+		t.Fatal(err)
+	}
+	_, err = engine.Load[config](readerSource.toEngine(), engine.SecretBinding{})
+	var loadError *engine.LoadError
+	if !errors.As(err, &loadError) || len(loadError.Diagnostics()) != 1 || loadError.Diagnostics()[0].Code != engine.CodeSourceReaderUsed {
+		t.Fatalf("copied reader source error = %#v", err)
+	}
+}
+
+func TestWrappedPathsRetainEngineSegmentIntent(t *testing.T) {
+	t.Parallel()
+
+	parsed, err := ParsePath("/0")
+	if err != nil {
+		t.Fatal(err)
+	}
+	keyed, indexed := Keys("0"), Path{}.Index(0)
+	if parsed.String() != "/0" || keyed.String() != "/0" || indexed.String() != "/0" {
+		t.Fatalf("path spellings = %q, %q, %q", parsed, keyed, indexed)
+	}
+	if reflect.DeepEqual(parsed.value, keyed.value) || reflect.DeepEqual(parsed.value, indexed.value) || reflect.DeepEqual(keyed.value, indexed.value) {
+		t.Fatal("path wrappers collapsed parsed, mapping-key, and index segments")
+	}
+}

facade_layered_test.go

@@ -0,0 +1,243 @@
+package configkit_test
+
+import (
+	"bytes"
+	"os"
+	"path/filepath"
+	"reflect"
+	"strconv"
+	"strings"
+	"testing"
+	"testing/fstest"
+
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+)
+
+type layeredFacadeConfig struct {
+	Settings map[string]string `yaml:"settings"`
+	Count    int               `yaml:"count"`
+	Enabled  bool              `yaml:"enabled"`
+	List     []string          `yaml:"list"`
+	Optional *string           `yaml:"optional"`
+	Derived  string            `yaml:"derived"`
+}
+
+func TestFacadeLayeredMixedSourcesAndInspection(t *testing.T) {
+	mainPath := filepath.Join(t.TempDir(), "main.yml")
+	if err := os.WriteFile(mainPath, []byte("settings: {shared: main, secret: new-canary}\ncount: 0\nenabled: false\nlist: []\noptional: null\n"), 0o600); err != nil {
+		t.Fatal(err)
+	}
+	lower := configkit.NewFilesystem("bundle", fstest.MapFS{
+		"main.yml":             &fstest.MapFile{Data: []byte("configkit: {imports: [{path: defaults.yml}]}\nsettings: {shared: lower, native: retained, secret: old-canary}\nlist: [lower]\n")},
+		"defaults.yml":         &fstest.MapFile{Data: []byte("settings: {imported: retained}\n")},
+		"overlays/testing.yml": &fstest.MapFile{Data: []byte("settings: {from_lower_namespace: retained}\n")},
+	})
+	selected := configkit.NewFilesystem("bundle", fstest.MapFS{
+		"overlays/testing.yml": &fstest.MapFile{Data: []byte("settings: {shared: overlay}\n")},
+	})
+	checks := struct{ defaults, resolution, validation int }{}
+	result, err := configkit.LoadLayered(configkit.Input{Source: configkit.File(mainPath)}, configkit.LayeredOptions[layeredFacadeConfig]{
+		Underlays: []configkit.Underlay{
+			{Inputs: []configkit.Input{
+				{Source: lower.File("main.yml"), Imports: true},
+				{Source: configkit.Mapping("programmatic-low", map[string]any{"settings": map[string]any{"mapping": "retained"}, "count": 7, "enabled": true})},
+				{Source: lower.File("overlays/testing.yml")},
+			}},
+			{Inputs: []configkit.Input{{Source: configkit.Mapping("programmatic-high", map[string]any{
+				"settings": map[string]any{"shared": "middle", "second": "retained"}, "list": []any{"middle"},
+			})}}},
+		},
+		Overlay: "testing", OverlayFilesystem: &configkit.FilesystemContext{Root: ".", BaseDir: ".", FS: &selected},
+		Overrides: []configkit.Override{{Path: configkit.Keys("settings", "shared"), Value: "cli", Flag: "--shared"}},
+		Definition: configkit.Definition[layeredFacadeConfig]{
+			Defaults: func() layeredFacadeConfig { checks.defaults++; return layeredFacadeConfig{} },
+			Resolve: func(config *layeredFacadeConfig, resolution *configkit.Resolution) error {
+				checks.resolution++
+				if source, ok := resolution.Source("source-2"); !ok || source.Layer != configkit.LayerUnderlay || source.UnderlayIndex != 1 || source.Kind != configkit.SourceKindFilesystem {
+					t.Errorf("resolver source = %#v, %v", source, ok)
+				}
+				configkit.Default(resolution, configkit.Keys("derived"), &config.Derived, config.Settings["native"], "derive from native", configkit.Keys("settings", "native"))
+				return nil
+			},
+			Validate: func(config *layeredFacadeConfig, validation *configkit.Validation) { checks.validation++ },
+			Secret:   func(path configkit.Path) bool { return path.String() == "/settings/secret" },
+		},
+	})
+	if err != nil {
+		t.Fatalf("layered load: %v, diagnostics %#v", err, err.(*configkit.LoadError).Diagnostics())
+	}
+	wantSettings := map[string]string{
+		"shared": "cli", "secret": "new-canary", "native": "retained", "imported": "retained",
+		"mapping": "retained", "from_lower_namespace": "retained", "second": "retained",
+	}
+	if !reflect.DeepEqual(result.Config.Settings, wantSettings) || result.Config.Count != 0 || result.Config.Enabled || result.Config.List == nil || len(result.Config.List) != 0 || result.Config.Optional != nil || result.Config.Derived != "retained" {
+		t.Fatalf("configuration = %#v", result.Config)
+	}
+	if checks != (struct{ defaults, resolution, validation int }{1, 1, 1}) {
+		t.Fatalf("lifecycle calls = %#v", checks)
+	}
+	sources := result.Sources()
+	if len(sources) != 8 {
+		t.Fatalf("sources = %#v", sources)
+	}
+	wantLayers := []configkit.Layer{configkit.LayerBase, configkit.LayerUnderlay, configkit.LayerUnderlay, configkit.LayerUnderlay, configkit.LayerUnderlay, configkit.LayerUnderlay, configkit.LayerOverlay, configkit.LayerCLI}
+	wantIndexes := []int{0, 1, 1, 1, 1, 2, 0, 0}
+	wantKinds := []configkit.SourceKind{configkit.SourceKindFile, configkit.SourceKindFilesystem, configkit.SourceKindFilesystem, configkit.SourceKindMapping, configkit.SourceKindFilesystem, configkit.SourceKindMapping, configkit.SourceKindFilesystem, configkit.SourceKindCLI}
+	for index, source := range sources {
+		if source.ID != "source-"+strconv.Itoa(index+1) || source.Layer != wantLayers[index] || source.UnderlayIndex != wantIndexes[index] || source.Kind != wantKinds[index] {
+			t.Errorf("source %d = %#v", index, source)
+		}
+	}
+	if sources[4].Path != sources[6].Path || sources[4].Label != sources[6].Label {
+		t.Fatalf("namespace-collision fixture changed: %#v, %#v", sources[4], sources[6])
+	}
+	sources[1].Label = "changed"
+	if result.Sources()[1].Label != "bundle/main.yml" {
+		t.Fatal("source records alias retained metadata")
+	}
+	for _, test := range []struct {
+		path string
+		want configkit.Layer
+	}{
+		{"/settings/native", configkit.LayerUnderlay},
+		{"/settings/shared", configkit.LayerCLI},
+		{"/derived", configkit.LayerResolution},
+	} {
+		path, err := configkit.ParsePath(test.path)
+		if err != nil {
+			t.Fatal(err)
+		}
+		info, ok := result.Metadata().Lookup(path)
+		if !ok || info.Origin.Layer != test.want {
+			t.Errorf("%s metadata = %#v, %v", test.path, info, ok)
+		}
+	}
+	container, ok := result.Metadata().Lookup(configkit.Keys("settings"))
+	if !ok || len(container.Origin.Locations) < 4 {
+		t.Fatalf("composite mapping origin = %#v, %v", container, ok)
+	}
+	explanation, ok := result.Explain(configkit.Keys("settings", "shared"))
+	if !ok || len(explanation.History) < 5 || explanation.Origin.Layer != configkit.LayerCLI {
+		t.Fatalf("shared history = %#v, %v", explanation, ok)
+	}
+	var effective, rendered bytes.Buffer
+	if err := result.WriteEffective(&effective); err != nil {
+		t.Fatal(err)
+	}
+	if err := result.WriteExplanation(&rendered, configkit.Keys("settings", "secret")); err != nil {
+		t.Fatal(err)
+	}
+	if strings.Contains(effective.String()+rendered.String(), "old-canary") || strings.Contains(effective.String()+rendered.String(), "new-canary") || !strings.Contains(rendered.String(), "redacted") {
+		t.Fatalf("secret rendering leaked: effective %q, explanation %q", effective.String(), rendered.String())
+	}
+}
+
+func TestFacadeLayeredDisplacedDescendantRemainsInspectable(t *testing.T) {
+	type config struct {
+		Choice string `yaml:"choice"`
+	}
+	result, err := configkit.LoadLayered(configkit.Input{Source: configkit.Mapping("main", map[string]any{"choice": "flat"})}, configkit.LayeredOptions[config]{
+		Underlays: []configkit.Underlay{{Inputs: []configkit.Input{{Source: configkit.Mapping("lower", map[string]any{
+			"choice": map[string]any{"nested": "historical"},
+		})}}}},
+	})
+	if err != nil || result.Config.Choice != "flat" {
+		t.Fatalf("replacement load = %#v, %v", result, err)
+	}
+	path := configkit.Keys("choice", "nested")
+	explanation, ok := result.Explain(path)
+	if !ok || explanation.Effective.Present || len(explanation.History) == 0 || explanation.History[0].Origin.Layer != configkit.LayerUnderlay {
+		t.Fatalf("deleted descendant = %#v, %v", explanation, ok)
+	}
+}
+
+func TestFacadeLayeredZeroUnderlaysMatchesOrdinaryLoad(t *testing.T) {
+	filesystem := configkit.NewFilesystem("bundle", fstest.MapFS{
+		"overlays/testing.yml": &fstest.MapFile{Data: []byte("value: selected\n")},
+	})
+	context := &configkit.FilesystemContext{Root: ".", BaseDir: ".", FS: &filesystem}
+	source := configkit.Bytes("main", []byte("value: base\n"))
+	type config struct {
+		Value string `yaml:"value"`
+	}
+	ordinary, err := configkit.Load(source, configkit.Options[config]{Overlay: "testing", Filesystem: context})
+	if err != nil {
+		t.Fatal(err)
+	}
+	layered, err := configkit.LoadLayered(configkit.Input{Source: source}, configkit.LayeredOptions[config]{Overlay: "testing", OverlayFilesystem: context})
+	if err != nil {
+		t.Fatal(err)
+	}
+	if ordinary.Config != layered.Config || !reflect.DeepEqual(ordinary.Sources(), layered.Sources()) {
+		t.Fatalf("ordinary = %#v, %#v; layered = %#v, %#v", ordinary.Config, ordinary.Sources(), layered.Config, layered.Sources())
+	}
+	var first, second bytes.Buffer
+	if err := ordinary.WriteEffective(&first); err != nil {
+		t.Fatal(err)
+	}
+	if err := layered.WriteEffective(&second); err != nil {
+		t.Fatal(err)
+	}
+	if first.String() != second.String() {
+		t.Fatalf("effective ordinary %q, layered %q", first.String(), second.String())
+	}
+	if ordinaryExplanation, ok := ordinary.Explain(configkit.Keys("value")); !ok {
+		t.Fatal("ordinary explanation missing")
+	} else if layeredExplanation, ok := layered.Explain(configkit.Keys("value")); !ok || !reflect.DeepEqual(ordinaryExplanation, layeredExplanation) {
+		t.Fatalf("explanations differ: %#v, %#v", ordinaryExplanation, layeredExplanation)
+	}
+}
+
+func TestFacadeLayeredOptionAndVersionFailures(t *testing.T) {
+	type config struct {
+		Version string `yaml:"version"`
+	}
+	namespace := configkit.NewFilesystem("bundle", fstest.MapFS{
+		"overlays/testing.yml": &fstest.MapFile{Data: []byte("{}\n")},
+	})
+	for _, test := range []struct {
+		name    string
+		main    configkit.Input
+		options []configkit.LayeredOptions[config]
+		want    configkit.Code
+	}{
+		{"zero source", configkit.Input{}, nil, configkit.CodeSourceInvalid},
+		{"multiple options", configkit.Input{Source: configkit.NoSource()}, []configkit.LayeredOptions[config]{{}, {}}, configkit.CodeOptionsInvalid},
+		{"missing overlay context", configkit.Input{Source: configkit.NoSource()}, []configkit.LayeredOptions[config]{{Overlay: "testing"}}, configkit.CodeOptionsInvalid},
+		{"selected file already acquired", configkit.Input{Source: configkit.NoSource()}, []configkit.LayeredOptions[config]{{
+			Overlay: "testing", OverlayFilesystem: &configkit.FilesystemContext{Root: ".", BaseDir: ".", FS: &namespace},
+			Underlays: []configkit.Underlay{{Inputs: []configkit.Input{{Source: namespace.File("overlays/testing.yml")}}}},
+		}}, configkit.CodeOverlayRepeated},
+		{"underlay version", configkit.Input{Source: configkit.NoSource()}, []configkit.LayeredOptions[config]{{
+			Definition: configkit.Definition[config]{Version: &configkit.VersionRule{Path: configkit.Keys("version"), Check: func(configkit.Version, *configkit.Validation) error { return nil }}},
+			Underlays:  []configkit.Underlay{{Inputs: []configkit.Input{{Source: configkit.Mapping("lower", map[string]any{"version": "forbidden"})}}}},
+		}}, configkit.CodeUnderlayVersion},
+	} {
+		t.Run(test.name, func(t *testing.T) {
+			_, err := configkit.LoadLayered(test.main, test.options...)
+			loadError, ok := err.(*configkit.LoadError)
+			if !ok || len(loadError.Diagnostics()) == 0 || loadError.Diagnostics()[0].Code != test.want {
+				t.Fatalf("error = %#v, want %s", err, test.want)
+			}
+		})
+	}
+}
+
+func TestFacadeLayeredExplicitHostOverlayWithoutMain(t *testing.T) {
+	root := t.TempDir()
+	if err := os.Mkdir(filepath.Join(root, "overlays"), 0o700); err != nil {
+		t.Fatal(err)
+	}
+	if err := os.WriteFile(filepath.Join(root, "overlays", "testing.yml"), []byte("value: selected\n"), 0o600); err != nil {
+		t.Fatal(err)
+	}
+	type config struct {
+		Value string `yaml:"value"`
+	}
+	result, err := configkit.LoadLayered(configkit.Input{Source: configkit.NoSource()}, configkit.LayeredOptions[config]{
+		Overlay: "testing", OverlayFilesystem: &configkit.FilesystemContext{Root: root, BaseDir: root},
+	})
+	if err != nil || result.Config.Value != "selected" || len(result.Sources()) != 1 || result.Sources()[0].Kind != configkit.SourceKindFile {
+		t.Fatalf("explicit host overlay = %#v, %v", result, err)
+	}
+}

facade_mapping_test.go

@@ -0,0 +1,133 @@
+package configkit_test
+
+import (
+	"math"
+	"reflect"
+	"strings"
+	"testing"
+	"testing/fstest"
+
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+)
+
+type mappingFacadeConfig struct {
+	Enabled  bool     `yaml:"enabled"`
+	Count    uint64   `yaml:"count"`
+	Optional *string  `yaml:"optional"`
+	Items    []string `yaml:"items"`
+	Name     string   `yaml:"name"`
+}
+
+func TestFacadeMappingSnapshotsAndMatchesYAML(t *testing.T) {
+	items := []any{"one", "two"}
+	values := map[string]any{
+		"name": "original", "enabled": false, "count": ^uint64(0),
+		"optional": nil, "items": items,
+	}
+	source := configkit.Mapping("programmatic", values)
+	values["name"] = "mutated"
+	items[0] = "mutated"
+	for range 2 {
+		result, err := configkit.Load[mappingFacadeConfig](source)
+		if err != nil {
+			t.Fatal(err)
+		}
+		want := mappingFacadeConfig{Count: ^uint64(0), Items: []string{"one", "two"}, Name: "original"}
+		if !reflect.DeepEqual(result.Config, want) {
+			t.Fatalf("mapping config = %#v, want %#v", result.Config, want)
+		}
+		if sources := result.Sources(); len(sources) != 1 || sources[0].ID != "source-1" || sources[0].Kind != configkit.SourceKindMapping || sources[0].Layer != configkit.LayerBase || sources[0].Path != "" {
+			t.Fatalf("mapping sources = %#v", sources)
+		}
+		info, ok := result.Metadata().Lookup(configkit.Keys("name"))
+		if !ok || len(info.Origin.Locations) != 1 || info.Origin.Locations[0].SourceID != "source-1" || info.Origin.Locations[0].Line != 0 {
+			t.Fatalf("mapping name origin = %#v, %v", info, ok)
+		}
+		fromYAML, err := configkit.Load[mappingFacadeConfig](configkit.Bytes("equivalent", []byte("enabled: false\ncount: 18446744073709551615\noptional: null\nitems: [one, two]\nname: original\n")))
+		if err != nil || !reflect.DeepEqual(result.Config, fromYAML.Config) {
+			t.Fatalf("equivalent YAML = %#v, %v", fromYAML, err)
+		}
+	}
+}
+
+func TestFacadeMappingNullEmptyAndVersion(t *testing.T) {
+	result, err := configkit.Load[mappingFacadeConfig](configkit.Mapping("empty", map[string]any{}))
+	if err != nil || len(result.Sources()) != 1 {
+		t.Fatalf("empty mapping = %#v, %v", result, err)
+	}
+	var nilSequence []any
+	var nilMap map[string]any
+	var checked string
+	result, err = configkit.Load(configkit.Mapping("nullable", map[string]any{
+		"items": nilSequence, "optional": nilMap, "enabled": false, "count": uint64(0),
+	}), configkit.Options[mappingFacadeConfig]{Definition: configkit.Definition[mappingFacadeConfig]{
+		Version: &configkit.VersionRule{Path: configkit.Keys("count"), Check: func(version configkit.Version, validation *configkit.Validation) error {
+			checked = version.Text
+			return nil
+		}},
+	}})
+	if err != nil || checked != "0" || result.Config.Items != nil || result.Config.Optional != nil {
+		t.Fatalf("null and zero mapping = %#v, checked %q, %v", result, checked, err)
+	}
+	info, ok := result.Metadata().Lookup(configkit.Keys("items"))
+	if !ok || !info.Null || !info.Explicit {
+		t.Fatalf("null metadata = %#v, %v", info, ok)
+	}
+}
+
+func TestFacadeMappingImportsUseExplicitContext(t *testing.T) {
+	namespace := configkit.NewFilesystem("bundle", fstest.MapFS{
+		"root/shared.yml": &fstest.MapFile{Data: []byte("name: imported\n")},
+	})
+	source := configkit.Mapping("programmatic", map[string]any{
+		"configkit": map[string]any{"imports": []any{map[string]any{"path": "shared.yml"}}},
+		"enabled":   true,
+	})
+	result, err := configkit.Load(source, configkit.Options[mappingFacadeConfig]{
+		Imports: true, Filesystem: &configkit.FilesystemContext{Root: "root", BaseDir: "root", FS: &namespace},
+	})
+	if err != nil || result.Config.Name != "imported" || !result.Config.Enabled {
+		t.Fatalf("mapping import = %#v, %v", result, err)
+	}
+	if sources := result.Sources(); len(sources) != 2 || sources[0].Kind != configkit.SourceKindMapping || sources[1].Kind != configkit.SourceKindFilesystem || sources[1].Layer != configkit.LayerBase {
+		t.Fatalf("mapping import sources = %#v", sources)
+	}
+	checkMappingCode(t, source, configkit.Options[mappingFacadeConfig]{Imports: true}, configkit.CodeOptionsInvalid)
+	checkMappingCode(t, source, configkit.Options[mappingFacadeConfig]{}, configkit.CodeImportDisabled)
+}
+
+func TestFacadeMappingDeferredValueDiagnostics(t *testing.T) {
+	cycle := map[string]any{}
+	cycle["secret"] = cycle
+	for _, test := range []struct {
+		name   string
+		source configkit.Source
+		want   configkit.Code
+		path   string
+	}{
+		{"nil root", configkit.Mapping("nil", nil), configkit.CodeSourceInvalid, ""},
+		{"bad label", configkit.Mapping("bad\nlabel", map[string]any{}), configkit.CodeSourceInvalid, ""},
+		{"unsupported", configkit.Mapping("bad", map[string]any{"secret": struct{ Value string }{"canary-value"}}), configkit.CodeSourceInvalid, "/secret"},
+		{"nonfinite", configkit.Mapping("bad", map[string]any{"count": math.NaN()}), configkit.CodeSourceInvalid, "/count"},
+		{"cycle", configkit.Mapping("bad", cycle), configkit.CodeSourceInvalid, "/secret"},
+		{"too many bytes", configkit.Mapping("bad", map[string]any{"name": strings.Repeat("x", 8<<20+1)}), configkit.CodeSourceLimitExceeded, "/name"},
+	} {
+		t.Run(test.name, func(t *testing.T) {
+			loadError := checkMappingCode(t, test.source, configkit.Options[mappingFacadeConfig]{}, test.want)
+			diagnostic := loadError.Diagnostics()[0]
+			if diagnostic.Path.String() != test.path || diagnostic.Primary == nil || diagnostic.Primary.SourceID != "source-1" || strings.Contains(diagnostic.Message, "canary-value") {
+				t.Fatalf("diagnostic = %#v", diagnostic)
+			}
+		})
+	}
+}
+
+func checkMappingCode(t *testing.T, source configkit.Source, options configkit.Options[mappingFacadeConfig], want configkit.Code) *configkit.LoadError {
+	t.Helper()
+	_, err := configkit.Load(source, options)
+	loadError, ok := err.(*configkit.LoadError)
+	if !ok || len(loadError.Diagnostics()) == 0 || loadError.Diagnostics()[0].Code != want {
+		t.Fatalf("error = %#v, want %s", err, want)
+	}
+	return loadError
+}

facade_resource_context_test.go

@@ -0,0 +1,221 @@
+package configkit_test
+
+import (
+	"errors"
+	"io/fs"
+	"os"
+	"path"
+	"path/filepath"
+	"strings"
+	"testing"
+	"testing/fstest"
+
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+)
+
+type observedResourceFS struct {
+	files  fstest.MapFS
+	opens  int
+	closed bool
+}
+
+func (f *observedResourceFS) Open(name string) (fs.File, error) {
+	f.opens++
+	if f.closed {
+		return nil, fs.ErrClosed
+	}
+	return f.files.Open(name)
+}
+
+type resourceFacadeConfig struct {
+	Native   string `yaml:"native"`
+	Shared   string `yaml:"shared"`
+	Host     string `yaml:"host"`
+	Selected string `yaml:"selected"`
+}
+
+func TestFacadeSourceContextsFollowOriginsWithoutQueryIO(t *testing.T) {
+	host := t.TempDir()
+	if err := os.WriteFile(filepath.Join(host, "main.yml"), []byte("host: host.txt\n"), 0o600); err != nil {
+		t.Fatal(err)
+	}
+	if err := os.WriteFile(filepath.Join(host, "host.txt"), []byte("host-v1"), 0o600); err != nil {
+		t.Fatal(err)
+	}
+	borrowed := &observedResourceFS{files: fstest.MapFS{
+		"bundle/config/defaults.yml":  &fstest.MapFile{Data: []byte("configkit: {imports: [{path: ../shared.yml}]}\nnative: icon.txt\n")},
+		"bundle/shared.yml":           &fstest.MapFile{Data: []byte("shared: shared.txt\n")},
+		"bundle/overlays/test.yml":    &fstest.MapFile{Data: []byte("selected: overlay.txt\n")},
+		"bundle/config/icon.txt":      &fstest.MapFile{Data: []byte("icon-v1")},
+		"bundle/shared.txt":           &fstest.MapFile{Data: []byte("shared-v1")},
+		"bundle/overlays/overlay.txt": &fstest.MapFile{Data: []byte("overlay-v1")},
+	}}
+	namespace := configkit.NewFilesystem("bundle", borrowed)
+	var resolverContext configkit.ResourceContext
+	result, err := configkit.LoadLayered(configkit.Input{Source: configkit.File(filepath.Join(host, "main.yml"))}, configkit.LayeredOptions[resourceFacadeConfig]{
+		Underlays: []configkit.Underlay{{Inputs: []configkit.Input{{
+			Source: namespace.File("bundle/config/defaults.yml"), Imports: true,
+			Filesystem: &configkit.FilesystemContext{Root: "bundle", FS: &namespace},
+		}}}},
+		Overlay: "test", OverlayFilesystem: &configkit.FilesystemContext{Root: "bundle", BaseDir: "bundle", FS: &namespace},
+		Definition: configkit.Definition[resourceFacadeConfig]{Resolve: func(config *resourceFacadeConfig, resolution *configkit.Resolution) error {
+			before := borrowed.opens
+			var ok bool
+			resolverContext, ok = resolution.SourceContext("source-2")
+			if !ok || resolverContext.BaseDir != "config" || resolverContext.FS == nil {
+				t.Errorf("resolver context = %#v, %v", resolverContext, ok)
+			}
+			if _, ok := resolution.SourceContext("missing"); ok || borrowed.opens != before {
+				t.Error("resolution context query performed I/O or guessed an unknown source")
+			}
+			return nil
+		}},
+	})
+	if err != nil {
+		t.Fatalf("load: %v, diagnostics %#v", err, err.(*configkit.LoadError).Diagnostics())
+	}
+	queriesBefore := borrowed.opens
+	for _, test := range []struct {
+		field, wantBase, wantData string
+	}{
+		{"native", "config", "icon-v1"},
+		{"shared", ".", "shared-v1"},
+		{"selected", "overlays", "overlay-v1"},
+		{"host", ".", "host-v1"},
+	} {
+		origin, ok := result.Metadata().Lookup(configkit.Keys(test.field))
+		if !ok || len(origin.Origin.Locations) != 1 {
+			t.Fatalf("%s origin = %#v, %v", test.field, origin, ok)
+		}
+		context, ok := result.SourceContext(origin.Origin.Locations[0].SourceID)
+		if !ok || context.FS == nil || context.BaseDir != test.wantBase {
+			t.Fatalf("%s context = %#v, %v", test.field, context, ok)
+		}
+		if borrowed.opens != queriesBefore {
+			t.Fatal("result SourceContext query performed filesystem I/O")
+		}
+		resourceName := path.Join(context.BaseDir, map[string]string{
+			"native": result.Config.Native, "shared": result.Config.Shared,
+			"selected": result.Config.Selected, "host": result.Config.Host,
+		}[test.field])
+		data, err := fs.ReadFile(context.FS, resourceName)
+		if err != nil || string(data) != test.wantData {
+			t.Fatalf("%s resource = %q, %v", test.field, data, err)
+		}
+		queriesBefore = borrowed.opens
+	}
+	if _, ok := result.SourceContext(""); ok {
+		t.Fatal("empty source ID returned a context")
+	}
+	var nilResult *configkit.Result[resourceFacadeConfig]
+	if _, ok := nilResult.SourceContext("source-2"); ok {
+		t.Fatal("nil result returned a context")
+	}
+	if _, err := fs.ReadFile(resolverContext.FS, "../shared.txt"); !errors.Is(err, fs.ErrInvalid) {
+		t.Fatalf("native root escape = %v", err)
+	}
+	borrowed.files["bundle/config/icon.txt"].Data = []byte("icon-v2")
+	data, err := fs.ReadFile(resolverContext.FS, "config/icon.txt")
+	if err != nil || string(data) != "icon-v2" {
+		t.Fatalf("updated native resource = %q, %v", data, err)
+	}
+	borrowed.closed = true
+	if result.Config.Native != "icon.txt" {
+		t.Fatal("closing caller filesystem altered loaded configuration")
+	}
+	if _, err := fs.ReadFile(resolverContext.FS, "config/icon.txt"); !errors.Is(err, fs.ErrClosed) {
+		t.Fatalf("closed caller filesystem error = %v", err)
+	}
+}
+
+func TestFacadeHostContextSurvivesConfigurationDeletion(t *testing.T) {
+	root := t.TempDir()
+	main := filepath.Join(root, "main.yml")
+	resource := filepath.Join(root, "asset.txt")
+	if err := os.WriteFile(main, []byte("native: asset.txt\n"), 0o600); err != nil {
+		t.Fatal(err)
+	}
+	if err := os.WriteFile(resource, []byte("first"), 0o600); err != nil {
+		t.Fatal(err)
+	}
+	result, err := configkit.Load[resourceFacadeConfig](configkit.File(main))
+	if err != nil {
+		t.Fatal(err)
+	}
+	context, ok := result.SourceContext("source-1")
+	if !ok || context.BaseDir != "." {
+		t.Fatalf("host context = %#v, %v", context, ok)
+	}
+	if err := os.Remove(main); err != nil {
+		t.Fatal(err)
+	}
+	if err := os.WriteFile(resource, []byte("second"), 0o600); err != nil {
+		t.Fatal(err)
+	}
+	data, err := fs.ReadFile(context.FS, path.Join(context.BaseDir, result.Config.Native))
+	if err != nil || string(data) != "second" || result.Config.Native != "asset.txt" {
+		t.Fatalf("resource after source deletion = %q, %v", data, err)
+	}
+	if _, err := fs.ReadFile(context.FS, "../asset.txt"); !errors.Is(err, fs.ErrInvalid) {
+		t.Fatalf("invalid host path = %v", err)
+	}
+	if err := os.Remove(resource); err != nil {
+		t.Fatal(err)
+	}
+	if _, err := fs.ReadFile(context.FS, "asset.txt"); !errors.Is(err, fs.ErrNotExist) {
+		t.Fatalf("missing later resource = %v", err)
+	}
+	outside := filepath.Join(t.TempDir(), "outside.txt")
+	if err := os.WriteFile(outside, []byte("outside"), 0o600); err != nil {
+		t.Fatal(err)
+	}
+	if err := os.Symlink(outside, filepath.Join(root, "escape")); err == nil {
+		if _, err := fs.ReadFile(context.FS, "escape"); !errors.Is(err, fs.ErrPermission) {
+			t.Fatalf("host symlink escape = %v", err)
+		}
+	}
+}
+
+func TestFacadeSyntheticSourceContextsAndContextlessSources(t *testing.T) {
+	namespace := configkit.NewFilesystem("bundle", fstest.MapFS{
+		"bundle/config/icon.txt": &fstest.MapFile{Data: []byte("icon")},
+	})
+	context := &configkit.FilesystemContext{Root: "bundle", BaseDir: "bundle/config", FS: &namespace}
+	for _, test := range []struct {
+		name   string
+		source configkit.Source
+	}{
+		{"bytes", configkit.Bytes("memory", []byte("native: icon.txt\n"))},
+		{"reader", configkit.Reader("stream", strings.NewReader("native: icon.txt\n"))},
+		{"mapping", configkit.Mapping("values", map[string]any{"native": "icon.txt"})},
+	} {
+		t.Run(test.name, func(t *testing.T) {
+			result, err := configkit.Load(test.source, configkit.Options[resourceFacadeConfig]{Filesystem: context})
+			if err != nil {
+				t.Fatal(err)
+			}
+			resource, ok := result.SourceContext("source-1")
+			if !ok || resource.BaseDir != "config" {
+				t.Fatalf("synthetic context = %#v, %v", resource, ok)
+			}
+			data, err := fs.ReadFile(resource.FS, path.Join(resource.BaseDir, result.Config.Native))
+			if err != nil || string(data) != "icon" {
+				t.Fatalf("synthetic resource = %q, %v", data, err)
+			}
+		})
+	}
+	result, err := configkit.Load[resourceFacadeConfig](configkit.Bytes("plain", []byte("native: none\n")))
+	if err != nil {
+		t.Fatal(err)
+	}
+	if _, ok := result.SourceContext("source-1"); ok {
+		t.Fatal("contextless byte source returned a context")
+	}
+	result, err = configkit.Load(configkit.NoSource(), configkit.Options[resourceFacadeConfig]{Overrides: []configkit.Override{{Path: configkit.Keys("native"), Value: "from-cli", Flag: "--native"}}})
+	if err != nil {
+		t.Fatal(err)
+	}
+	if _, ok := result.SourceContext("source-1"); ok {
+		t.Fatal("CLI source returned a context")
+	}
+}

facade_underlay_origins_test.go

@@ -0,0 +1,107 @@
+package configkit_test
+
+import (
+	"reflect"
+	"testing"
+	"testing/fstest"
+
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+)
+
+func TestUnderlaySequenceDescendantOrigins(t *testing.T) {
+	for _, later := range []bool{false, true} {
+		name := "first tier"
+		if later {
+			name = "later tier"
+		}
+		t.Run(name, func(t *testing.T) {
+			bundle := configkit.NewFilesystem("bundle", fstest.MapFS{
+				"main.yml":  &fstest.MapFile{Data: []byte("configkit: {imports: [{path: items.yml}]}\n")},
+				"items.yml": &fstest.MapFile{Data: []byte("items: [{name: first, nested: [false]}]\n")},
+			})
+			tiers := []configkit.Underlay{}
+			if later {
+				tiers = append(tiers, configkit.Underlay{Inputs: []configkit.Input{{Source: configkit.Mapping("lower", map[string]any{"other": true})}}})
+			}
+			tiers = append(tiers, configkit.Underlay{Inputs: []configkit.Input{{Source: bundle.File("main.yml"), Imports: true}}})
+			paths := []string{"/items", "/items/0", "/items/0/name", "/items/0/nested", "/items/0/nested/0"}
+			entry := map[string]configkit.Origin{}
+			result, err := configkit.LoadLayered[map[string]any](configkit.Input{Source: configkit.Mapping("main", map[string]any{"main": true})}, configkit.LayeredOptions[map[string]any]{
+				Underlays: tiers,
+				Definition: configkit.Definition[map[string]any]{Resolve: func(_ *map[string]any, resolution *configkit.Resolution) error {
+					for _, pointer := range paths {
+						path, _ := configkit.ParsePath(pointer)
+						info, ok := resolution.InputInfo(path)
+						if !ok {
+							t.Errorf("missing resolver input %s", pointer)
+						}
+						entry[pointer] = info.Origin
+					}
+					return nil
+				}},
+			})
+			if err != nil {
+				t.Fatal(err)
+			}
+			var sourceID string
+			for _, source := range result.Sources() {
+				if source.Path == "items.yml" {
+					sourceID = source.ID
+				}
+			}
+			if sourceID == "" {
+				t.Fatal("missing imported source")
+			}
+			for _, pointer := range paths {
+				path, _ := configkit.ParsePath(pointer)
+				info, ok := result.Metadata().Lookup(path)
+				if !ok || info.Origin.Layer != configkit.LayerUnderlay || len(info.Origin.Locations) != 1 || info.Origin.Locations[0].SourceID != sourceID {
+					t.Errorf("%s origin = %+v", pointer, info.Origin)
+				}
+				if !reflect.DeepEqual(entry[pointer], info.Origin) {
+					t.Errorf("%s resolver origin differs", pointer)
+				}
+				explanation, ok := result.Explain(path)
+				if !ok || !reflect.DeepEqual(explanation.Origin, info.Origin) {
+					t.Errorf("%s explanation origin differs", pointer)
+				}
+				history := result.Metadata().History(path)
+				if len(history) == 0 || !reflect.DeepEqual(history[len(history)-1].Origin, info.Origin) {
+					t.Errorf("%s history = %+v", pointer, history)
+				}
+			}
+		})
+	}
+}
+
+func TestUnderlayHistoryRetainsLaterMappingContributors(t *testing.T) {
+	result, err := configkit.LoadLayered[map[string]any](configkit.Input{Source: configkit.NoSource()}, configkit.LayeredOptions[map[string]any]{Underlays: []configkit.Underlay{
+		{Inputs: []configkit.Input{{Source: configkit.Mapping("one", map[string]any{"x": 1})}}},
+		{Inputs: []configkit.Input{{Source: configkit.Mapping("two", map[string]any{"x": map[string]any{}})}}},
+		{Inputs: []configkit.Input{{Source: configkit.Mapping("three", map[string]any{"x": map[string]any{"y": 2}})}}},
+	}})
+	if err != nil {
+		t.Fatal(err)
+	}
+	path := configkit.Keys("x")
+	info, _ := result.Metadata().Lookup(path)
+	wantOrigin := configkit.Origin{Layer: configkit.LayerUnderlay, Locations: []configkit.Location{{SourceID: "source-2"}, {SourceID: "source-3"}}}
+	if !reflect.DeepEqual(info.Origin, wantOrigin) {
+		t.Fatalf("effective origin = %+v, want %+v", info.Origin, wantOrigin)
+	}
+	history := result.Metadata().History(path)
+	if len(history) != 3 || !reflect.DeepEqual(history[len(history)-1].Origin, info.Origin) {
+		t.Fatalf("history = %+v, effective origin = %+v", history, info.Origin)
+	}
+	explanation, ok := result.Explain(path)
+	if !ok || !reflect.DeepEqual(explanation.Origin, info.Origin) {
+		t.Fatal("explanation and metadata disagree")
+	}
+	if len(explanation.History) != 3 {
+		t.Fatalf("explanation history = %+v", explanation.History)
+	}
+	last := explanation.History[len(explanation.History)-1].Origin
+	if last.Layer != configkit.LayerUnderlay || len(last.Locations) != 1 || last.Locations[0].SourceID != "source-3" {
+		t.Fatalf("last explanation origin = %+v", last)
+	}
+}

facade_version_test.go

@@ -0,0 +1,66 @@
+package configkit_test
+
+import (
+	"errors"
+	"strings"
+	"testing"
+
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+)
+
+type versionCountingReader struct {
+	*strings.Reader
+	reads int
+}
+
+func (r *versionCountingReader) Read(data []byte) (int, error) {
+	r.reads++
+	return r.Reader.Read(data)
+}
+
+func TestFacadeRejectsMissingVersionCheckerBeforeReading(t *testing.T) {
+	t.Parallel()
+	type configuration struct {
+		Version string `yaml:"version"`
+	}
+	reader := &versionCountingReader{Reader: strings.NewReader("version: v1\n")}
+	source := configkit.Reader("version.yml", reader)
+	var defaults, resolutions, validations, checks int
+	options := configkit.Options[configuration]{Definition: configkit.Definition[configuration]{
+		Version:  &configkit.VersionRule{Path: configkit.Keys("version")},
+		Defaults: func() configuration { defaults++; return configuration{} },
+		Resolve:  func(*configuration, *configkit.Resolution) error { resolutions++; return nil },
+		Validate: func(*configuration, *configkit.Validation) { validations++ },
+	}}
+	result, err := configkit.Load(source, options)
+	var loadError *configkit.LoadError
+	if result != nil || !errors.As(err, &loadError) {
+		t.Fatalf("missing checker: result = %v, error = %v", result, err)
+	}
+	diagnostics := loadError.Diagnostics()
+	if len(diagnostics) != 1 || diagnostics[0].Code != configkit.CodeOptionsInvalid {
+		t.Fatalf("diagnostics = %v", diagnostics)
+	}
+	if reader.reads != 0 || defaults != 0 || resolutions != 0 || validations != 0 {
+		t.Fatalf("invalid options performed work: reads=%d defaults=%d resolve=%d validate=%d", reader.reads, defaults, resolutions, validations)
+	}
+	options.Definition.Version.Check = func(version configkit.Version, validation *configkit.Validation) error {
+		checks++
+		if version != (configkit.Version{Present: true, Text: "v1"}) {
+			t.Errorf("version = %#v", version)
+		}
+		validation.Warning(configkit.Keys("version"), "version accepted")
+		return nil
+	}
+	result, err = configkit.Load(source, options)
+	if err != nil || result == nil || result.Config.Version != "v1" {
+		t.Fatalf("reuse with checker: result = %v, error = %v", result, err)
+	}
+	if checks != 1 || defaults != 1 || resolutions != 1 || validations != 1 {
+		t.Fatalf("callback counts: check=%d defaults=%d resolve=%d validate=%d", checks, defaults, resolutions, validations)
+	}
+	diagnostics = result.Diagnostics()
+	if len(diagnostics) != 1 || diagnostics[0].Code != configkit.CodeVersionWarning {
+		t.Fatalf("version callback diagnostics = %v", diagnostics)
+	}
+}

go.mod

@@ -0,0 +1,5 @@
+module gitea.maximumdirect.net/eric/ConfigKit
+
+go 1.25.0
+
+require go.yaml.in/yaml/v4 v4.0.0-rc.6

go.sum

@@ -0,0 +1,2 @@
+go.yaml.in/yaml/v4 v4.0.0-rc.6 h1:1h7H1ohdUh93/FyE4YaDa1Zh64K6VVbjF4K6WUxMtH4=
+go.yaml.in/yaml/v4 v4.0.0-rc.6/go.mod h1:aZqd9kCMsGL7AuUv/m/PvWLdg5sjJsZ4oHDEnfPPfY0=

import_boundary_test.go

@@ -0,0 +1,59 @@
+package configkit
+
+import (
+	"go/parser"
+	"go/token"
+	"io/fs"
+	"path/filepath"
+	"strconv"
+	"strings"
+	"testing"
+)
+
+func TestDependencyImportBoundary(t *testing.T) {
+	t.Parallel()
+
+	err := filepath.WalkDir(".", func(path string, entry fs.DirEntry, walkErr error) error {
+		if walkErr != nil {
+			return walkErr
+		}
+		if entry.IsDir() {
+			if path == ".git" {
+				return filepath.SkipDir
+			}
+			return nil
+		}
+		if filepath.Ext(path) != ".go" {
+			return nil
+		}
+		file, err := parser.ParseFile(token.NewFileSet(), path, nil, parser.ImportsOnly)
+		if err != nil {
+			return err
+		}
+		for _, imported := range file.Imports {
+			importPath, err := strconv.Unquote(imported.Path.Value)
+			if err != nil {
+				return err
+			}
+			if strings.HasPrefix(importPath, "go.yaml.in/yaml/") && !strings.HasPrefix(filepath.ToSlash(path), "internal/yaml/") {
+				t.Errorf("%s imports private YAML dependency %s", path, importPath)
+			}
+			if strings.HasPrefix(importPath, "github.com/google/go-cmp/") && !strings.HasSuffix(path, "_test.go") {
+				t.Errorf("%s imports test-only dependency %s", path, importPath)
+			}
+			production := !strings.HasSuffix(path, "_test.go")
+			rootProduction := production && filepath.Dir(path) == "."
+			internalProduction := production && strings.HasPrefix(filepath.ToSlash(path), "internal/")
+			if rootProduction && strings.HasPrefix(importPath, "gitea.maximumdirect.net/eric/ConfigKit/internal/") && importPath != "gitea.maximumdirect.net/eric/ConfigKit/internal/engine" {
+				t.Errorf("%s bypasses the engine boundary through %s", path, importPath)
+			}
+			if internalProduction && importPath == "gitea.maximumdirect.net/eric/ConfigKit" {
+				t.Errorf("%s imports the public root package", path)
+			}
+		}
+		return nil
+	})
+	if err != nil {
+		t.Fatal(err)
+	}
+}

inspection.go

@@ -0,0 +1,71 @@
+package configkit
+
+import (
+	"io"
+
+	"gitea.maximumdirect.net/eric/ConfigKit/internal/engine"
+)
+
+// ValueSnapshot is a detached, deterministic YAML representation of one value.
+// Present distinguishes absence or deletion from an explicit null value.
+type ValueSnapshot struct {
+	Present  bool
+	Redacted bool
+	YAML     string
+}
+
+// ValueChange describes one explicit definition or audited domain operation.
+type ValueChange struct {
+	Before       ValueSnapshot
+	After        ValueSnapshot
+	Origin       Origin
+	Reasons      []string
+	Dependencies []Path
+}
+
+// SecretReferenceInfo describes a successfully resolved effective reference.
+// Name is the environment-variable name, never its value.
+type SecretReferenceInfo struct {
+	Name string
+}
+
+// Explanation is a detached safe account of one effective or historical path.
+type Explanation struct {
+	Path            Path
+	Effective       ValueSnapshot
+	Origin          Origin
+	History         []ValueChange
+	SecretReference *SecretReferenceInfo
+}
+
+// Explain returns safe effective and chronological values for a known final or
+// historical path. Structural inheritance appears between source applications
+// and typed reconciliation. Unknown and malformed paths return false.
+func (r *Result[T]) Explain(path Path) (Explanation, bool) {
+	if r == nil {
+		return Explanation{}, false
+	}
+	value, ok := r.inspection.Explain(toEnginePath(path))
+	return fromEngineExplanation(value), ok
+}
+
+// WriteEffective writes deterministic redacted YAML from the frozen resolved
+// snapshot. The output is intended for inspection and is not promised reloadable.
+// Writer errors, including short writes, are returned and may leave partial output.
+func (r *Result[T]) WriteEffective(output io.Writer) error {
+	if r == nil {
+		var inspection *engine.Inspection
+		return inspection.WriteEffective(output)
+	}
+	return r.inspection.WriteEffective(output)
+}
+
+// WriteExplanation writes a deterministic human-readable rendering of Explain.
+// Unknown paths produce no output. Writer failures may leave partial output.
+func (r *Result[T]) WriteExplanation(output io.Writer, path Path) error {
+	if r == nil {
+		var inspection *engine.Inspection
+		return inspection.WriteExplanation(output, toEnginePath(path))
+	}
+	return r.inspection.WriteExplanation(output, toEnginePath(path))
+}

internal/document/document.go

@@ -0,0 +1,65 @@
+// Package document defines ConfigKit's parser-independent configuration tree.
+package document
+
+// Kind identifies a configuration node category.
+type Kind uint8
+
+const (
+	Mapping Kind = iota + 1
+	Sequence
+	String
+	Boolean
+	Number
+	Null
+)
+
+// Location identifies a source coordinate. Root depth and unavailable coordinates
+// are represented independently by callers; line and column are one-based when set.
+type Location struct {
+	SourceID string
+	Line     int
+	Column   int
+}
+
+// Entry is an ordered mapping entry with separate key and value locations.
+type Entry struct {
+	Key           string
+	KeyLocation   Location
+	ValueLocation Location
+	Value         *Node
+}
+
+// Node is ConfigKit's owned configuration representation. Number Text retains its
+// exact validated decimal spelling; Boolean Text is "true" or "false".
+type Node struct {
+	// Sensitive preserves field classification from concrete typed projections.
+	// It is metadata, not part of the configuration value or emitted YAML.
+	Sensitive bool
+	Kind      Kind
+	Location  Location
+	Text      string
+	Mapping   []Entry
+	Sequence  []*Node
+}
+
+// Clone returns a detached copy of a node tree.
+func Clone(node *Node) *Node {
+	if node == nil {
+		return nil
+	}
+	cloned := *node
+	if node.Mapping != nil {
+		cloned.Mapping = make([]Entry, len(node.Mapping))
+		for i, entry := range node.Mapping {
+			cloned.Mapping[i] = entry
+			cloned.Mapping[i].Value = Clone(entry.Value)
+		}
+	}
+	if node.Sequence != nil {
+		cloned.Sequence = make([]*Node, len(node.Sequence))
+		for i, child := range node.Sequence {
+			cloned.Sequence[i] = Clone(child)
+		}
+	}
+	return &cloned
+}

internal/engine/assembly_bench_test.go

@@ -0,0 +1,119 @@
+package engine
+
+import (
+	"strconv"
+	"testing"
+
+	"gitea.maximumdirect.net/eric/ConfigKit/internal/document"
+)
+
+func BenchmarkComposeWideMappings(b *testing.B) {
+	for _, width := range []int{128, 256, 512} {
+		b.Run(strconv.Itoa(width), func(b *testing.B) {
+			left := benchmarkCatalog("source-1", 0, width)
+			right := benchmarkCatalog("source-2", width, width)
+			b.ReportAllocs()
+			b.ResetTimer()
+			for range b.N {
+				if _, diagnostics := composeDocuments(left, right); len(diagnostics) != 0 {
+					b.Fatal(diagnostics)
+				}
+			}
+		})
+	}
+}
+
+func BenchmarkOverlayRecursiveMappings(b *testing.B) {
+	for _, width := range []int{128, 256, 512} {
+		b.Run(strconv.Itoa(width), func(b *testing.B) {
+			base, diagnostics := composeDocuments(benchmarkCatalog("source-1", 0, width))
+			if len(diagnostics) != 0 {
+				b.Fatal(diagnostics)
+			}
+			overlay := benchmarkCatalog("source-2", width/2, width)
+			b.ReportAllocs()
+			b.ResetTimer()
+			for range b.N {
+				if _, diagnostics := overlayDocuments(base, overlay); len(diagnostics) != 0 {
+					b.Fatal(diagnostics)
+				}
+			}
+		})
+	}
+}
+
+func BenchmarkOverlayManyApplications(b *testing.B) {
+	for _, count := range []int{32, 64, 128} {
+		inputs := make([]*document.Node, count)
+		for index := range inputs {
+			inputs[index] = benchmarkCatalog("source-2", index, 1)
+		}
+		benchmarkOverlayApplications(b, count, inputs)
+	}
+}
+
+func BenchmarkOverlayRepeatedReplacement(b *testing.B) {
+	for _, count := range []int{32, 64, 128} {
+		inputs := make([]*document.Node, count)
+		for index := range inputs {
+			location := document.Location{SourceID: "source-2"}
+			value := &document.Node{Kind: document.String, Text: "replacement", Location: location}
+			if index%2 == 0 {
+				value = &document.Node{Kind: document.Mapping, Location: location, Mapping: []document.Entry{{
+					Key: "enabled", Value: &document.Node{Kind: document.Boolean, Text: "false", Location: location},
+				}}}
+			}
+			inputs[index] = &document.Node{Kind: document.Mapping, Location: location, Mapping: []document.Entry{{
+				Key: "catalog", Value: &document.Node{Kind: document.Mapping, Location: location, Mapping: []document.Entry{{
+					Key: "item-0", Value: value,
+				}}},
+			}}}
+		}
+		benchmarkOverlayApplications(b, count, inputs)
+	}
+}
+
+func benchmarkOverlayApplications(b *testing.B, count int, inputs []*document.Node) {
+	base, diagnostics := composeDocuments(benchmarkCatalog("source-1", 0, 1))
+	if len(diagnostics) != 0 {
+		b.Fatal(diagnostics)
+	}
+	for _, mode := range []string{"owned", "copy-preserving"} {
+		b.Run(mode+"/"+strconv.Itoa(count), func(b *testing.B) {
+			b.ReportAllocs()
+			b.ResetTimer()
+			for range b.N {
+				if mode == "owned" {
+					assembly := newAssemblyAccumulator(cloneComposedDocument(base))
+					for _, input := range inputs {
+						if diagnostics := assembly.applyOverlay(input, nil, nil, LayerOverlay); len(diagnostics) != 0 {
+							b.Fatal(diagnostics)
+						}
+					}
+					continue
+				}
+				current := base
+				for _, input := range inputs {
+					current, diagnostics = overlayDocuments(current, input)
+					if len(diagnostics) != 0 {
+						b.Fatal(diagnostics)
+					}
+				}
+			}
+		})
+	}
+}
+
+func benchmarkCatalog(source string, first, width int) *document.Node {
+	location := document.Location{SourceID: source}
+	entries := make([]document.Entry, width)
+	for index := range entries {
+		entries[index] = document.Entry{
+			Key:   "item-" + strconv.Itoa(first+index),
+			Value: &document.Node{Kind: document.Mapping, Location: location, Mapping: []document.Entry{{Key: "enabled", Value: &document.Node{Kind: document.Boolean, Text: "true", Location: location}}}},
+		}
+	}
+	return &document.Node{Kind: document.Mapping, Location: location, Mapping: []document.Entry{{
+		Key: "catalog", Value: &document.Node{Kind: document.Mapping, Location: location, Mapping: entries},
+	}}}
+}