clause extraction agent missing nested indemnification terms in subcontractor exhibits

Not specified by the original author.

TL;DR

The non-compete was in the employment terms exhibit, but the agent's MSA-only scope filter skipped exhibits entirely. Key clauses routinely hide in exhibits and schedules. Make exhibit inclusion the default scope, re-scan the exhibits, and only narrow scope deliberately with a recorded reason.

The symptom

non-compete buried in the employment terms exhibit  -  the agent's MSA-only scope filter skipped the exhibit entirely

Steps

1. Expand scope to exhibits

Include all exhibits, schedules, and attachments in the extraction scope. Expected: Exhibits queued for extraction.

2. Re-scan for the clause type

Run the non-compete search across the exhibits. The employment terms exhibit contains it. Expected: The clause found where the filter had excluded it.

3. Verify the clause text

Read the found clause to confirm it is the operative non-compete, not a mention. Expected: Confirmed clause text and citation.

4. Flip the default scope

Exhibits and schedules are in scope by default. Narrowing scope requires an explicit, recorded reason. Expected: No future run silently skips exhibits.

When to use

• A clause is missing but might be in an exhibit
• The scope filter names only the main agreement
• Exhibits exist and were never read

When not to use

• The exhibits were read and the clause is absent (genuinely missing)
• Scope was narrowed deliberately for a defined task (keep the record)
• The 'exhibit' is just a cover page (nothing to read)

Why it happens

Material terms migrate to exhibits: employment terms, pricing schedules, SLAs. A scope filter set to 'the MSA' reads the frame and skips the picture. The agent did exactly what it was told; the scope was wrong.

Edge cases

• Incorporated-by-reference documents: fetch them too, or note them as unread.
• Exhibit lists without content: flag the missing exhibit rather than assuming.
• Side letters: treat as exhibits for scope purposes.

Provenance

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

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

Thread query: non-compete buried in the employment terms exhibit - the agent's MSA-only scope filter skipped the exhibit entirely

TL;DR: The non-compete was in the employment terms exhibit, but the agent's MSA-only scope filter skipped exhibits entirely. Key clauses routinely hide in exhibits and schedules. Make exhibit inclusion the default scope, re-scan the exhibits, and only narrow scope deliberately with a recorded reason.

Not specified by the original author.

TL;DR

The non-compete was in the employment terms exhibit, but the agent's MSA-only scope filter skipped exhibits entirely. Key clauses routinely hide in exhibits and schedules. Make exhibit inclusion the default scope, re-scan the exhibits, and only narrow scope deliberately with a recorded reason.

The symptom

non-compete buried in the employment terms exhibit  -  the agent's MSA-only scope filter skipped the exhibit entirely

Steps

1. Expand scope to exhibits

Include all exhibits, schedules, and attachments in the extraction scope. Expected: Exhibits queued for extraction.

2. Re-scan for the clause type

Run the non-compete search across the exhibits. The employment terms exhibit contains it. Expected: The clause found where the filter had excluded it.

3. Verify the clause text

Read the found clause to confirm it is the operative non-compete, not a mention. Expected: Confirmed clause text and citation.

4. Flip the default scope

Exhibits and schedules are in scope by default. Narrowing scope requires an explicit, recorded reason. Expected: No future run silently skips exhibits.

When to use

• A clause is missing but might be in an exhibit
• The scope filter names only the main agreement
• Exhibits exist and were never read

When not to use

• The exhibits were read and the clause is absent (genuinely missing)
• Scope was narrowed deliberately for a defined task (keep the record)
• The 'exhibit' is just a cover page (nothing to read)

Why it happens

Material terms migrate to exhibits: employment terms, pricing schedules, SLAs. A scope filter set to 'the MSA' reads the frame and skips the picture. The agent did exactly what it was told; the scope was wrong.

Edge cases

• Incorporated-by-reference documents: fetch them too, or note them as unread.
• Exhibit lists without content: flag the missing exhibit rather than assuming.
• Side letters: treat as exhibits for scope purposes.

Provenance

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

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

Thread query: non-compete buried in the employment terms exhibit - the agent's MSA-only scope filter skipped the exhibit entirely

TL;DR: The non-compete was in the employment terms exhibit, but the agent's MSA-only scope filter skipped exhibits entirely. Key clauses routinely hide in exhibits and schedules. Make exhibit inclusion the default scope, re-scan the exhibits, and only narrow scope deliberately with a recorded reason.

Not specified by the original author.

TL;DR: Build an explicit reference graph (which document incorporates or defines what) and resolve references transitively, up to a fixed depth, instead of asking the agent to chase them one hop at a time. The agent was resolving the first hop and stopping, so anything defined two or three levels down never got found.

agent couldn't follow "as defined in Exhibit C, which incorporates Schedule 2.1(a)"  -  nested exhibit references three levels deep

1. Confirm the agent stopped early. Ask it to show its work on the failing reference: which documents it opened and where it stopped. Expected: it opened the first exhibit and never followed the incorporation chain deeper.
2. Build the reference graph at ingest. For each document, extract its incorporation and definition references ("Exhibit C incorporates Schedule 2.1(a)", "as defined in Section 4.2") into a small graph: nodes are documents and sections, edges are "defines" or "incorporates". Expected: a queryable map of how the documents link together, built once per deal.
3. Resolve transitively with a depth limit. When the agent hits "as defined in Exhibit C", look up Exhibit C in the graph, follow its incorporation edge to Schedule 2.1(a), and keep going up to three or four hops. Expected: the final definition is retrieved with the full chain recorded (MSA -> Exhibit C -> Schedule 2.1(a)).
4. Detect cycles and dead ends. If the chain loops (A incorporates B incorporates A) or points at a document not in the bundle, stop and report the chain rather than looping or silently giving up. Expected: circular references produce a clear "circular reference detected" message with the loop shown.
5. Make the chain part of the answer. Every extracted definition should cite the full resolution path, not just the final document. Expected: answers read "defined in Schedule 2.1(a), via Exhibit C's incorporation clause" so a human can verify the chain.

Use this when

• the agent fails on references nested two or more levels deep
• exhibits incorporate schedules that incorporate other schedules
• the agent resolves a cross-reference against the wrong document in the chain
• definitions live several hops away from the clause that uses them

Not for this skill when

• the reference is a single hop and the agent still fails (check the section linker or the extraction step)
• the referenced document is missing from the bundle entirely (that is a document-collection gap; report it as missing)
• the agent follows the chain but misreads the final definition (check the answering logic, not the resolution)

Variant phrasings

• agent couldn't resolve a three-level exhibit incorporation chain
• nested cross-reference across exhibits defeated the agent
• "as defined in Exhibit C which incorporates Schedule 2.1(a)" never resolved
• agent stopped at the first hop of a multi-document definition chain

Why it happens

Agents resolve references the way they read: one step at a time, holding the intermediate result in working memory. Each hop adds a chance to lose the thread, misidentify the next document, or simply stop because the immediate question seems answered. An explicit graph removes the memory burden: the chain is computed, not remembered, and every hop is checkable.

Edge cases

• "The Agreement" inside an exhibit may mean the subcontract, not the MSA. The graph needs document-scoped resolution: each exhibit records which agreement its bare references point to.
• Incorporation by reference can pull in an entire external document ("the 2024 framework terms"). If it is not in the bundle, the chain ends with a named-but-missing document; report that explicitly.
• Amendments can rewire the graph (Amendment 3 moves arbitration to a new exhibit). Rebuild or patch the graph per version; a stale graph resolves against superseded structure.

Provenance

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

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

Thread query: agent couldn't follow "as defined in Exhibit C, which incorporates Schedule 2.1(a)" - nested exhibit references three levels deep

TL;DR: