Runtime governance for delegated AI

Public services that work for people and their agents.

When software holds standing authority to act for a person, safety is decided at the service boundary. A public catalog of policy challenges and design patterns for scoping agency, tracing accountability, and keeping a path open for people.

The map

Territories

A territory is a cluster of related policy and design challenges where a service must bound, verify, or govern delegated agent use.

T1

Provenance & Intent

Telling where a submission came from, and whether it states a view the user holds or one an agent generated. Nothing in a submission's text shows who wrote it, yet the agency still has to act on it.

7 patterns
T2

Delegation & Authorization

Enforcing least agency when a user grants software standing authority to act. Identity systems prove who a person is, not the minimum scope they granted an agent or how to revoke it in flight.

14 patterns
T3

Accountability & Audit

Tracing every agent action back to a human decision-maker and halting systemic faults at runtime. Without pre-commit checkpoints and circuit breakers, a single flawed process repeats across a population before anyone sees it.

11 patterns
T4

Trust Calibration

Helping a user judge how far to rely on a government AI agent, and giving the agency a basis to support that judgment. A user can wrongly refuse an agent that would help, or lean on one a serious case needs a human for.

8 patterns
T5

Rationing & Friction

Forms, queues, and deadlines rationed services for years by demanding effort no one designed in. AI agents strip that effort away, forcing a deliberate choice about which friction only excluded people and which metered need.

7 patterns
T6

Volume vs Breadth Signaling

Reading the weight of opinion behind public submissions once agents file fluent, distinct-looking entries at scale. Volume and the look of variety can both be manufactured, so neither shows how widely a view is held.

9 patterns
T7

Representation & Equity

Keeping every user able to reach a government outcome, from a consultation to a benefit, license, or appeal, as private agents come between them and government. Left alone, outcomes start to track who has the better agent.

9 patterns
T8

Verification & Certification

Evaluating civic AI tools independently of the labs and vendors that build them. Building an authoritative-sounding agent is nearly free; verifying its reliability and backing it when it fails is not.

8 patterns
T9

Cross-border & Sovereignty

Governing sovereign exposure across the AI supply chain when a model runs, or can be legally compelled, outside the user's jurisdiction. It decides who can reach the data and whether the service can be relied on under pressure.

8 patterns
The detail

Patterns

Each pattern examines one risk at the service boundary and prototypes the control that answers it.

01

The impact of agents

How autonomous or delegated action changes the risk at this boundary.

02

What must be verified

What the relying party must confirm at runtime and who is responsible.

03

Protecting access

Who is at risk of exclusion, and what keeps the path open.

04

Response surface

Which interaction, service, or protocol control enforces the boundary.

05

Precedents & sources

What's already been done elsewhere, and how proven the response is.

Least agency at the boundary: an agent receives only the minimum scope required, off by default for standing authority, with a machine-readable grant tied to a human originator.

User The control
City Assistant · Permissions
Act without asking each time broad
Ongoing authority with no per-action confirmation. Rarely needed, off by default.
Scoped grant
Government The record
{
  "type": "standing_authority",
  "duration": "ongoing",
  "confirmation": "none"
}
Read the pattern: 2.1 Fine-grained scope negotiation

A work in progress

Feedback, corrections, and collaboration are all welcome: write to hello@agenticsurfaces.org.