A schema can require evidence. It cannot create it.

Video caption

A schema can require evidence. It cannot create it.

The agent presents a syntactically valid but stale source.

Check identity, version, scope, expiry and contradiction.

A string pattern is never an authorization receipt.

#EricFieldNotes

Full written post / accessibility read

Strict structured output can make an evidence identifier field mandatory. That removes a parser failure. It does not prove the cited record exists, belongs to this customer, is current, or supports the proposed action.

Imagine a customer-transfer assistant returning a valid partner route and evidence ID amendment forty-two. The authoritative store has already superseded amendment forty-two. The response matches its schema while the record it relies on is no longer the governing one.

A semantic validator should fetch the exact source from a protected store, compare its version with the current policy and verify customer and recipient scope. A fabricated or expired citation returns evidence missing, not permission granted.

Attach the verified record and version to the proposed route, then recheck authorization at dispatch. Do this because required fields make responses easier to consume; only a source lookup and action-boundary check can make a claim actionable.

#EricFieldNotes

Four-beat scene transcript

1. A schema can require evidence. It cannot create it.

Strict structured output can make an evidence identifier field mandatory. That removes a parser failure. It does not prove the cited record exists, belongs to this customer, is current, or supports the proposed action.

Visual: A valid evidence_id can still name nothing.

2. The ID looks perfect.

Imagine a customer-transfer assistant returning a valid partner route and evidence ID amendment forty-two. The authoritative store has already superseded amendment forty-two. The response matches its schema while the record it relies on is no longer the governing one.

Visual: The agent presents a syntactically valid but stale source.

3. Resolve the record before action.

A semantic validator should fetch the exact source from a protected store, compare its version with the current policy and verify customer and recipient scope. A fabricated or expired citation returns evidence missing, not permission granted.

Visual: Check identity, version, scope, expiry and contradiction.

4. Make the cited source executable evidence.

Attach the verified record and version to the proposed route, then recheck authorization at dispatch. Do this because required fields make responses easier to consume; only a source lookup and action-boundary check can make a claim actionable.

Visual: A string pattern is never an authorization receipt.

Research and claim limits

• OpenAI: Structured Outputs guide (S175)
• XGrammar: engine integration (S173)

The examples identified as illustrative or simulated are design probes, not reported incidents. Vendor specifications do not establish workload performance.