FIELD NOTE / X
A grammar can guarantee shape. Not truth.
The complete written thought and the evidence behind it. The video edition will follow its public release.
The written argument is here.
This approved X edition is on the journal now. Its video player and original platform link will appear after each public release is verified.
A grammar can guarantee shape. Not truth.
Video caption
A grammar can guarantee shape. Not truth. Both SHARE and REVIEW may fit the grammar. Name runtime, grammar, refusal and fallback handling. #EricFieldNotes
Full written post / accessibility read
People say a model was constrained as though the whole workflow were constrained. A grammar matcher can compute valid next tokens and mask invalid logits before sampling. That is a real, strong claim about output form in that configured path.
In a fictional partner-export case, the model returns route share. The JSON parses and every token was legal. A signed customer amendment says external transfer must wait. The grammar has succeeded while the proposed business action has failed.
Run the same synthetic cases through prompt-only formatting, a named hosted strict-schema route and one named self-hosted grammar backend. Record refusals and truncation separately. Then compare each valid branch with an owner-labeled expected outcome.
Use decoder constraints for form, then independently test whether a valid answer is the right answer. Do this because a token mask can prevent malformed continuations, but it cannot know which current customer agreement grants permission.
#EricFieldNotes
Four-beat scene transcript
1. A grammar can guarantee shape. Not truth.
People say a model was constrained as though the whole workflow were constrained. A grammar matcher can compute valid next tokens and mask invalid logits before sampling. That is a real, strong claim about output form in that configured path.
Visual: The guarantee attaches to one configured sampler path.
2. A legal enum can select the wrong branch.
In a fictional partner-export case, the model returns route share. The JSON parses and every token was legal. A signed customer amendment says external transfer must wait. The grammar has succeeded while the proposed business action has failed.
Visual: Both SHARE and REVIEW may fit the grammar.
3. Test form and branch separately.
Run the same synthetic cases through prompt-only formatting, a named hosted strict-schema route and one named self-hosted grammar backend. Record refusals and truncation separately. Then compare each valid branch with an owner-labeled expected outcome.
Visual: Measure malformed, incomplete and valid-but-wrong.
4. Write the guarantee with its boundary.
Use decoder constraints for form, then independently test whether a valid answer is the right answer. Do this because a token mask can prevent malformed continuations, but it cannot know which current customer agreement grants permission.
Visual: Name runtime, grammar, refusal and fallback handling.
Research and claim limits
- XGrammar: engine integration (S173)
- OpenAI: Structured Outputs guide (S175)
The examples identified as illustrative or simulated are design probes, not reported incidents. Vendor specifications do not establish workload performance.