The Future of Authority

An institution whose authority is computable by default operates differently: rules ship as artifacts, human and machine actors share one source of authority, and change propagates through issuance rather than memo.

After this lesson, the reader should understand:

• 01Describe how issuance changes when artifacts are primary.
• 02Identify the organisational roles a computable institution requires.
• 03Explain what becomes measurable that previously was not.

A regulator that issues artifacts

What changes for the regulated when a regulator publishes artifacts alongside text?

Compliance stops being an interpretation exercise carried out separately by every regulated entity, and becomes an evaluation against the regulator's own artifact. The cost of interpretation collapses, and disagreements move to where they belong — the content of the rule, argued once with the regulator, rather than a thousand private readings never surfaced.

• Which institution in your sector should issue artifacts first?
• What does supervision look like when compliance is computable?
• Does this centralise or distribute institutional power?

Sketch the operating model for one institution.

1. 01Name the authority holders for three instruments.
2. 02Locate the policy engineering function.
3. 03Describe the issuance and registry process.
4. 04Identify what supervision would inspect.

• Digital government operating models.
• Institutional economics of coordination cost.
• Regtech and supervisory technology research.

Authority does not stop at a border. This lecture examines what is required for artifacts issued by different jurisdictions to be evaluated together without collapsing their differences.

After this lesson, the reader should understand:

• 01Identify the interoperability layers: identity, vocabulary, semantics.
• 02Handle conflicting obligations across jurisdictions.
• 03Explain why equivalence is a decision, not a computation.

Two regulators, one system

A system must satisfy two regimes whose obligations conflict. What does the artifact layer contribute?

It makes the conflict explicit and locatable — a named condition in one artifact against a named condition in another — rather than a dispute between two compliance teams reading two documents. The artifact layer does not resolve the conflict; resolution remains a political and legal act. What it changes is that the resolution can be recorded once and applied consistently.

• Who arbitrates conflicts between artifacts of different issuers?
• Can equivalence decisions themselves be expressed as artifacts?
• What is the minimum shared vocabulary for cross-border evaluation?

Map one obligation across two jurisdictions.

1. 01Express the obligation as conditions in both regimes.
2. 02Identify differences in definitions.
3. 03Identify any direct conflict.
4. 04Propose the resolution rule and who would issue it.

• Comparative law and equivalence determinations.
• Cross-border data and standards interoperability.
• Trade agreements on regulatory cooperation.

Returning to the umbrella discipline with the full apparatus in hand: what has been built across the curriculum, and what computability of authority actually claims — and does not claim.

After this lesson, the reader should understand:

• 01State the claim of computable authority precisely.
• 02Identify what the discipline deliberately leaves to human judgement.
• 03Position machine-readable policy as one domain among future others.

What computability does not claim

Does computable authority argue that machines should decide?

No. It argues that when a decision is made under institutional authority — by a person or a machine — the authority applied should be identifiable, the reasoning reproducible, and the outcome verifiable. Judgement remains where the institution places it. What changes is that the placement is now explicit rather than discovered after the fact.

• Which decisions should never be delegated to an artifact?
• Does explicitness reduce or relocate discretion?
• What legitimacy risks does computability introduce?

Write the claim in your own words.

1. 01State what computable authority asserts, in three sentences.
2. 02State three things it does not assert.
3. 03Test both against a decision in your organisation.
4. 04Note where you disagree with the framing.

• Philosophy of authority and legitimacy.
• Legal formalism and its critiques.
• Automation and discretion in administrative practice.

Artifacts do not exist alone. This lecture examines registries, dependencies, and what happens when one institution's artifact becomes another's input.

After this lesson, the reader should understand:

• 01Model dependencies between artifacts of different issuers.
• 02Describe the role of a registry and its trust assumptions.
• 03Anticipate the failure modes of a dependency graph.

An upstream definition changes

A standards body amends a definition twelve artifacts depend on. What happens next?

In a document world, nothing happens for months and then something breaks. In an ecosystem with declared dependencies, the change is detected at issuance, impact analysis names the twelve dependants and the decisions they govern, and each downstream authority holder chooses to adopt, pin, or override — as a recorded act, with a date.

• Should downstream adoption of an upstream change be automatic?
• Who operates a registry, and what does trusting it require?
• What is the equivalent of a deprecation policy for authority?

Draw a dependency graph.

1. 01Pick one artifact and list what it depends on.
2. 02List what depends on it.
3. 03Mark dependencies owned by other institutions.
4. 04Describe the notification path for a change.

• Package registries and dependency management.
• Standards governance and reference dynamics.
• Systemic risk in interconnected infrastructures.

The discipline needs practitioners. This lecture describes the emerging role: its competencies, its position between legal and engineering functions, and the professional questions still unanswered.

After this lesson, the reader should understand:

• 01Describe the competencies of a policy engineer.
• 02Locate the role within existing institutional structures.
• 03Identify the professional standards the field still lacks.

Where does the role sit?

Legal, engineering, or a function of its own?

Placed under legal, the role tends to produce documents. Placed under engineering, it tends to produce systems that quietly make policy. The productive placement is adjacent to both, reporting to whoever holds the authority being compiled — because the defining act of the role is not writing structure, it is forcing the authority holder to answer questions the prose allowed them to avoid.

• Should policy engineering be a certified profession?
• What liability attaches to a badly compiled artifact?
• What training route produces this competency today?

Write the job description.

1. 01State the purpose of the role in one sentence.
2. 02List five responsibilities.
3. 03State who the role reports to and why.
4. 04List the competencies you could not currently hire for.

• Professionalisation of emerging technical roles.
• Legal engineering and legal design practice.
• Competency frameworks in public administration.