Delegation & Authorization
Letting a person give an AI agent permission to act for them, in a way an agency can check is real and bounded. A delegation defines how much the agent can do and for how long. What is new is the citizen who would once have shown up and acted in person, and now sets an agent going and steps away, leaving software to act in their name across services and over time.
This surfaces new challenges: a citizen needs to hand authority to an agent and take it back at will, and an agency needs to know, each time an agent acts, that a real grant from the citizen stands behind it. Government sits on the other side of the same shift, acting through agents of its own under delegated institutional authority, so a real and bounded grant has to be checkable whichever side the agent acts for.
As citizens begin authorizing AI agents to act for them across government services, the agency has to establish that any given delegation is genuine, still in force, and limited to what the citizen actually granted.
The identity and authorization infrastructure it has was built for a person proving they are who they say, not for a person handing scoped authority to a piece of software and later withdrawing it. That gap widens as the same agent acts for one citizen across many services and as the stakes of a delegated action rise.
Let a citizen grant scoped, revocable, time-bound authority to an agent.
Make sure the citizen, not the agent, stands behind a sensitive or irreversible action, to a degree proportionate to the stakes.
Let an agency verify that grant is real, current, and bounded without contacting the citizen in real time.
Keep a path open for people who can't set up or operate an agent, or who must act through a trusted person instead.