Impact GateReview changes
Use Retirement Radar
Assess static, runtime, and measured function evidence, record a review for the current snapshot, and plan removals with service owners.
On this page
What a candidate means#
Retirement Radar collects APIs for evidence review. The evidence state and next action summarize what is known about static callers, runtime coverage, API request counts, attributed function calls, and external usage. An item is a starting point for investigation.
Use Needs runtime coverage, Static callers found, Measured usage observed, and Unknown external usage to choose the next evidence step. Review state is independent and tied to the workspace snapshot.
Record an evidence review#
Find the endpoint
Search candidate paths or reasons, or filter by status. Review its static caller count and runtime label.
Open Review evidence
Read the candidate reason and follow the provider and available caller source references.
Verify outside the index
Check relevant traffic, consumers outside the selected repositories, externally maintained clients, and team migration obligations before planning a removal.
Mark reviewed for this snapshot
An owner or admin with a verified email can record the review using Mark reviewed for this snapshot. Wait for server confirmation.
Revisit changed evidence
A later snapshot can show Previous snapshot — review updated evidence. Reopen the evidence and record a fresh review when appropriate. Use Mark needs review to remove the current acknowledgment.
Plan a removal#
- Confirm which consumers and deployment environments are outside the indexed scope.
- Agree on a migration window and ownership with affected teams.
- Keep API contracts consistent with the proposed implementation change.
- Review the removal PR's report and all coverage gaps.
- Use your established production observation and rollback procedures.