Recap. The platform is politically visible again — for now. Meanwhile, the provider ships a new well-architected pillar and deprecates something the hub depends on.
Series In Production · 6
Part of In Production. Browse the series overview for every part.
Outline
- Hook: The email: service retirement in twelve months, production dependency confirmed
- Context: Version-pin and fall behind vs. track and absorb churn
- The landing zone refresh: Refactor foundations while carrying live tenants
- NZ field note: Running a major platform version upgrade underneath people who did not know they were standing on it
Sections to Draft
- Provider change register — what the platform team must watch
- Refresh cadence vs. tenant communication
- Rollout pattern: canary management group, then waves
- Steal-this checklist
Next in the Series
Part 7 — “Key Person Risk and the Bus Number of One.” The person who understands the identity model leaves — and knowledge lives in exceptions, not docs.
One Block · build from here
List every production dependency with a retirement date in the next eighteen months — and name the tenant who will notice first.