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.
Territories
A territory is a cluster of related policy and design challenges where a service must bound, verify, or govern delegated agent use.
Patterns
Each pattern examines one risk at the service boundary and prototypes the control that answers it.
The impact of agents
How autonomous or delegated action changes the risk at this boundary.
What must be verified
What the relying party must confirm at runtime and who is responsible.
Protecting access
Who is at risk of exclusion, and what keeps the path open.
Response surface
Which interaction, service, or protocol control enforces the boundary.
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.
{
"type": "standing_authority",
"duration": "ongoing",
"confirmation": "none"
} Case studies
Real failures and step-by-step scenarios that show what the patterns are for.
See all case studiesA work in progress
Feedback, corrections, and collaboration are all welcome: write to hello@agenticsurfaces.org.