TwinEthosRequest access

Recommended guardrail

Validate generated output before it drives a consequential decision or record

Where generated output feeds a consequential decision, a system of record, or an action, ground it in retrieved evidence, validate it against authoritative data or schemas, and block or flag claims that cannot be verified — including an agent's own reports about what it did. Detect consequential GenAI paths that write generated content into records or decisions with no grounding or validation step.

TwinEthos recommendation — not law

This is TwinEthos's opinion of what a responsible AI integration does anyway. It is never a legal or standards requirement; where binding law applies, the law governs.

The recommended-guardrail rule files are open under CC BY 4.0; attribution and scope are in the terms.

Informational data, not legal advice. Summaries are TwinEthos's own words and rules have not been reviewed by a lawyer: check the official text before relying on any of it. A guard addresses an item; adding it is not a statement that your code meets any law.

Evidence grade

Standards consensus (2)

2 standards and frameworks · 2 graded incidents.

TwinEthos recommendation, not law. Where binding law applies, the law governs. No binding law in the corpus requires this control yet. 2 standards and frameworks recommend it (FINRA GenAI/Agentic Guidance, NIST GenAI Profile (AI 600-1)). 2 graded incidents cited.

Standards and frameworks

Family “Generated output is acted on without validation or leakage screening”: binding law on related controls is in force in no jurisdiction. Context only: it does not change this guardrail's grade.

Graded incidents

  • Coding agent deleted a production database during a code freeze (2025-07; confirmed) The Register · evidence grade: press of record
  • Federal court orders issued containing unverified generative-AI output (2025-07; confirmed) U.S. Senate Judiciary Committee (2025-10-23) · evidence grade: primary

The guard to add

Validate GenAI output against a schema and its cited sources, and send unverifiable claims to review, before it drives a consequential decision or record.

A validation layer between the model call and the decision or record write: parse the output into a typed schema (Pydantic model_validate_json, zod parse, response_format json_schema), check every cited source id, figure, or extracted field against the retrieved documents or the system of record, and route anything that fails or carries no support to a review queue instead of writing it. Log prompt, output, model id and version, and the validation result per request to a retained store so confabulation rates can be monitored and errors traced back. For agents, check the system state rather than trusting the agent's own report that an action succeeded.

Example (Python + OpenAI SDK + Pydantic), before:

resp = client.chat.completions.create(model=MODEL, messages=msgs)
result = json.loads(resp.choices[0].message.content)
db.execute('UPDATE claims SET status=%s WHERE id=%s', (result['decision'], claim_id))

After:

class Assessment(BaseModel):
    decision: Literal['approve', 'refer']
    cited_doc_ids: list[str]

resp = client.chat.completions.create(model=MODEL, messages=msgs,
                                      response_format={'type': 'json_object'})
a = Assessment.model_validate_json(resp.choices[0].message.content)
unsupported = not a.cited_doc_ids or any(d not in retrieved_ids for d in a.cited_doc_ids)
genai_log.insert(prompt=msgs, output=a.model_dump(), model=resp.model, unsupported=unsupported)
if unsupported:
    review_queue.enqueue(claim_id, a)
else:
    db.execute('UPDATE claims SET status=%s WHERE id=%s', (a.decision, claim_id))

Control: GenAI in consequential decisions without confabulation/output-validation controls. Engineering guidance, not legal advice.

Why

Confabulated output is harmless in a draft and dangerous in a record. In one widely reported case an agent fabricated thousands of records and misreported whether its own changes could be undone. NIST describes the control; no binding law in the corpus requires it.

Class: law derived · set: output integrity · maturity: reviewed · confidence: high · id guardrail.output-confabulation-controls