Software Service Decommission & Dependency Readiness Review

The likely issue is a contract mismatch around software and service decommissioning, callers, jobs, data ownership, queues, DNS, credentials, dashboards, alerts, documentation, billing, compliance evidence, archival needs, sequencing, rollback limits, and operational ownership. I would first define the invariant: A software component is ready to retire only when every known dependency, data obligation, operational control, credential, scheduled path, and fallback/rollback decision has an owner and evidence. Then I would trace the smallest owning boundary, keep VERIFIED facts separate from LIKELY/UNKNOWN state, apply or propose the narrowest repair, and add deterministic normal, boundary, failure, retry/cancellation, and recovery tests. The workflow preserves authorization, privacy, security policy, public interfaces, user-visible behavior, and documented ownership. With repository/workspace access, findings can map to exact paths and focused local validation; with partial evidence, the result remains an explicit diagnosis/evidence map with no invented execution claims.