Inside my practice · Enterprise software
We ship Fridays. That is who we are.
A routine release rhythm took precedence over an unresolved identity-mapping risk for customers.
What the situation reveals
The operating condition
Cultural habit substituted for explicit authorization of residual access risk.
The move I would make
Give a named owner authority to freeze a release until identity conditions are met.
The question to take into the room
Who may stop a deployment when a tenant’s access cannot be certified?
Explore the architecture
Follow the condition through the system.
Start with VERTO, then examine where the other disciplines alter the decision or its consequences.
Bring it into your work
Who may stop a deployment when a tenant’s access cannot be certified?