Plan ConfigKit overlays for testing with cheaper models
This commit is contained in:
@@ -57,9 +57,10 @@ avoid duplicate model, endpoint, credential, or timeout definitions with competi
|
||||
precedence.
|
||||
|
||||
Keep ConfigKit application configuration distinct from PromptKit execution profiles.
|
||||
In particular, optional ConfigKit configuration profiles and PromptKit execution
|
||||
profiles are different concepts. Select an explicit profile-ownership model;
|
||||
complete Audita-owned execution profiles are the initial recommendation, with
|
||||
ConfigKit v0.4.0 calls its optional configuration layers overlays. Enable selected
|
||||
overlays for testing as specified in the [ConfigKit roadmap](configkit.md#selected-overlays-for-testing);
|
||||
these select application settings, including PromptKit execution profiles.
|
||||
Select an explicit profile-ownership model; complete Audita-owned execution profiles are the initial recommendation, with
|
||||
catalog-driven selection a deliberate alternative.
|
||||
|
||||
Capacity needs are simple: protect local backends from exceeding their available
|
||||
@@ -103,7 +104,8 @@ ConfigKit-facing settings around the old LLM runtime only to redesign them later
|
||||
Implement the agreed application configuration contract following the
|
||||
[ConfigKit roadmap](configkit.md). Retire legacy environment overlays and obsolete
|
||||
CLI/configuration conventions, update maintained examples and canonical references,
|
||||
and begin the combined migration guide.
|
||||
and begin the combined migration guide. Include the selected testing-overlay path
|
||||
and its offline integration evidence from the ConfigKit roadmap.
|
||||
|
||||
If the existing LLM runtime remains temporarily during this stage, keep translation
|
||||
into it small and explicitly transitional. Do not preserve its old settings merely
|
||||
|
||||
Reference in New Issue
Block a user