agent flagged every cross-reference as changed after the counterparty renumbered the sections — the numbers moved but…

Not specified by the original author.

TL;DR

The counterparty renumbered the sections without changing any clause text, and the agent flagged every cross-reference as changed. Align clauses between versions by text similarity instead of by number, emit the renumbering as a single mapping (old 4.2 is now 5.1), and verify the clause texts are identical before calling it renumber-only.

The symptom

agent flagged every cross-reference as changed after the counterparty renumbered the sections  -  the numbers moved but no clause text changed

Steps

1. Align clauses by text, not by number

Parse each version into (section number, clause text) pairs. Match pairs across versions by text similarity (normalized text, ignoring the number). Renumbered clauses match on text. Expected: Each clause in v1 matched to its v2 counterpart despite different numbers.

2. Emit a single renumber map

From the alignment, produce the mapping: 4.1 to 5.1, 4.2 to 5.2, and so on. Present this once instead of flagging each reference. Expected: One renumber table covering all moved sections.

3. Verify the texts are identical

For each aligned pair, diff the clause texts. If all diffs are empty, the change is renumber-only. Any non-empty diff is a real edit hiding inside the renumbering: report it. Expected: Empty text diffs across the board, or a short list of real edits.

4. Rewrite references through the map for the report

Show cross-references resolved through the map so reviewers see 'see Section 5.1 (formerly 4.2)'. Do not list each reference as a change. Expected: References readable under the new numbering with old numbers noted.

When to use

• Every cross-reference is flagged but clause texts are unchanged
• The counterparty renumbered sections, articles, or exhibits
• The diff is number-driven rather than text-driven

When not to use

• Clause text actually changed along with the numbers (report the text edits)
• References point at sections that no longer exist (broken links, different issue)
• Numbering is unchanged (different cause)

Why it happens

Cross-references embed section numbers, so a renumbering touches every reference string. A string diff cannot tell 'number moved' from 'meaning changed'. Aligning on clause text separates the two: identical texts mean the renumbering is the whole story.

Edge cases

• Split or merged sections: one-to-many alignments need human review; do not force a map.
• Exhibit renumbering (Exhibit A to Exhibit 1): same technique, separate map.
• References inside defined terms: apply the map there too, consistently.

Provenance

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

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

Thread query: agent flagged every cross-reference as changed after the counterparty renumbered the sections - the numbers moved but no clause text changed

TL;DR: The counterparty renumbered the sections without changing any clause text, and the agent flagged every cross-reference as changed. Align clauses between versions by text similarity instead of by number, emit the renumbering as a single mapping (old 4.2 is now 5.1), and verify the clause texts are identical before calling it renumber-only.

Not specified by the original author.

TL;DR

Resolve citations against the fully-amended text, never the base document. Build a versioned clause map keyed by (section, amendment chain) and apply every amendment in effective-date order before the agent looks up any cross-reference. "As amended by Amendment No. 2" is a pointer into the post-amendment document, so resolving it against the original text silently reads wording that is no longer operative.

clause points to "Section 4.2 of the Original Agreement as amended by Amendment No. 2"  -  the agent resolved it against the unamended text

Steps

1. Index every amendment in effective-date order, parsing the effective date from the amendment text itself, not from the filename or upload time. Expected: each amendment has an effective-date field; the order matches the legal sequence

2. Build a layered section map: for each numbered section, stack the base text then each amendment's replacement text on top. Expected: "Section 4.2" resolves to a stack of versions, each tagged with the amendment that produced it

3. Parse the citation's amendment qualifier ('as amended by Amendment No. 2') as a version selector, and resolve the citation to that layer of the stack. Expected: the resolved text comes from the Amendment 2 version of Section 4.2, not the base

4. Add a regression check that diffs the resolved text against the base text whenever a qualifier is present; if they are identical, the qualifier was ignored and the resolution is flagged. Expected: every citation resolution logs which amendment layer it came from

5. Re-run the full extraction suite after this change and confirm no citation with an amendment qualifier points at raw base text. Expected: zero qualifier-bearing citations resolve against the unamended text

Use this when

• A citation names an amendment: "as amended by Amendment No. 2", "as restated by Amendment 3".
• The agent extracts clauses from agreements that have an amendment chain.
• Resolved text looks subtly wrong but matches the original agreement.
• You are auditing an extraction pipeline and want citation-resolution correctness.

Not for this skill when

• The contract is a single version with no amendments.
• The reference carries no amendment qualifier; it is a plain section pointer.
• You need legal interpretation of what the clause means, not a fix for which text was resolved.
• The wrong text came from OCR or PDF parsing, not from version selection.

Variant phrasings

agent resolved against the original agreement instead of the amended version

clause citation ignores the amendment chain

"as amended by" qualifier dropped by the extraction agent

cross-reference points at pre-amendment wording

Why it happens

Agents usually resolve citations eagerly against the base document and apply amendments in a separate, later pass (or never). Because the base and the amended version share section numbers, the wrong hit looks exactly right: the section exists, the text is plausible, and nothing errors. The failure is silent by construction.

Edge cases

• An amendment restates only part of a section; the untouched paragraphs of the base text are still live. Resolve paragraph-level, not section-level.
• The qualifier names an amendment the agent does not have. Raise a missing-document warning; never guess what the amendment said.
• Effective date and signing date disagree. Order by effective date; use signing date only as a tiebreak.
• Multiple amendments touch the same section. The qualifier selects one layer; without a qualifier, the latest effective layer wins.

Provenance

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

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

Thread query: clause points to "Section 4.2 of the Original Agreement as amended by Amendment No. 2" - the agent resolved it against the unamended text

TL;DR: Resolve citations against the fully-amended text, never the base document. Build a versioned clause map keyed by (section, amendment chain) and apply every amendment in effective-date order before the agent looks up any cross-reference. "As amended by Amendment No. 2" is a pointer into the post-amendment document, so resolving it against the original text silently reads wording that is no longer operative.

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.