Lecture 3.2
If the operating system is not a set of written rules, what is it made of? This lecture introduces the decision boundary — the point at which an institution's answer changes — as the unit that makes an unwritten system measurable rather than merely acknowledged.
Learning objectives
After this lesson, the reader should understand:
Concept framework
Anatomy of a boundary
Case study
A procurement team's records show near-universal approval below £48,000 and near-universal escalation above it. The written limit is £50,000. Where is the boundary?
At £48,000. The written figure states intent; the observed figure states practice, and the difference between them is recorded nowhere. The gap is not noise — it is stable across years and across officers, which is precisely what makes it a boundary rather than variance. Note carefully what the observation does not establish: whether £48,000 represents prudent caution or an unauthorised tightening that has been quietly denying suppliers a hearing. Locating a boundary and judging it are separate operations, and collapsing them is the most common error in this work.
Discussion questions
Exercise
Recover a boundary from records.
Research notes