Record intentional editorial acceptance across modules
This commit is contained in:
@@ -17,6 +17,13 @@ supplies the embedded instruction fragments for those names. Processing supplies
|
||||
Audita's response-schema contract separately.
|
||||
The operator's prompt definition controls which variables its template uses.
|
||||
|
||||
Proposal focus and validator acceptance intentionally differ: minor editorial
|
||||
cleanup may be accepted even when the proposing module was not asked to perform
|
||||
it. Follow the [architecture boundary](../policy/architecture.md#correction-and-concurrency-invariants)
|
||||
when maintaining proposal, validation, and repair instructions; the difference
|
||||
alone is not a reason to tighten validation. The testing rationale is recorded in
|
||||
[ADR 0003](../adr/0003-module-focus-and-editorial-acceptance.md).
|
||||
|
||||
For a standard request preview or validation, select a native PromptKit profile
|
||||
and supply the template variables used by the selected prompt. The shipped
|
||||
proposal definitions use `TranscriptDescriptionBlock`, `GlossaryJSON`,
|
||||
|
||||
Reference in New Issue
Block a user