Module 4 · Executable Authority

Lecture 4.4

Policy Versioning

Every decision was made under some version of the rules. This lecture covers immutable issuance, effective dates, and replaying past decisions against past authority.

Learning objectives

After this lesson, the reader should understand:

  • 01Bind a decision to the artifact version in force at the time.
  • 02Distinguish issuance date from effective date.
  • 03Handle retrospective amendment correctly.

Concept framework

Version binding

  1. 01Immutable artifact identity
  2. 02Issuance and effective dates
  3. 03Supersession chain
  4. 04Decision-to-version binding
  5. 05Replay against historical authority

Case study

The retrospective amendment

A rule is amended with effect from a past date. What happens to decisions already made?

With versioned artifacts the question is answerable: identify every decision bound to the superseded version whose facts fall inside the amended window, re-execute against the new version, and report the delta. Without versioning, the institution can only estimate. Retrospectivity is a policy choice; the ability to compute its consequences is an engineering property.

Discussion questions

  • Should artifacts ever be amended in place?
  • How long must superseded versions remain executable?
  • Who decides that a change is material?

Exercise

Design a version scheme for one instrument.

  1. 01Define what constitutes a material change.
  2. 02Define the identity and numbering rule.
  3. 03Define the retention period for superseded versions.
  4. 04Describe the replay procedure.

Research notes

  • Temporal databases and bitemporal modelling.
  • Point-in-time consolidation of legislation.
  • Semantic versioning and change classification.