Update documentation for PromptKit adoption

This commit is contained in:
2026-11-18 19:25:54 +00:00
parent a2205db152
commit 50c65adac4
16 changed files with 270 additions and 347 deletions

View File

@@ -50,24 +50,24 @@ inventory; [adapter internals](../internal/adapters.md) and
## Framework And Application Boundaries
Scriptorium consumes
[Promptkit v0.12.0](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.12.0/docs/consumers/pkg-promptkit.md)
[PromptKit v0.23.2](https://forge.maximumdirect.net/base-layer/promptkit/src/commit/382ccfb14b9630fd8f48c8364dbe2b6159637d71/docs/consumers/pkg-promptkit.md)
through its supported public root package. Promptkit owns prompt execution,
preparation, prompt and profile formats, built-in profiles, model-client
behavior, validation, and framework defaults. Scriptorium owns application
configuration, executable CLI and HTTP adapters, prepared-run and
definition-inspection presentation, captured-configuration inspection
exposure, process behavior, and HTTP deployment policy. The [format
reference](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.12.0/docs/formats.md)
and [outbound integration contract](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.12.0/docs/integrations/openai-compatible-chat.md)
reference](https://forge.maximumdirect.net/base-layer/promptkit/src/commit/382ccfb14b9630fd8f48c8364dbe2b6159637d71/docs/formats.md)
and [outbound integration contract](https://forge.maximumdirect.net/base-layer/promptkit/src/commit/382ccfb14b9630fd8f48c8364dbe2b6159637d71/docs/integrations/openai-compatible-chat.md)
remain Promptkit's contracts.
Scriptorium uses ConfigKit v1.2.0 for strict application YAML decoding,
Scriptorium uses ConfigKit v1.2.1 for strict application YAML decoding,
resolution, and validation flow. Scriptorium retains its application schema,
defaults, normalization, validation rules, source selection, and CLI override
mapping. Promptkit uses its own ConfigKit v0.5.0 dependency to decode and
assemble framework sources under Promptkit's schema and format contract; Scriptorium selects
the inputs but does not parse Promptkit definitions. These ConfigKit generations
are loading mechanisms, not owners of either domain schema or HTTP artifact
mapping. PromptKit uses the same ConfigKit generation to decode and assemble
framework sources under its separate schema and format contract; Scriptorium
selects the inputs but does not parse PromptKit definitions. ConfigKit is a
loading mechanism, not the owner of either domain schema or HTTP artifact
containment. The [configuration contract](../config.md) owns externally
observable application behavior, while Promptkit owns framework formats.