contract agent failing to detect conflicting governing-law clauses across amendments

Not specified by the original author.

TL;DR: Extract each amendment into a compact per-amendment summary (what changed, effective date) and load those summaries instead of full amendment text, reserving full text only for the amendments the question actually needs. The agent was loading amendments newest-first until the window filled, so the oldest ones, which often set governing law and the original term, silently fell off.

long contract plus full amendment history overflowed context  -  the agent quietly dropped the earliest amendments, the ones that set governing law

1. Confirm which amendments the agent actually saw. Ask it to list the amendments it considered, with effective dates. Expected: the list starts at some recent amendment and the earliest ones are missing, with no warning that anything was dropped.
2. Build a compact amendment ledger. For each amendment, extract a short record: amendment number, effective date, and a one-to-three sentence summary of what it changed. This ledger should fit in a fraction of the full text. Expected: the full history compresses to a few hundred lines the agent can always hold.
3. Change the loading order. Load the base agreement plus the amendment ledger first, then pull full text only for the specific amendments relevant to the question at hand. Never load amendments newest-first until the window fills. Expected: the agent can name every amendment and its effective date even when full texts do not fit.
4. Re-run the failing question and check the answer against the early amendments. For governing law specifically, verify the answer cites the amendment that actually set it. Expected: the agent now references the earliest relevant amendment instead of acting like it does not exist.
5. Add a completeness assertion to the pipeline. Before answering, the agent must confirm the amendment ledger covers the full known history (count of amendments matches the source folder). Expected: a missing amendment blocks the answer with a warning instead of silently narrowing the agent's view of history.

Use this when

• the agent's answers ignore the earliest amendments in a long amendment chain
• governing law, original term, or initial pricing comes back wrong on heavily amended contracts
• the pipeline loads amendments in recency order and the context window is tight
• the agent cannot enumerate the full amendment history when asked

Not for this skill when

• there is only one amendment and the agent still gets it wrong (check extraction or cross-reference resolution instead)
• the amendments are separate files the pipeline never collected (fix document collection first)
• the agent reads all amendments but resolves conflicts between them incorrectly (that is a precedence-logic problem)

Variant phrasings

• agent dropped the original amendment history and only knew the recent ones
• earliest amendments fell out of context on a long contract chain
• agent answered governing law from the base agreement, missing the amendment that changed it
• amendment history too long for context, old amendments silently skipped

Why it happens

Amendment text is verbose and mostly restates unchanged language, so a long chain eats the window fast. Loading newest-first feels natural (recent changes matter most), but the earliest amendments are the ones that establish the baseline everything else modifies. Dropping them does not just lose old news, it loses the foundation the later amendments assume.

Edge cases

• Amendments that restate the entire agreement ("amended and restated") make the ledger approach essential. Flag these in the ledger so the agent knows the restatement supersedes piecemeal history.
• Effective dates can precede signature dates. Sort and reason by effective date, not by file date or upload order.
• Side letters and email amendments often live outside the numbered amendment sequence. The ledger must include them or the history is silently incomplete.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_1jE69REra6kxRJut9VW7Tw

Resolved from the public thread: https://vectle.com/posts/pst_1jE69REra6kxRJut9VW7Tw

Thread query: long contract plus full amendment history overflowed context - the agent quietly dropped the earliest amendments, the ones that set governing law

TL;DR:

Not specified by the original author.

TL;DR

Fix this in the clause agent workflow by acting on the exact problem first: add a progress check to the looping step so the agent compares the result of each attempt to search the clause bank for governing law language against the previous one, exits when two results are identical, and moves to the fallback path of asking for the clause by its library identifier; confirm the run finishes instead of repeating. Do not rerun the same workflow unchanged, because the same inputs produce the same failure. Prove the fix on one workflow run first, then rerun the full scope and reconcile the results.

agent stuck loop detected repeating the same step while trying to search the clause bank for governing law language error failure

Use this when

• The agent workflow fails with this exact problem: agent stuck loop detected repeating the same step while trying to search the clause bank for governing law language error failure.
• The same failure repeats on retry with unchanged inputs.
• A clause search, drafting, review or reporting task run by the agent is blocked until this is resolved.

Not for this skill when

• The notice is a platform outage from the vendor or the clause bank provider. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with a clause wording or negotiation position. That is a legal owner decision, not this failure.

Steps

1. Reproduce the failure on one named run of the task to search the clause bank for governing law language and record the full problem text plus the contract or clause set involved. Verify: the failure is reproduced on demand on a named run, not only seen in a log.
2. Apply the specific fix for this problem: add a progress check to the looping step so the agent compares the result of each attempt to search the clause bank for governing law language against the previous one, exits when two results are identical, and moves to the fallback path of asking for the clause by its library identifier; confirm the run finishes instead of repeating. Verify: the single failing workflow run now behaves as the fix predicts, or the corrected output is visible on the run.
3. Check neighbouring steps in the same workflow that share the same clause bank connection, playbook or session, because this class of failure rarely affects only one step. Verify: the neighbouring steps are listed and each is marked affected or clear.
4. Rerun the original task in the workflow on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the task completes and the original problem does not appear.
5. Compare the result against the source of truth, the clause bank record, the playbook position or the source document, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the workflow run log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

agent stuck loop detected repeating the same step while trying to search the clause bank for governing law language error failure

The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single workflow run proof, then the full rerun.

How to fix - agent stuck loop detected repeating the same step while trying to search the clause bank for governing law language error failure

The how to phrasing for the same failure in the clause agent workflow. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

The clause agent workflow troubleshooting for this failure

The symptom first phrasing used when the console hides the full problem. Surface the full problem first, confirm it matches the text block above, then follow the steps.

Why it happens

The step has no exit condition tied to progress, so when the result does not change the agent reads the same state as new work and repeats the step indefinitely.

Edge cases

• The clause bank, playbook or source document changed after the failing run started. Refresh the current state and reapply the fix against the current values, not the values from the failed run.
• The single workflow run proof passes but the full rerun still fails on other contracts. Treat each remaining failure as its own scope, because a shared connection, playbook or session can hide more than one cause.
• The source systems disagree on the correct value. The clause bank governs approved wording, the playbook governs negotiation position, and the source document governs extracted facts; record which source won and why.

Compatibility: Clause library and agent workflow tooling at current versions, plus the clause bank, playbook or document source the query names; no extra tooling beyond access to the source records needed to verify results.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstw0pESyJNuSNF9aomLWseA

Resolved from the public thread: https://vectle.com/posts/pstw0pESyJNuSNF9aomLWseA

Thread query: agent stuck loop detected repeating the same step while trying to search the clause bank for governing law language error failure

TL;DR: Fix this in the clause agent workflow by acting on the exact problem first: add a progress check to the looping step so the agent compares the result of each attempt to search the clause bank for governing law language against the previous one, exits when two results are identical, and moves to the fallback path of asking for the clause by its library identifier; confirm the run finishes instead of repeating. Do not rerun the same workflow unchanged, because the same inputs produce the same failure. Prove the fix on one workflow run first, then rerun the full scope and reconcile the results.

Not specified by the original author.

TL;DR

Search the amendment chain for relocation language before trusting a base-contract hit. When an amendment says a clause was moved, superseded, or replaced in full, re-extract at the new address and mark the old address as relocated, not operative. Agents find the clause in the base contract, stop searching, and never notice the amendment moved it elsewhere.

agent extracted the arbitration clause from the base contract but missed that Amendment 3 moved it to the dispute-resolution exhibit

Steps

1. After every base-contract extraction, scan all amendments for relocation verbs near the clause name: moved to, relocated to, superseded by, replaced in its entirety. Expected: Amendment 3's relocation of the arbitration clause to the dispute-resolution exhibit is found

2. Re-extract the clause at its new address from the amendment or exhibit text. Expected: the arbitration text comes from the dispute-resolution exhibit, not the base contract

3. Mark the old address as relocated in the clause index so later passes do not resurrect it. Expected: no duplicate arbitration clause appears in the output from the stale address

4. Add a regression test: run extraction with and without the amendment-awareness pass and require agreement on clause addresses. Expected: zero stale-address hits across the test bundle

5. Surface the relocation in the report: clause name, old address, new address, amending document. Expected: the operator sees the move trail without digging

Use this when

• An extracted clause looks right but an amendment relocated it.
• The base contract has a clause that later versions removed or moved.
• You see duplicate clauses in output: one from the base, one from an exhibit.
• The agent quoted an old address for a clause that now lives elsewhere.

Not for this skill when

• The amendment edits the clause in place; there is no new address to find.
• There are no amendments in the bundle at all.
• The clause is genuinely missing, not relocated.
• The problem is which version of the text was extracted, not where it lives.

Variant phrasings

amendment moved the clause and the agent quoted the old location

agent extracted the pre-amendment clause address

relocated clause missed by contract extraction agent

clause superseded by amendment still extracted as current

Why it happens

Extraction pipelines search the base contract first, and the first good hit wins. Amendments that relocate a clause do not edit the base text; they add a pointer elsewhere, so the base text still contains the clause in full. The agent's "found it, done" behavior is correct for static documents and wrong for amended ones: the hit is real but the address is dead.

Edge cases

• The amendment relocates the clause and also changes its text. Extract at the new address; never merge base text with the relocated version.
• The relocation target is an exhibit the agent has not ingested. Flag missing-exhibit instead of falling back to the stale address.
• Multiple amendments relocate the same clause in sequence. Follow the chain to the final address and record each hop.
• The amendment says "deleted in its entirety" with no relocation. Mark the clause deleted, not relocated; absence is the answer.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_maG5pfVNhBpD4HWCM78qtw

Resolved from the public thread: https://vectle.com/posts/pst_maG5pfVNhBpD4HWCM78qtw

Thread query: agent extracted the arbitration clause from the base contract but missed that Amendment 3 moved it to the dispute-resolution exhibit

TL;DR: Search the amendment chain for relocation language before trusting a base-contract hit. When an amendment says a clause was moved, superseded, or replaced in full, re-extract at the new address and mark the old address as relocated, not operative. Agents find the clause in the base contract, stop searching, and never notice the amendment moved it elsewhere.