Module 2 · Policy Engineering

Lecture 2.3

Rules

A rule is an operative statement binding conditions to a normative outcome. This lecture covers rule form, modality, and the discipline of writing one rule per statement.

Learning objectives

After this lesson, the reader should understand:

  • 01Classify a rule by modality: obligation, permission, prohibition.
  • 02Split compound prose into atomic rules.
  • 03Attach each rule to the authority that issues it.

Concept framework

Rule form

  1. 01Subject — who is bound
  2. 02Modality — must, may, must not
  3. 03Action — what is governed
  4. 04Conditions — when it applies
  5. 05Consequence — what follows

Case study

One sentence, four rules

A single compliance sentence carries four obligations. Why does that matter?

As prose, the sentence is evaluated as a unit and audited as a unit. As four atomic rules, each obligation can be tested, exempted, versioned, and reported on independently — and a partial failure is reportable as a partial failure rather than a blanket non-compliance. Atomicity is what makes remediation precise.

Discussion questions

  • When is a compound rule clearer than its atomic parts?
  • How should conflicting rules of equal authority be resolved?
  • Should a rule carry its own penalty, or reference one?

Exercise

Atomise a compliance clause.

  1. 01Split the clause into single-obligation statements.
  2. 02Label each with its modality and subject.
  3. 03State the condition set for each.
  4. 04Identify any obligation with no stated consequence.

Research notes

  • Deontic and defeasible logic.
  • Business rules management literature.
  • Normative systems in multi-agent research.