Architecture

Substrate. Estate. Town.
Federation.

Agentic Primitives is built the way a place is built. The materials and the building code are the substrate. Your own property, with its front door, its staff, its records and its gate, is an estate. The street of estates that share an address book and a notice board is a town. Towns on different ground, joined by public roads, are a federation. Every screen, every agent and every receipt lives at one of these four scales, and knowing which one tells you who is in charge there.

In plain words A day in the town · 1 minute The full picture For engineers: inside the substrate

01 Substrate
Live
The materials and the building code. Nobody lives here; everything else is built from it, so every Home, town and federation behaves the same way.
Like the building code and the lumber yard: you never see them, and they are why the house stands.
If you are a person
You never touch it. It is why your agent can sign, why a permission you give can be taken back, and why there is always a receipt.
If you run an organization
The guarantees are the same whichever Home or town you use, because they come from here, not from a vendor.
If you build
Published packages and contracts. Take one capability or all nine; your app imports them, they never import you.
02 Estate
Public
Your own property. The front door where you sign in, the staff who work for you (your agents), the filing cabinet that holds your records (the vault), and the gate that checks who may come in (the edge). You hold the keys.
Like your house: your door, your help, your papers, your gate, your name on the deed.
If you are a person
This is where you sign in, decide, and keep what is yours. Nothing is done in your name without a permission you signed here, and you can take it back here.
If you run an organization
Your members, teams and treasuries live in your estate. A member acts under a role you gave; a treasury pays only within a limit you set.
If you build
ap-home is the estate product, public on GitHub. Run one for your community, or build a relying app that plugs into someone else’s.
03 Town
Public
The street your estate is on. The address book that says who lives where, the public notice board, the directories of who offers what, and the utilities every neighbour shares. Shared by all, owned by none.
Like a town: street names, a notice board, a trades directory. Being listed is not the same as being in charge.
If you are a person
How others find you and how you find them. A listing in a directory never gives anyone power over your estate.
If you run an organization
Your name is unique in the town, your public facts are readable by anyone, and your private ones stay in your vault.
If you build
Naming, discovery and registries for every estate on one chain. Build a vertical registry from the same kit; it lists, it never grants.
04 Federation
Next
Towns in different places, connected by public roads. You can visit another town and act there, but your keys never leave home; you prove what you are entitled to, sign at your own door, and keep the receipt.
Like travelling with a passport: another country can check it, but it cannot sign your name.
If you are a person
Act somewhere else, sign at home, keep the receipt. A permission you gave in one place is never quietly honoured in another.
If you run an organization
Work with organizations whose estates stand on other chains, including public ones, without moving your records or your money to them.
If you build
Public ground, proofs of standing, and the binding between one principal’s accounts. Designed, not yet built; the open questions are listed, not hidden.

The rule that runs through all four: being somewhere never gives anyone power over you. Your keys stay at your estate. A town can list you; it cannot act for you. A federation can prove what you are entitled to elsewhere; it cannot spend on your behalf.

The four scales, in full All architecture notes

01A day in the town

One person's agent, four conversations, one set of keys.

Alice's agent walks out of her front door and wears a different hat at every stop: patient at the practice, member at the church and the home group, neighbour at the rec centre. Each provider answers from its own estate with its own agent. Then she opens one shelf of her vault to her coach, and closes it when the season ends.

1 / 7 · One person, one agent, one town · ← → to step, space to pause

01 · ONE PERSON, ONE AGENT, ONE TOWN

Alice lives at the bottom of the hill. Her agent lives at her Home, next to her vault. Across town: her doctor's practice, her church and her home group, the rec centre. In the middle, the services the whole town shares. Every one of them has its own agent, at its own address.

Each has its own front door. Nobody holds anyone else's keys.

02How the street works

Eight beats on one street: discover, trust, talk, act, receipt, revoke — and the road out.

The same town, drawn flat and slowed down. One chain. A person, an organization and a service, each on their own estate; the address book, notice board, directories and the chain they share at the end of the street. Watch what crosses the street — and what never does.

1 / 8 · The street · ← → to step, space to pause

Every other picture of an "agent town" ends at the transaction. This one ends where ours actually does: the permission was signed at her door, the receipt came home to her vault, and she cut the road from the same door. Nothing on the street — not the directory, not the key service, not the chain — could have done any of those three things for her.

03The full picture

Four scales, four repositories, one rule running through them.

Each scale is its own repository. Each depends only on the one below it. Each answers a question the one below cannot, and each is held to one rule that keeps it from becoming the one above: the substrate names no deployment, the estate's vault is the record, the town grants nothing, the federation carries evidence and value but never authority.

The four scales: substrate, estate, town, federation — one repository each, each depending only on the one below — One chain per estate. One chain per town. Many chains per federation. Authority never leaves the chain it was signed into: evidence and value cross, a grant never does.

01 Substrate

Live

What is an agent, what may it do, and how is that proven?

The published packages and contracts: everything an agentic application needs, as primitives with one identity, one authority mechanism and one evidence trail.

Chain: Any EVM. The contracts are deployed per chain; nothing in a package names one.

Rule: Generic. No vertical, no brand, no hostname, no deployment. Products import it; it imports nothing of theirs.

agentictrustlabs/agentic-primitives →

Ring 0. Packages on npm, exact-pinned by consumers.

02 Estate

Public

Where does a person sign, where do her agents run, and where is the record?

One deployment of the substrate for one set of people and organizations: the Home where they sign, their agents, their vault, the edge in front of it, the Home MCP that lets a client reach the person, and the chain they enforce on.

Chain: One chain. An estate enforces on exactly one; its grants, names and anchors live there.

Rule: The vault is the record; DO storage is the serving plane. Only a person signs, and only at her Home.

agentictrustlabs/ap-home →

The Home product. Deploys Faithnet on faithchain. Public since 2026-10.

03 Town

Public

How do estates on one chain find each other, name each other and read the same facts?

Several estates on one chain and the services they share: agent naming, the public graph and discovery, registries, the KMS tenants, and the operations of the chain itself.

Chain: One chain, by definition. A town is the chain’s estates plus the services built on that chain’s state.

Rule: Nothing in a town grants. A resolver returns an address, a registry lists, a graph holds only what the chain can prove.

agentictrustlabs/ap-town →

Public. The services every estate on one chain shares: registry, public graph, naming, chain access, the town portal.

04 Federation

How does an agent from one chain act in an estate on another without authority ever crossing?

Towns on different chains, private and public, and the public ground that lets an estate in one prove its standing to an edge in another: roots, presentations, bindings between a principal’s accounts.

Chain: Many chains. Authority stays on each; evidence and value cross; a grant never does.

Rule: A message from another chain is evidence that something happened there. It is never a mandate here.

agentictrustlabs/ap-federation

Next. Spec 410 §4 is its design; the chains note names what is still open.

04Notes

Each part, drawn and explained.

The deployed names are an estate's. The shapes are the substrate's. The pictures use one vocabulary throughout: a house is a Home, a gatehouse is an edge, a vault is a vault, a hall with columns is a chain or a registry, a dome is the public graph.

2026-10-05