Module 2 · Policy Engineering

Lecture 2.4

Exceptions

Exceptions are where most policy failures live. This lecture treats the exception as a first-class object with its own conditions, authority, and expiry.

Learning objectives

After this lesson, the reader should understand:

  • 01Distinguish an exception from a condition and from a waiver.
  • 02Express precedence between a rule and its exceptions.
  • 03Handle exceptions granted by a different authority.

Concept framework

Exception anatomy

  1. 01Rule displaced
  2. 02Trigger conditions
  3. 03Granting authority
  4. 04Duration or expiry
  5. 05Recorded justification

Case study

The standing emergency exemption

An exemption granted for an emergency is still in force four years later. Why?

Because nothing in the document expressed an expiry, and nothing in the process re-evaluated the trigger. As an artifact, the exception carries its own conditions and an expiry, and the runtime stops applying it when the conditions no longer hold. The failure was not the exemption — it was expressing a temporary displacement in a form with no notion of time.

Discussion questions

  • Should exceptions ever be permanent?
  • Who audits the population of live exceptions?
  • How do overlapping exceptions resolve?

Exercise

Model one exception completely.

  1. 01Name the rule it displaces.
  2. 02State its trigger conditions precisely.
  3. 03Name the granting authority and the expiry.
  4. 04Describe what happens on expiry.

Research notes

  • Defeasible reasoning and priority orderings.
  • Administrative law on waivers and derogations.
  • Exception handling in safety-critical specification.