base-layer/promptkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 2 Wiki Activity

Document recorded configuration normalization

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-03 03:32:59 +00:00
parent 43abbcb414
commit 855aae6daa
7 changed files with 52 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/roadmap/field-normalization.md
View File

@@ -2,8 +2,8 @@
## Status And Purpose
Planned; implementation has not started. ConfigKit v1.1.0 is released, while
PromptKit currently depends on v1.0.0.
Implemented: PromptKit uses ConfigKit v1.1.0 and records the selected field
normalizations and queue default in its resolved configuration.
Move PromptKit's existing configuration-time normalization and derived defaults
into ConfigKit's recorded application resolution. Configuration inspection should
@@ -15,13 +15,13 @@ The benefit is a more useful inspection view and removal of the parallel
interpreted configuration maintained for execution. This is a focused loading
change, not a new configuration format, normalization policy, or execution API.
## Current Baseline
## Historical Baseline
PromptKit already uses identified lists for backends, profiles, and prompts at
the root and within named collections. Six ConfigKit identity registrations
cover those destinations. This roadmap does not repeat that migration.
The configuration adapter's `Definition.Resolve` currently captures input
At the baseline, the configuration adapter's `Definition.Resolve` captured input
presence information. During validation, `interpretConfiguration` constructs
detached backend, profile, and prompt interpretations and applies normalization
and a conditional backend queue default. Runtime construction uses those
@@ -34,7 +34,7 @@ ConfigKit v1.0.0. Such a record would replace the effective origins of unchanged
fields, including `content_file`, whose origin selects the filesystem and
directory used to load message text.
The current behavior is documented in the [format reference](../formats.md) and
The implemented behavior is documented in the [format reference](../formats.md) and
[source-loading implementation](../internal/sources.md). The
[configuration ownership decision](../adr/0001-configuration-boundary.md)
continues to govern the division of responsibility: ConfigKit owns composition;

4
docs/roadmap/implementation.md
View File

@@ -268,3 +268,7 @@ construction; all selected transformations have field-level records; unchanged
resource origins and runtime semantics are preserved; tests and documentation
cover the intentional inspection change. There are no unresolved product
decisions or upstream publication steps required by this plan.
Completion: current guides and the next release note describe recorded effective
normalization and its limits. The race-enabled full suite, vet, and all three
example commands passed with Go 1.27.0; the full diff and formatting were reviewed.