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

Document PromptKit request validation

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-12 22:25:43 +00:00
parent be8bd9c1ea
commit 88d4059e8d
10 changed files with 219 additions and 79 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
docs/internal/overview.md
View File

@@ -48,11 +48,13 @@ acquisitions or comparison callback.
`integrations/ckprompt` owns PromptKit engine loading, configuration-scope
adaptation and native comparison, plus optional prompt/profile catalogs, named
inspection, and native requirements discovery. It uses public core and ckconfig
contracts plus PromptKit's public APIs. It does not add a configuration family
when its declaration is installed; callers compose `ckprompt.ConfigScope` with
`ckconfig.Command` separately when they want configuration operations alongside
PromptKit commands.
inspection, native requirements discovery, and concrete request validation.
Validation delegates request preparation to PromptKit and is independently
opted into a suite. It uses public core and ckconfig contracts plus PromptKit's
public APIs. It does not add a configuration family when its declaration is
installed; callers compose `ckprompt.ConfigScope` with `ckconfig.Command`
separately when they want configuration operations alongside PromptKit
commands.
The three maintained consumers live at `examples/core`,
`integrations/ckconfig/examples/simple`, and
@@ -67,7 +69,9 @@ graph isolation.
ConfigKit owns configuration decoding, validation, source history, and path
explanations. PromptKit owns its captured engine configuration, prompt
definitions, profile inheritance, and named inspection semantics. CommandKit
adapts those public contracts without maintaining parallel schemas or invoking
prompt execution. Application loaders and domain behavior remain application
owned.
definitions, profile inheritance, named inspection, requirements discovery,
and concrete request validation semantics. CommandKit adapts those public
contracts without maintaining parallel schemas or invoking model generation.
Native request validation may load resources and artifacts, render messages,
and perform applicable configuration or credential checks through PromptKit.
Application loaders and domain behavior remain application owned.