Computable·Authority
← Module 6 · The Future of Authority

Lecture 6.5

Objections

A discipline is only as strong as its answers to the obvious challenges. This lecture takes the five that recur — that this is just access control, just policy-as-code, unworkable if the encoding is wrong, impossible because law needs interpretation, or unnecessary with a human in the loop — and answers each on its merits.

Lesson 37 / 39Start the course to keep your place and get the rest by email.

Learning objectives

After this lesson, the reader should understand:

  • 01State each recurring objection in its strongest form.
  • 02Give the substantive answer, not a rebuttal by assertion.
  • 03Identify the objection that is partly correct and what it correctly identifies.

Concept framework

Five objections

  1. 01"Just access control" — identity may pass and authority still deny
  2. 02"Just policy-as-code" — the lifecycle around the policy is the point
  3. 03"What if the encoding is wrong" — make compilation explicit and reviewable
  4. 04"Law needs interpretation" — agreed; represent the boundary, escalate past it
  5. 05"Just keep a human in the loop" — humans set the boundary; they cannot adjudicate every action

Case study

The strongest objection

'What if the institution encodes its authority incorrectly? You have just given a wrong rule a runtime and a seal.' What is the honest answer?

That the risk is real and the discipline does not eliminate it. What it does is make the failure visible instead of silent. An incorrect prose policy fails through inconsistent human application that no one records. An incorrect artifact fails the same way a defective program does — reproducibly, against a version, traceable to the compilation step that introduced it — and the response is the same: source provenance, review by the authority holder, conformance testing, version control, independent inspection. The objective was never a representation that cannot be wrong. It is that an error in authority does not get to become invisible software behaviour.

Discussion questions

  • Which of the five objections is strongest, and does it change the design or just its framing?
  • Is 'partly access control' a fair description, and where does the analogy break?
  • What review regime would you require before an artifact could execute?
  • Does making interpretation explicit reduce discretion, or relocate it?

Exercise

Steelman one objection and answer it.

  1. 01Pick the objection you find most persuasive.
  2. 02Write it in its strongest form, with a concrete example.
  3. 03Write the answer, conceding whatever is true in it.
  4. 04State what would have to change in the architecture if the objection held.

Research notes

  • Access control models — the resource-permission frame and its limits.
  • Policy-as-code tooling — expression and evaluation versus lifecycle governance.
  • Legal formalism and its critics — the interpretation objection.
  • Automation in administrative practice — the limits of human-in-the-loop at scale.
  • Computable Authority, §14 — 'Objections'.
All lectures in this moduleGlossary of terms