Anthropic's deprecations page opens with a model-status table (API model name / Current state / Deprecated / Tentative retirement date) listing ACTIVE models with tentative retirement dates - e.g. claude-fable-5 -> 2027-06-09, claude-sonnet-5 -> 2027-06-30. We currently skip this table and only ingest the per-announcement retirement tables.
These dates are real lifecycle signal for current models and would enrich schedule/safe_until output, but ingesting them needs design first:
- A bare
shutdown overstates certainty - tentative dates likely need date_precision: earliest or a new precision value, plus spec wording.
- Records would carry no
announced date; checker/diff semantics for announced-less scheduled entries need a decision.
- The table also lists deprecated/retired models whose rows duplicate the retirement tables - merge precedence needs defining.
- Interaction with policy floors (min_notice_days guarantees) - a tentative date beyond the floor is informative, one inside it contradicts the policy.
Surfaced during enforcement wave 2 when a corrective pass accidentally started ingesting this table (reverted for scope).
Anthropic's deprecations page opens with a model-status table (API model name / Current state / Deprecated / Tentative retirement date) listing ACTIVE models with tentative retirement dates - e.g. claude-fable-5 -> 2027-06-09, claude-sonnet-5 -> 2027-06-30. We currently skip this table and only ingest the per-announcement retirement tables.
These dates are real lifecycle signal for current models and would enrich schedule/safe_until output, but ingesting them needs design first:
shutdownoverstates certainty - tentative dates likely needdate_precision: earliestor a new precision value, plus spec wording.announceddate; checker/diff semantics for announced-less scheduled entries need a decision.Surfaced during enforcement wave 2 when a corrective pass accidentally started ingesting this table (reverted for scope).