Applications
The layers are constant. Which boundary matters most, and how much headroom sits behind it, is not.
Small operations
Low absolute concurrency, high consequence per call, and typically nobody whose role includes noticing that something is wrong. The containment boundary carries most of the weight here.
Containment
Thresholds that stop traffic without waiting for anyone to read an alert.
Automatic failover
Redirection on loss of registration, requiring no human decision.
Legible configuration
Simple enough that a non-specialist can follow the documentation.
Honest sizing
Proportionally greater headroom than the absolute figure suggests.
Large organisations
At scale the technical boundaries are settled and the operation boundary carries the risk. Most incidents in a mature estate originate in change rather than in failure.
Governed change
A process that maps onto the control framework already in place.
Partitioned capacity
Floors and ceilings so one unit cannot consume another unit's baseline.
Evidence by default
Records produced during change rather than assembled before audit.
Bounded blast radius
Diverse interconnects and layer boundaries keeping an incident local.
Distributed teams
The access network belongs to somebody else, which puts part of the connectivity boundary outside anybody's control. Everything else is designed around that fact.
Portable identity
One extension and one policy per person, anywhere.
Short uncontrolled path
Media anchored nearest the user, minimising what nobody can configure.
Attributable quality
Per-call metrics that locate a fault outside the organisation.
Invariant policy
Recording and retention independent of location.
Contact operations
The one application where demand is a plateau rather than a peak, which changes how the connectivity boundary has to be set.
Plateau-aware sizing
Interval data rather than averages, because sustained load is not a peak.
Partition isolation
Campaign traffic bounded in both directions.
Investigable quality
Per-call metrics granular enough to act on.
Same-day reporting
Latency low enough to inform tomorrow's roster.
The layers behind all four
The layers are constant. Only the boundary that carries the weight changes.
Connectivity
The outermost layer. Whether a call can happen at all.
Open Layer twoControl
Where a call goes, and what happens when nobody answers.
Open Layer threeNumbering
What a caller dials, and whether it can ever be unreachable.
Open Layer fourOperation
Change, treated as a layer because it causes more incidents than failure does.
Open