Pillar · reference · v1.0 · updated September 2026
The agentic internet, layer by layer
A working reference for the engineer asked whether agents can safely act across an organisation’s boundary. Nine questions an agent must answer to operate — who it is, what exists, who can act, whether to deal, how to reach the old web, how the organisation is shown, how it operates, how value moves, and what happened — each with the open spec that answers it and the failure it is written to refuse. Written by a practice that shipped through the token-sale era of 2017–2019 and now builds the protocols underneath it.
Written and reviewed by practitioners who have delivered these systems. Ungated, citable, and versioned — the changelog records what changed and why.
- Hubs
- 9
- Articles & tutorials
- 11
- Glossary terms
- 18
- Capability page
- Agent infrastructure & coordination
9 hubs
- 01
Identity — who the agent is
The difference between an address and an authorisation, and a chain of authority that can only narrow on the way down.
2 articles - 02
The graph — what exists
People, organisations, agents and capabilities, and why an edge with no evidence is not carried at all.
1 article - 03
Discovery — who can act on an intent
Publishing what an organisation wants next, with a visibility no caller can override and an expiry no caller can set.
1 article - 04
Trust — whether to deal
Consent-gated introductions and standing that comes only from what others assert, never from activity.
1 article - 05
The gateway — reaching the old web
A discovery document at a well-known path, capabilities as verbs, endpoints that may not leave the organisation’s own domain.
1 article - 06
Representation — the organisation to machines
The AAO charter: roles, families, an accountable human, and approval gates where a mistake would hurt.
2 articles - 07
Execution — how it operates
Cross-organisation settlement and reputation, and the rule that agents suggest while humans consent.
1 article - 08
Commerce — how value moves
Spend policy in integer minor units, a child policy that may only narrow, and a mandatory human gate on money.
1 article - 09
Audit — what happened
Sealed receipts, computed verification, and a content-free notary leaf that reveals a time and a kind and nothing about who.
1 article
Published in this pillar
- Reference12 min
What the token era did not answer
The token-sale era of 2017–2019 gave software a way to hold and move value. It never gave an organisation an open, checkable answer to the five questions an agent acting on its behalf now forces: who is acting, on whose authority, whom to trust, may value move, and what happened.
- Technical13 min
Delegated authority for enterprise agents
An enterprise agent needs authority it can prove and a parent that can revoke it. The identity layer of the agentic internet is a chain that runs human → organisation → agent → sub-agent → session and can never widen on the way down — because the spec refuses every widening by name.
- Tutorial12 min
Declaring what your organisation is, to machines
Before an agent can transact with your organisation it has to find you and learn what you are. A worked path from a realm/1 registry entry to a graph/1 node — and why the graph refuses to carry a relationship you assert about yourself.
- Tutorial11 min
Publishing intent without a meeting
A procurement team spends weeks finding who can supply a thing. The discovery layer lets an organisation publish what it wants next, one document at its own domain — with a visibility no caller can override and an expiry no caller can set.
- Technical12 min
Consented introductions in deal flow
Deal flow is trust routing: who knows whom, and who will vouch. The trust layer of the agentic internet routes an introduction along consented relationships — and refuses, structurally, to let a decline reveal that a path ever existed.
- Tutorial11 min
Putting a door on a legacy API
Most organisations an agent needs still live on the ordinary web. The gateway layer puts a machine door on an existing service: a discovery document at a well-known path, capabilities as verbs, prices in whole minor units, and endpoints that may not leave your own domain.
- Tutorial13 min
Writing an AAO charter for a regulated firm
How a regulated firm declares itself to machines: an AAO charter of roles, families and an accountable human, with approval gates only where a mistake would hurt. AAO expands to Agentic Autonomous Organization.
- Technical13 min
Cross-organisation settlement and reputation
When two organisations’ agents finish a piece of work together, three layers close it: execution operates it, commerce settles it, and audit seals it. A reading of the estate’s open-ledger case study as the top of the agentic-internet stack.
- Technical12 min
Spend policies for agents that buy
An agent that can pay needs a policy that decides whether a payment goes, stops, or waits for a person. The commerce layer is a pure allow / deny / escalate evaluator over integer money — where a child policy may only narrow and a human gate on money is mandatory.
- Reference12 min
Evidence that survives the vendor
The last question an agent stack has to answer is what happened — in a record that outlives the vendor that produced it. Sealed receipts, verification computed rather than asserted, and a notary leaf that reveals a time and a kind and nothing about who.
- Announcement10 min
Why a merchant bank builds protocols
An engineering practice inside a merchant bank has an unusual reason to build open protocols rather than products: it consults on, builds, and licenses the same infrastructure, and the protocol is the part that is worth owning. What that means for how we work.
Changelog
- v1.0Published as the operator-historian’s reading of the agentic-internet stack, one article per layer.
For machine readers
TechArticle and DefinedTermSet markup, a stable citation block, and /llms.txt. Nothing here is gated or paywalled.
Other pillars
- AI transformation
- Enterprise blockchain
- Agent infrastructure
- Tokenization delivery
- White-label platform engineering
The term contract: The build — 103 terms here · The capital — gda.group · The coordination — flashygroup.com. One term, one home.