Clarify PromptKit capture and preparation behavior

This commit is contained in:
2026-11-18 00:30:24 +00:00
parent 0663fe566a
commit 3f9727d5e8
5 changed files with 25 additions and 13 deletions

View File

@@ -358,8 +358,10 @@ profiles:
service_tier: null
~~~
The `promptkit.local_backend` configuration registers that conventional
backend. Prompt overlays use the same recursive source composition; for
The backend can be declared as `backends.local` in the operator source or
registered through the optional `promptkit.local_backend` convenience object.
The [source precedence](#native-promptkit-sources-and-migration) applies when
both contribute. Prompt overlays use the same recursive source composition; for
example, this changes one output setting while retaining the other embedded
definition fields:
@@ -372,8 +374,10 @@ prompts:
~~~
Sequences such as prompt messages are replaced as a whole when overridden.
Prompt and schema definitions remain subject to final effective validation at
engine construction.
Engine construction validates final effective prompt definitions and captures
message files and static templates. Request preparation loads response schemas
and resolves request variables and input artifacts. Profile preflight needs no
transcript, credential value, or provider call, but can read prompt-content files.
`notarius config validate --pipeline <id>` resolves the selected pipeline and
inspects every explicit effective profile without contacting a provider or