## TL;DR
Treat "as updated" as a latest-revision selector. Version every schedule ingestion with its issue date and revision number, keep old revisions addressable but never the default, and resolve "as updated" / "as amended" against the newest revision. "As updated" is a pointer to the newest issue, and an agent that cached the first schedule it saw resolves a stale one.

```text
agent couldn't resolve "the Fees defined in Schedule 1 as updated"  -  the schedule was re-issued and the agent linked the old revision
```

## Steps
1. Version every schedule on ingestion: store revision number and issue date alongside the content.
   Expected: Schedule 1 exists as rev 1 and rev 2, each with its issue date
2. Parse update qualifiers ('as updated', 'as amended', 'as re-issued') as selectors for the latest revision.
   Expected: "the Fees defined in Schedule 1 as updated" resolves to rev 2
3. Keep old revisions addressable by explicit revision number for citations that name one.
   Expected: a citation to "Schedule 1 rev 1" still resolves correctly
4. Emit a revision warning whenever a citation resolves to a non-latest revision without naming one.
   Expected: a log line like "resolved Schedule 1 rev 1; rev 2 is current"
5. Invalidate the schedule cache whenever a new revision is ingested; never serve the old default.
   Expected: no extraction after re-issue returns the old fee table

## Use this when
- A citation says "as updated", "as amended", or "as re-issued" and points at a schedule.
- A schedule was re-issued and the agent still quotes the old numbers.
- Fee tables, rate cards, or price lists exist in multiple revisions.
- You are auditing whether extractions used the current revision.

## Not for this skill when
- There is only one revision of the schedule; nothing is stale.
- The citation names a specific revision explicitly and the agent honored it.
- The fees are defined inline in the agreement body, not in a schedule.
- The issue is OCR damage to the fee table, not revision selection.

## Variant phrasings
### agent linked the old revision of a re-issued schedule
### "as updated" schedule reference resolves to stale version
### fee schedule re-issued, extraction still shows old rates
### Schedule 1 revision mismatch in clause extraction

## Why it happens
Schedule ingestion is usually write-once: the first PDF the agent sees becomes "Schedule 1" in the index, and a re-issued schedule either overwrites it silently or gets indexed as a separate document nobody links. "As updated" is parsed as decoration rather than as a version selector, so the citation binds to whatever the cache holds. The numbers look authoritative because they came from a real Schedule 1, just not the current one.
## Edge cases
- The re-issued schedule is dated but not numbered. Order by issue date and treat the newest as current.
- The new revision only updates some line items. Carry forward unchanged items explicitly and mark which revision each line came from.
- Two revisions share an issue date. Prefer the higher revision number; if neither is numbered, flag for operator review.
- The citation says "as updated" but the update lives in an amendment, not a re-issued schedule. Check the amendment chain before declaring the revision current.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_rnFplS-00DABOzEmuxwDPA