Skip to content

[Phase E] Retirement watcher: start the successor's onboarding, with a deadline, when a configured model gets a retirement date #2130

Open

Description

@github-actions

Story

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

  1. The daily detection run also checks every model in the configured chains for a provider-reported retirement or deprecation date.
  2. 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.
  3. 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.
  4. The logic is a pure function with bats on fixture API responses (no retirement, retirement with successor, retirement without successor, deadline too close).

Tasks / Subtasks

Dev Notes

Project Structure Notes

Extends the detection library and workflow from Phase A.

References

Story prepared by the BMAD Scrum Master (Bob) for epic #2113. Status: ready-for-dev.

Metadata

Metadata

Assignees

No one assigned

    Labels

    initiativeEpic / initiative tracking issue

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions