SYSE.40:1 - Problem frame

Use this pattern when bursts, expensive work or a failing dependency prevent other users from obtaining supported platform results. Start with the constrained resource and the workload classes consuming it, including the control and recovery work needed to keep the service operable.

The first result is a tested capacity-protection arrangement for a stated operating envelope, or the exact unqualified envelope. It includes admission, bounded waiting, separation, deadline/retry limits and useful rejected or degraded outcomes.

If ordinary demand already fits a qualified envelope and no consequential coupling exists, do not add isolation machinery merely for architectural symmetry. If an active failure needs immediate mitigation, use SYSE.38. Continuing allocation of operating work remains an operating responsibility; this pattern engineers the means and limits.