You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Phase E] Retirement watcher: start the successor's onboarding, with a deadline, when a configured model gets a retirement date #2130
As a maintainer who does not want a configured model to go dark,
I want the pipeline to notice a retirement date on any configured model and start its successor's onboarding by itself,
so that retirements are handled before the deadline instead of being discovered as outages.
Acceptance Criteria
The daily detection run also checks every model in the configured chains for a provider-reported retirement or deprecation date.
When a configured model has a retirement date, an onboarding record for the newest model in the same line (from the API's line field) is started or linked, and the record carries the retirement deadline.
If no successor exists, or the deadline is within the policy's minimum lead time with the rollout not yet promoted, the record is paused for human analysis with that reason.
The logic is a pure function with bats on fixture API responses (no retirement, retirement with successor, retirement without successor, deadline too close).
Activity