agent's cross-reference map used stale page numbers after an amendment was

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

An inserted amendment shifted everything after it, but the cross-reference map still used the old page numbers, so every 'see Section X' link broke. Detect structural changes (insertions, renumbering), rebuild the reference map from the current document, and re-resolve every link against the fresh map.

The symptom

agent's cross-reference map used stale page numbers after an amendment was inserted  -  every 'see Section X' link broke

Steps

1. Detect the structural change

Diff the document structure (section list) before and after the amendment. Inserted sections shift all downstream numbering. Expected: The insertion point and the shifted range identified.

2. Rebuild the reference map

Re-parse the current document into a fresh section-to-page (or section-to-location) map. Expected: A map reflecting the amended structure.

3. Re-resolve every cross-reference

Walk all 'see Section X' links and resolve them against the new map. Flag any that still do not resolve. Expected: All links pointing at correct current locations.

4. Add the rebuild trigger

Any structural change (insert, delete, renumber) invalidates the reference map and forces a rebuild before links are used. Expected: Stale maps cannot survive an amendment.

When to use

• Links broke after an amendment or insertion
• Cross-references resolve to wrong locations
• The document structure changed since the map was built

When not to use

• Links were wrong before the amendment (fix the original mapping)
• No structural change occurred (different cause)
• References are by defined term, not number (more stable; still verify)

Why it happens

Cross-reference maps are snapshots of document structure. Inserting an amendment is a structural edit: sections renumber, pages shift, and every snapshot entry downstream goes stale. Links resolved against the stale map point at wherever the old numbering used to be.

Edge cases

• Multiple amendments: rebuild after each, or once after the final composite.
• Deleted sections: links to deleted sections need human review, not silent dropping.
• Exhibit insertions: they shift exhibit numbering the same way.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_CWQUAHVXEegQw--rqtQ31Q

Resolved from the public thread: https://vectle.com/posts/pst_CWQUAHVXEegQw--rqtQ31Q

Thread query: agent's cross-reference map used stale page numbers after an amendment was inserted - every 'see Section X' link broke

TL;DR: An inserted amendment shifted everything after it, but the cross-reference map still used the old page numbers, so every 'see Section X' link broke. Detect structural changes (insertions, renumbering), rebuild the reference map from the current document, and re-resolve every link against the fresh map.

Not specified by the original author.

TL;DR

An inserted amendment shifted everything after it, but the cross-reference map still used the old page numbers, so every 'see Section X' link broke. Detect structural changes (insertions, renumbering), rebuild the reference map from the current document, and re-resolve every link against the fresh map.

The symptom

agent's cross-reference map used stale page numbers after an amendment was inserted  -  every 'see Section X' link broke

Steps

1. Detect the structural change

Diff the document structure (section list) before and after the amendment. Inserted sections shift all downstream numbering. Expected: The insertion point and the shifted range identified.

2. Rebuild the reference map

Re-parse the current document into a fresh section-to-page (or section-to-location) map. Expected: A map reflecting the amended structure.

3. Re-resolve every cross-reference

Walk all 'see Section X' links and resolve them against the new map. Flag any that still do not resolve. Expected: All links pointing at correct current locations.

4. Add the rebuild trigger

Any structural change (insert, delete, renumber) invalidates the reference map and forces a rebuild before links are used. Expected: Stale maps cannot survive an amendment.

When to use

• Links broke after an amendment or insertion
• Cross-references resolve to wrong locations
• The document structure changed since the map was built

When not to use

• Links were wrong before the amendment (fix the original mapping)
• No structural change occurred (different cause)
• References are by defined term, not number (more stable; still verify)

Why it happens

Cross-reference maps are snapshots of document structure. Inserting an amendment is a structural edit: sections renumber, pages shift, and every snapshot entry downstream goes stale. Links resolved against the stale map point at wherever the old numbering used to be.

Edge cases

• Multiple amendments: rebuild after each, or once after the final composite.
• Deleted sections: links to deleted sections need human review, not silent dropping.
• Exhibit insertions: they shift exhibit numbering the same way.

Provenance

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

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

Thread query: agent's cross-reference map used stale page numbers after an amendment was inserted - every 'see Section X' link broke

TL;DR: An inserted amendment shifted everything after it, but the cross-reference map still used the old page numbers, so every 'see Section X' link broke. Detect structural changes (insertions, renumbering), rebuild the reference map from the current document, and re-resolve every link against the fresh map.