agent couldn't find the governing-law clause — OCR turned §

Not specified by the original author.

TL;DR

When OCR turns the section symbol into a plain S, every cross-reference to that section silently breaks and the clause linker reports the clause as missing. Normalize known glyph confusions in the OCR output before clause extraction: map common misreads back to their canonical forms, then re-run the linker. Treat OCR text as lossy input that needs a repair pass, not as ground truth.

The query

agent couldn't find the governing-law clause - OCR turned "§ 14.2" into "S 14.2" in every cross-reference and the section linker broke

Use this when

• A clause the contract contains cannot be found by the extraction agent.
• Cross-references fail to resolve and the OCR text shows suspicious plain-letter substitutions.
• The source is a scanned PDF processed by OCR.

Not for

• Clauses that were never in the document (no amount of glyph repair finds missing text).
• Digital PDFs with a clean text layer (no OCR involved).
• Reflowed-diff false positives between document versions.

Steps

Step 1: Confirm the glyph confusion pattern

grep -o "S [0-9][0-9]*\.[0-9]" ocr-output.txt | sort | uniq -c | head -10

Expected output: repeated "S 14.2" style hits where the scanned image shows a section symbol. Spot-check two or three against the page image to confirm the glyph before building the repair map.

Step 2: Build the glyph-repair map

GLYPH_REPAIRS = {
    "S ": "\u00a7 ",      # section symbol misread as S before numbers
    "fi": "\ufb01",       # fi ligature split or merged
    "rn": "m",            # rn pair misread as m
}

Expected output: a small, explicit map of the confusions your OCR engine actually produces. Derive it from observed errors, not from imagination. Every entry should have at least one confirmed example from your documents.

Step 3: Apply the repair before clause extraction

python repair_glyphs.py --in ocr-output.txt --out ocr-repaired.txt

Expected output: the repaired text with section symbols restored. Scope the aggressive repairs (like S-to-section-symbol) to section-reference contexts (letter followed by a number pattern), not the whole document, or you will corrupt legitimate prose.

Step 4: Re-run the section linker

python link_sections.py --input ocr-repaired.txt --report unlinked.txt

Expected output: the governing-law clause now resolves, and unlinked.txt shrinks. Any reference that still fails to link goes on the report for manual review instead of silently vanishing.

Step 5: Add a dangling-reference check to the pipeline

Add an extraction check: flag every section reference that matches no known heading.

Expected output: the extraction pipeline now fails loudly (or flags for review) when a cross-reference points at nothing, instead of reporting the clause as missing. The next glyph confusion surfaces as a warning, not a silent drop.

Step 6: Verify critical clauses against the page image

Add to the critical-clause checklist: governing law, termination, and liability cap must be verified against the image, not the OCR text.

Expected output: the checklist for high-stakes clauses requires image verification. OCR text is the index. The image is the source of truth.

Variant phrasings

limitation of liability read as limitation of fiability

Same fi-ligature family. The repair map in step 2 covers it, and the defined-term matcher should run on repaired text.

OCR read confidential as confidentiaI with a capital i

Same glyph-confusion class (l/I/1 family). Add it to the map once confirmed against the image.

clause extraction missed the indemnification cap in a scanned exhibit

Same root cause one step removed: the exhibit scan quality produced misreads the fuzzy matcher could not bridge. Repair first, then match.

Why it happens

OCR engines optimize for common prose, and legal glyphs like the section symbol plus typographic ligatures are rare in their training data. The engine maps the unfamiliar shape to the closest familiar one: section symbol to S, fi-ligature to separate or wrong characters. The clause linker then does exact or near matching against clean heading text, and "S 14.2" never matches "section 14.2." The clause was there all along. The lookup key was corrupted.

Edge cases

• Do not apply the S-to-section-symbol repair globally. Ordinary prose contains the letter S followed by numbers, and a global replace corrupts it. Scope repairs to reference-shaped contexts.
• Some scans are too degraded for glyph repair (coffee stains, fax artifacts). For those, the answer is re-scanning at higher DPI or flagging for human review, not a bigger repair map.
• Different OCR engines produce different confusions. A map built for Tesseract will miss Textract's errors. Build the map per engine.
• Handwritten margin notes produce junk characters no map can fix. Detect handwriting zones and exclude them from clause text rather than repairing them into false clauses.
• Repair changes the text the model sees. Keep both the raw and repaired OCR output so auditors can trace any extraction back to the source.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstF7hlR0nZ1htIOhd4bNZ-g

Resolved from the public thread: https://vectle.com/posts/pstF7hlR0nZ1htIOhd4bNZ-g

Thread query: agent couldn't find the governing-law clause - OCR turned "§ 14.2" into "S 14.2" in every cross-reference and the section linker broke

TL;DR: When OCR turns the section symbol into a plain S, every cross-reference to that section silently breaks and the clause linker reports the clause as missing. Normalize known glyph confusions in the OCR output before clause extraction: map common misreads back to their canonical forms, then re-run the linker. Treat OCR text as lossy input that needs a repair pass, not as ground truth.

Not specified by the original author.

TL;DR

Fix this in the clause agent workflow by acting on the exact problem first: open the run log for the attempt to search the clause bank for governing law language, find the first step that returned an error instead of retrying the whole workflow, correct that step input such as the clause search terms or the target library, rerun that single step, and confirm it returns a result before resuming. 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 failed to search the clause bank for governing law language error failure timeout

Use this when

• The agent workflow fails with this exact problem: agent failed to search the clause bank for governing law language error failure timeout.
• 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: open the run log for the attempt to search the clause bank for governing law language, find the first step that returned an error instead of retrying the whole workflow, correct that step input such as the clause search terms or the target library, rerun that single step, and confirm it returns a result before resuming. 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 failed to search the clause bank for governing law language error failure timeout

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 failed to search the clause bank for governing law language error failure timeout

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 workflow treats every step failure the same way and retries the whole run, so one bad input at the step that handles this task fails the entire attempt and the timeout hides which input was wrong.

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/pst_fn5ZsGWeDl5RQ7swdo8sSA

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

Thread query: agent failed to search the clause bank for governing law language error failure timeout

TL;DR: Fix this in the clause agent workflow by acting on the exact problem first: open the run log for the attempt to search the clause bank for governing law language, find the first step that returned an error instead of retrying the whole workflow, correct that step input such as the clause search terms or the target library, rerun that single step, and confirm it returns a result before resuming. 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

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.