# Sunset Census

> Find the third-party integrations that will break on a known date - a version sunset, an SDK end of life, a
> credential expiry, a payload retirement - and decide when the old surface is safe to turn off. List what retires
> and every integration still calling it; the browser classifies each by the migrated rule, ranks them by days to
> break and end customers affected, sizes the top tier by outreach hours and reads the five-line readiness gate.
> Metered runs write the outreach plan, and the go/no-go memo. Built on the SkillSafe skill
> @samber/integration-health-monitoring, from samber/developer-platform-skills (MIT), by Samuel Berthe.

https://sunset-census.skillsafe.ai/

## What is free
- The catalog: every dated risk with days to break; risks with no date flagged; compression when fewer than three notice intervals remain.
- The census: migrated only after one full business-cycle lookback with no old call following the first replacement call, or on written confirmation; partial movers (a replacement call, then old calls again), dormant credentials (never expired inside the program) and rows left unknown by short logs called out.
- The ranking: days-to-break buckets against the escalation interval, then end customers affected (installs), never call volume; contract weight promotes a row; the top tier holds as many rows as the outreach hours allow.
- The rungs: targeted email and in-response warnings by default, named outreach for the top tier, the customer-admin notice, brownouts only once the replacement holds, the dashboard report.
- The readiness gate, line by line, the door to new integrations, verified-contact coverage, a ranked census (.csv), one notice skeleton per integration, the checks (.csv) and everything (.json).

## The metered lanes
Two tasks on gpt-terra, metered per run, routed by `task`. Input string fields: `task` (plan or memo), `program`, `census`, `carry` (memo only: the plan's decisions) and `facts`.
- `plan` replies with `summary`, `ladder` (six rungs as ranked), `top_tier` (each open top-tier integration with an action and a date), `brownouts`, `door`, `notice`, `dormant` and `caveats`.
- `memo` replies with `summary`, `verdict`, `lines` (five, with the page's statuses), `exceptions` (per integration), `next` and `caveats`.
The page holds every reply to its own facts: the ranked ladder, exactly the open top-tier integrations with dates before their break, escalating brownouts inside the window or none when line 4 blocks them, the door closed to new identities, the full notice payload; the page's verdict and line statuses, no share-of-calls percentage, exceptions per integration with an owner, a reason and an expiry.

## Links
- API tutorial: https://sunset-census.skillsafe.ai/api.html
- Source skill: https://skillsafe.ai/skill/@samber/integration-health-monitoring