Plan ConfigKit overlays for testing with cheaper models

This commit is contained in:
2026-09-23 23:04:46 +00:00
parent 228087dec8
commit 187dc4cb1c
4 changed files with 100 additions and 20 deletions

View File

@@ -8,6 +8,11 @@ scope; [decisions, evidence, limitations, and handoff](library-boundary-findings
record the outcome. The [executable prototype](../../examples/library-adoption/README.md)
is isolated from production. No publication or upstream changes were made.
**Subsequent scope decision:** Enable ConfigKit v0.4.0 selected overlays for testing
in the next configuration unit. The [overlay plan](configkit.md#selected-overlays-for-testing)
supersedes the original optional-feature exclusion below; the completed prototype
has not yet exercised overlays.
## Objective
Define and prove the boundary between Audita, ConfigKit, and PromptKit before
@@ -80,7 +85,7 @@ Resolve these design decisions explicitly:
| Role selection and inheritance | Specify how proposal and validation choose profiles, including omission and any inheritance. Do not inherit old behavior solely for compatibility. |
| Credentials | Prefer one ConfigKit-owned secret-resolution path passed through PromptKit's supported request credential field. Define backend/profile credential association and avoid competing environment lookups. Validate this against profile requirements. |
| Retry, repair, and deadlines | Assign one owner and explicit defaults for each control. Use positive structural-repair defaults and document combined limits and total-operation scope. |
| Optional library features | Leave ConfigKit imports, configuration profiles, and secret-directory bootstrap out unless a concrete requirement is identified. These are separate from PromptKit execution profiles. |
| Optional library features | The original prototype omitted imports, selected configuration layers, and secret-directory bootstrap. Selected overlays are now planned for testing; see the [overlay plan](configkit.md#selected-overlays-for-testing). Imports and secret-directory bootstrap remain out. |
| Inspection | Define effective configuration and selected-profile inspection without implying that one library's snapshot contains the other's complete state. |
Choose concrete field names, example values, defaults, units, and omission/null/zero