Fees" excluded pass-throughs in the original but Amendment 2 folded them in - the agent extracted the stale exclusion...

TL;DR

Re-extract list fields after every amendment that touches the term. Treat amendment text as a patch that can add or remove list members, diff the old exclusion list against the new one, and never merge lists across versions. The agent cached the original exclusions and never re-ran extraction when Amendment 2 folded pass-throughs back into Fees.

"Fees" excluded pass-throughs in the original but Amendment 2 folded them in  -  the agent extracted the stale exclusion list

Steps

1. Detect amendments that touch the term: any amendment text mentioning 'Fees', its definition, or its exclusions.

Expected: Amendment 2 is flagged as touching the Fees definition

1. Re-run the exclusion-list extraction against the amended definition text.

Expected: a fresh exclusions list built from the post-Amendment-2 wording

1. Diff the old list against the new list and record added and removed members.

Expected: "pass-throughs removed from exclusions by Amendment 2"

1. Store one exclusion list per version; never merge members across versions.

Expected: v1 list and Amendment-2 list exist side by side, each labeled

1. Cite the amendment in the output next to the current list.

Expected: "current exclusion list (as amended by Amendment 2)"

Use this when

• An amendment changed what a defined term includes or excludes and the list output looks stale.
• Fee, cost, or charge exclusion lists do not match the latest amendment text.
• The agent extracted a list once from the base agreement and never revisited it.
• You are auditing definition-dependent lists across versions.

Not for this skill when

• No amendment touched the term; the list was wrong from the start (an extraction bug, not drift).
• The term has no list-type dependents; only the definition text matters.
• The amendment restated the definition without changing the exclusions.
• You need legal advice on whether pass-throughs are actually billable.

Variant phrasings

stale exclusion list after amendment changed the definition

amendment folded items into Fees, agent kept old exclusions

exclusion list not re-extracted after amendment

defined-term list drift across amendments

Why it happens

List extraction is expensive and usually runs once: parse the definition, pull out the exclusions, store the list. Amendments are processed as text diffs, and a one-line change like "pass-through costs are included in Fees" does not look like a list edit. The pipeline has no trigger that says "this amendment touched a term with a cached list, rebuild the list", so the stale list ships with full confidence.

Edge cases

• The amendment changes the list indirectly ("Section 3.2 is replaced", and 3.2 held the exclusions). Resolve the replacement target first, then re-extract.
• The new list is longer and the old list is shorter. Do not union them; the amendment's list is the whole truth for its version.
• The amendment moves exclusions to a schedule. Follow the pointer and extract the list at its new address.
• Multiple amendments each tweak the list. Apply them in effective-date order and keep the per-version lists for audit.

Provenance

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