When an autonomous AI agent acts on your behalf indefinitely, what does consent mean? Temporal consent, consent decay, and contextual permission..
| Dimension | Traditional UX | Agentic Experience Design (AXD) |
|---|---|---|
| Primary material | Attention and affordance | Trust and delegation |
| User state | Present, navigating | Absent, delegating |
| Design output | Screens and interfaces | Outcomes and constraints |
| Temporal model | Session-based | Relationship-based |
| Success metric | Task completion | Trust calibration |
Consent expires because human intentions, circumstances, and preferences change over time. A user who authorised an agent to buy groceries weekly may have changed dietary requirements, moved house, or changed financial circumstances. The consent horizon forces agents to periodically re-validate their authority rather than operating indefinitely on stale permissions.
AXD designers must build consent decay models that estimate when original authorisation becomes unreliable. This involves tracking time elapsed, context changes, and scope drift. When the consent horizon is reached, the agent must gracefully interrupt the user to re-establish authority - balancing the cost of interruption against the risk of acting on expired consent.
Consent expires because human intentions, circumstances, and preferences change over time. A user who authorised an agent to buy groceries weekly may have changed dietary requirements, moved house, or changed financial circumstances. The consent horizon forces agents to periodically re-validate their authority rather than operating indefinitely on stale permissions.
AXD designers must build consent decay models that estimate when original authorisation becomes unreliable. This involves tracking time elapsed, context changes, and scope drift. When the consent horizon is reached, the agent must gracefully interrupt the user to re-establish authority - balancing the cost of interruption against the risk of acting on expired consent.
The Observatory · Issue 007 · August 2026 Designing Permission for Systems That Never Stop Acting There is a corridor in every permission system. It begins at the moment of consent - the click, the signature, the spoken "yes" - and it extends forward in time toward a horizon that the person giving consent cannot see. In screen-based design, this corridor was short. You consented to a transaction, and the transaction completed. You agreed to terms of service, and the terms governed a relationship you could exit at any time by closing the app. The corridor had walls you could see, a floor you could feel, and a door at the end you could walk through. In agentic systems, the corridor stretches toward infinity. When you This is the consent horizon: the temporal boundary beyond which the person who gave consent can no longer meaningfully predict or control what their consent authorises. And it is the most underexamined design challenge in The consent mechanisms we have inherited from web-era design are catastrophically inadequate for agentic systems. The checkbox, the cookie banner, the terms-of-service scroll - these are consent theatre. They create a legal record of agreement without creating genuine understanding, genuine choice, or genuine control. They are designed to protect the organisation, not to empower the individual. In screen-based design, this inadequacy was tolerable because the consequences of uninformed consent were relatively contained. You agreed to cookies you did not understand, and the result was targeted advertising you found mildly annoying. You accepted terms of service you did not read, and the result was a data-sharing arrangement you would have objected to if you had known about it but that did not materially harm you. In agentic systems, uninformed consent has teeth. When you delegate financial authority to an autonomous agent without fully understanding the scope of that delegation, the agent can make decisions that cost you mon