Document native application configuration adoption

This commit is contained in:
2026-11-17 22:15:10 +00:00
parent 79dfe0a3ef
commit 2c3d8e4c8b
11 changed files with 118 additions and 67 deletions

View File

@@ -61,13 +61,13 @@ reference](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.12.0/docs/f
and [outbound integration contract](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.12.0/docs/integrations/openai-compatible-chat.md)
remain Promptkit's contracts.
Scriptorium uses ConfigKit v0.5.0 for strict application YAML decoding,
Scriptorium uses ConfigKit v1.2.0 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 also uses ConfigKit to decode and assemble framework
sources under Promptkit's own schema and format contract; Scriptorium selects
the inputs but does not parse Promptkit definitions. ConfigKit is the shared
loading mechanism, not the owner of either domain schema or HTTP artifact
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
containment. The [configuration contract](../config.md) owns externally
observable application behavior, while Promptkit owns framework formats.