When the Clause Is the Hallucination: Grounding Contract Terms and Governing the Moment of Commitment

An AI system negotiating or drafting on someone's behalf can produce a worse outcome for its own principal without manipulating anyone. It doesn't need to exploit a cognitive bias or misrepresent a fact to the other side. It only needs to propose or accept a term whose actual legal effect is different from what both parties believe it to be, an indemnification cap that doesn't survive a gross negligence carve-out, a liquidated damages figure that a court would strike down as an unenforceable penalty, a non-compete whose scope exceeds what the governing law will uphold. Neither party has to be deceived for this to happen. Both can read the clause, agree it looks reasonable, and sign something that does not do what either of them thinks it does.

This failure is worse than an outright hallucinated citation, because it has no visible defect. A fabricated case at least sits on the page making a claim someone can run down. A clause that silently fails under the governing law reads exactly like a clause that works. It survived negotiation. It got a compromise both sides could live with. It looks like the negotiation succeeded, right up until the clause is invoked and it does not do what everyone assumed.

Preventing this requires two defenses, and they are not substitutes for each other. One verifies the content: does this specific clause, under this specific governing law and fact pattern, actually produce the effect it appears to produce. The other verifies the process: independent of whatever the negotiating system itself claims, is there proof that this verification actually happened before the clause was accepted. A system with only the first can still let a bad clause through if nobody enforces the check. A system with only the second can rigorously prove that a process was followed while the underlying legal analysis inside that process was simply wrong. Both failures produce the same outcome: a signed document that does not do what it was supposed to do, with an audit trail that looks clean.

Why this is a harder grounding problem than legal research

Grounding an analytical claim is a resolution problem. The system asserts a proposition about the law, and grounding checks whether a verbatim, current source actually supports it. The check has a relatively fixed target: this passage, this provision, does it say what is claimed.

Grounding a negotiated clause is a different, harder problem, because the system is not making a claim about the law. It is proposing or accepting language whose legal effect depends on how the law would treat it, which requires more than retrieval. Consider three doctrinal categories that recur across most legal systems, differently shaped in each, but present in some form almost everywhere.

Penalty and liquidated damages doctrine. Many jurisdictions will not enforce a liquidated damages clause that functions as a penalty rather than a genuine pre-estimate of loss. A number both parties negotiated in good faith can be judicially unenforceable if it fails that test, and the test is fact-specific: what loss was foreseeable at the time of contracting, not at the time of breach.

Mandatory limits on exclusion and limitation of liability. Most legal systems refuse to let parties contract around liability for certain categories, commonly gross negligence, willful misconduct, death, or personal injury, regardless of what the liability cap clause says. A cap that reads as absolute in the document can be silently partial in application, and which categories are carved out, and how, varies by jurisdiction.

Formality and scope requirements for restrictive covenants. Non-competes, non-solicits, and similar restrictive terms are frequently enforceable only within specific bounds of duration, geography, and scope, bounds that differ sharply across jurisdictions and that a clause drafted to one jurisdiction's tolerance can silently fail in another.

None of these are edge cases. They are the ordinary operating terrain of contract negotiation, and in every one of them, the clause's text is not self-interpreting. Its actual effect depends on a body of law the negotiating system has to check against, not just a definition it has to retrieve.

Defense one: ground the clause's effect, not just its wording

The fix extends the same discipline already required for legal citation to a different target: not "does this citation exist and say what is claimed" but "does this proposed clause, under the specific governing law and specific facts, produce the effect both parties assume."

Concretely, this means every material clause a negotiating system proposes or accepts should carry a verification record with three components, each grounded in verbatim source text rather than a paraphrased summary of "how this usually works."

The applicable doctrine. What mandatory or default rule of the governing law bears on this clause type, cited to the actual provision or line of authority, not a general description of the area of law.

The specific fact dependency. Where the clause's enforceability turns on facts that are not yet known, the scope of a restrictive covenant against an employee's actual role, whether a liability cap survives a specific breach type, the system should say so explicitly rather than resolving the ambiguity silently in the direction that makes the clause look clean.

An explicit status, not a blended score. Whether the clause's enforceability is settled and verifiable against clear, current authority, or whether it is genuinely fact-dependent and requires a human legal judgment call. These are different categories of output and collapsing them into a single "this looks fine" assessment is where the risk actually lives. A clause flagged as confirmed should mean the system checked it against real, current, cited authority. A clause flagged as unresolved should mean exactly that, not a lower confidence version of confirmed.

This is a materially harder engineering problem than citation grounding, because it requires the system to reason about how a specific fact pattern interacts with a specific rule, not just retrieve a passage. It is also why treating it as solved by a good enough language model is exactly the mistake this whole problem is about. A model can write fluent, confident language about why a clause is standard and enforceable without that language being grounded in anything checkable, and fluent confidence is precisely what makes the failure invisible to both parties.

Defense two: govern the moment of commitment, independent of the system that proposed the term

Grounding fixes what the system knows. It does not fix what happens if nobody enforces the check before the deal closes. A negotiating system, however well grounded, is still the same system evaluating its own work, and a rushed negotiation under deadline pressure is exactly the condition under which a genuinely useful "flagged as unresolved" status gets silently waved through by someone who never wanted to slow the deal down to chase it.

The second, independent defense is procedural, and the architecture pattern is not specific to any one vendor or product. It is closer to a classical internal-controls principle, maker-checker, four-eyes, applied to AI-assisted negotiation: the system that proposes or evaluates a clause should not be the sole authority that clears it for signature. A separate control layer, external to the negotiating system itself, gates the actual moment of commitment and asks a narrower, more mechanical question than "is this a good deal": was the grounding check in the first defense actually performed on every material clause, is there a record of it, and for every clause flagged as unresolved, is there a named, accountable human sign-off rather than a silent pass-through.

This layer does not need to re-derive the legal analysis. Its job is procedural, not substantive: verify that the substantive check happened, verify that it is auditable after the fact independent of trusting the negotiating system's own report of its work, and block execution where that verification is missing. It converts "the system said this clause was fine" into "here is proof this clause was checked, by this process, and here is who signed off on what remained unresolved."

The reason this has to be a separate layer, not a feature bolted onto the negotiating system itself, is the same reason financial controls separate the person who authorizes a payment from the person who reconciles it. A system cannot be a fully reliable check on itself under commercial pressure to close, any more than a person can. Independence is the property that makes the check mean something, and independence cannot be manufactured by the same system whose incentives run toward getting the deal done.

Why both are necessary and neither is sufficient alone

A negotiating system with grounding but no governance layer can still let an unresolved clause through, because grounding produces an honest flag, and an honest flag is only useful if someone with the authority to stop the deal actually reads it before commitment. Under deadline pressure, an unenforced flag is functionally identical to no flag at all.

A negotiating system with governance but no grounding can produce a beautifully audited process around a substantively wrong legal analysis. The control layer can prove that a review happened, that a human signed off, that every step of the workflow is logged, while the underlying assessment of whether the liability cap actually survives a gross negligence claim was never checked against real authority in the first place. Process integrity without content correctness is a clean audit trail attached to a wrong answer.

The clause that silently fails is not a failure of intelligence. Model capability does not fix it, because the model can be entirely fluent and entirely wrong about how a specific fact pattern interacts with a specific rule of law, and fluency is what makes the error look like a normal, reasonable compromise instead of a defect. The fix is structural: verify the clause's effect against verbatim, current authority, distinguish what is settled from what is genuinely open, and require an independent layer to confirm that check happened before anyone signs. Neither piece is optional, and neither one, built alone, closes the gap.