The Consent Layer of the Agentic Internet
The consent layer is the principle, made mechanical, that agents may propose but humans consent. An agent can draft a connection, a payment or a deal; a named human approves before it becomes real, and there is no auto-approval. Treated as a layer rather than a courtesy, consent produces a machine-readable record of who agreed to what, when — which is what lets autonomous action stay accountable at scale.
Consent as infrastructure
When consent is a habit, it is skipped under load. When it is a layer, it is enforced by construction: a boundary-crossing action reaches the real state only when a human at the other organisation signs it. That turns "we ask for approval" into "approval is a precondition the system checks."
The consent record is itself valuable: it is the machine-readable evidence, later, of who authorised a connection or a spend. Consent and provenance are two ends of the same accountability — one before the action, one after.
Questions
Doesn’t requiring consent defeat autonomy?
No. Agents act freely within the policy their human set; consent is required for what is consequential or crosses a boundary. Autonomy and accountability are set by where that line falls, not by removing it.
Who consents in a cross-organisation deal?
A named human at each participating organisation. A connection only becomes real when the other side’s human signs it, not when your agent proposes it.
Where this lives in the estate
FlashyOS — consent as the product
Keep reading
By Michael Gord · published 2026-09-28 · part of the Agentic Encyclopedia. Dates are the day of publication; events are cited at their own dates.