Keep AI mechanic capabilities in sync

2026-07-27 21:43:48 -04:00
parent 568e46cd05
commit 37918bd411
5 changed files with 207 additions and 50 deletions
@@ -483,6 +483,14 @@ descriptions, and calculation metadata. The client cannot replace the system
 instructions, choose arbitrary models, attach files, add tools, or add external
 URLs.

+The deterministic draft parser owns the canonical outcome-capability manifest.
+The AI context serializes that manifest instead of maintaining a second outcome
+grammar. The parser rejects outcome fields absent from the manifest. Contract
+tests build a draft from each advertised capability example and pass it through
+the parser, so CI blocks a prompt that advertises unsupported fields. A mechanic
+grammar change must update the manifest and example, pass the round-trip test,
+and increment the prompt contract version before release.
+
 The OpenAI integration uses the Responses API with Structured Outputs, no
 tools, and `store: false`. The application stores the bounded clarification
 history needed for the current drafting session. Requests use a fixed