Module 2 · Policy Engineering

Lecture 2.5

Conditions

A condition is the point at which authority meets fact. This lecture examines evaluability: which conditions a machine can test, which require judgement, and how the boundary is declared.

Learning objectives

After this lesson, the reader should understand:

  • 01Classify conditions as evaluable, evidenced, or judgement-bound.
  • 02Specify the fact source for each evaluable condition.
  • 03Design a referral path for judgement-bound conditions.

Concept framework

Condition classification

  1. 01Evaluable from structured facts
  2. 02Evaluable from attested evidence
  3. 03Requires human judgement
  4. 04Requires a further authority

Case study

'Reasonable steps'

How should an artifact handle a condition that requires reasonableness?

It should not pretend to evaluate it. The artifact marks the condition as judgement-bound, halts the automated path, and refers the case with the evaluated context attached. The value is not that the machine decided — it is that the boundary between machine and human judgement is now explicit, recorded, and auditable, instead of being absorbed silently by whoever happened to handle the case.

Discussion questions

  • Can a judgement-bound condition ever be proxied by a metric?
  • Who owns the fact sources an artifact depends on?
  • What should happen when a fact is unavailable?

Exercise

Classify the conditions in one rule.

  1. 01List each condition separately.
  2. 02Assign a class to each.
  3. 03Name the fact source or the referral route.
  4. 04Note the behaviour when a fact is missing.

Research notes

  • Evidence law and standards of proof.
  • Data provenance and attestation.
  • Human-in-the-loop decision architecture.