Services" meant implementation in v1 and expanded to managed hosting in Amendment 4 - the agent's term glossary kept...

TL;DR

Version the term glossary per amendment. Every amendment that redefines a term opens a new glossary version tagged with its effective date, and every extraction cites which glossary version it used. Defined terms are mutable, and a single global glossary freezes the first definition the agent saw, so "Services" keeps meaning implementation long after Amendment 4 expanded it to managed hosting.

"Services" meant implementation in v1 and expanded to managed hosting in Amendment 4  -  the agent's term glossary kept the v1 definition

Steps

1. Parse the definitions section of every amendment, not just the base agreement. Expected: "Services" has a v1 definition and an Amendment 4 definition, each tagged

2. Attach effective dates to glossary versions so each version has a validity window. Expected: "Services v2 valid from the Amendment 4 effective date onward"

3. Require every extraction that uses a defined term to cite the glossary version. Expected: citations read like '"Services" (glossary v2, Amendment 4)'

4. Re-run extraction whenever a new amendment is ingested; any output whose glossary version is no longer current gets flagged stale. Expected: zero extractions cite a superseded definition after re-ingestion

5. Diff glossary versions in the report so operators see exactly what changed per term. Expected: a before/after line for "Services": implementation vs implementation plus managed hosting

Use this when

• A defined term changed meaning across amendments and extraction uses the old one.
• The agent's glossary is built once from the base agreement and never updated.
• Output cites a definition that an amendment superseded.
• You are auditing term consistency across a multi-amendment bundle.

Not for this skill when

• The term was never redefined; the glossary is correct and current.
• The issue is a missing definition, not a changed one.
• The term is used in its ordinary-language sense and was never defined.
• You need a legal opinion on which definition applies to a dispute.

Variant phrasings

defined term changed by amendment, agent uses old definition

term glossary not updated after amendment

"Services" definition drift across amendments

agent extracted with stale defined-term glossary

Why it happens

Glossaries are built at index time from the base agreement, because that is when the definitions section is biggest and cleanest. Amendments get parsed for operative changes, and their one-line redefinitions ("'Services' shall now include managed hosting") look like minor text, not like schema changes. The glossary is treated as static reference data, so it never re-opens, and every later extraction inherits the v1 meaning.

Edge cases

• An amendment narrows a term instead of expanding it. Same mechanism; the validity window still flips at the effective date.
• The redefinition lives in an exhibit, not the amendment body. Parse definitions in exhibits with the same versioning.
• Two amendments redefine the same term differently. The latest effective version wins; keep the full version history for audit.
• A term is redefined but the old definition still governs pre-amendment periods. Citations about past periods must use the version in force at that time, not the latest.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstRGpUx2Yto5Il74jQpw-uw