Repositories · by scale
Platform
Each offering is independently adoptable and depends only on the ones below it. Together they are every capability an agentic application needs — from a person's first passkey to the receipt for an AI agent's last action.
01Where it runs
Home for people and ceremonies, a runtime for agents, vaults for records, an edge for admission, and a chain for the anchor. Your application is a relying app: an OIDC client and an A2A caller. The estate product is ap-home, public on GitHub; the estates on one chain share a town; towns across chains form a federation.
01 Substrate
LiveChain: 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
PublicChain: 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.
The Home product. Deploys Faithnet on faithchain. Public since 2026-10.
03 Town
LiveChain: One chain, by definition. A town is the chain’s estates plus the services built on that chain’s state. A town may root its names at another town (hopenet roots at faithchain) while keeping a local table.
Rule: Nothing in a town grants. A resolver returns an address, a registry lists, a graph holds only what the chain can prove.
Two towns live: faithnet.town (faithchain) and hopenet.town (hopechain). Registry, public graph, typed naming, chain access, the town portal.
04 Federation
LiveChain: 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 →
Live at ap-federation.faithnet.io: neutral-ground registry, doors with the predicate grade, member payment, two towns on two chains; scheduled gates prove it.
The four scales, one repository each: Substrate, estate, town, federation → · Building by building: The estate and the federation → · What crosses a chain: Chains and estates →
02Live
Screens from the running faithnet estate, signed in as the Home's demo people. Every product here is a relying application of the same substrate.
01 Identity
Smart Agent accounts with passkey control, credential recovery, typed on-chain names and signed agent cards. The address is canonical; everything else points at it.
03 Harness
An authority-aware agent loop: the planner proposes, the mandate authorizes, the executor acts, the receipt proves. Durable runs, streamed progress, parallel read steps, schedule and message triggers, per-run bills.
04 Edge
A2A over HTTPS with application authentication, canonical identity resolution and an admission stage that no transport evidence can skip. Private MCP behind admitted runtimes; public MCP only as labelled interop.
05 Registry Kit
SA-anchored registry contracts with pluggable admission hooks, admission receipts, a lifecycle log, signed agent cards, discovery projections (A2A card, ARD, ACP registry) and a public knowledge base projected only from chain state.
06 Evidence
Verification receipts bound to intent + mandate + step + playbook digest; PROV-O graphs with a trace-context spine; append-only audit with forensics tooling; verifiable credentials for claims; anonymous credentials an organization issues to its members, with the issuer’s live-credential root anchored on neutral ground.
07 Coordination
A durable Endeavor with a shared plan, participants found through discovery at the capability level, signed contribution commitments against an exact plan revision, decisions and rules. Never confused with in-agent orchestration.
08 Ontology
An upper ontology for everything agentic — agents, credentials, custody, delegation, capabilities, situations, provenance — that a domain ontology imports and subclasses. From the two, an agent archetype bundles skills, capabilities and ontology areas; from the archetype, the A2A signed agent card and the SKILL.md packages are projected. Vault records are ontology-shaped; behaviour is generated from the model; a gate fails the build when code invents a term.
Ontology, live
An upper ontology says what every agentic system has. A domain ontology imports it and says what this domain has. An archetype bundles the skills, capabilities and ontology areas one kind of agent needs. From that, the A2A signed agent card and the SKILL.md packages are generated — never typed by hand. Meaning flows down the ladder; authority never does.
What this replaces
A system prompt that explains the domain, a table in the app that disagrees with it, an agent card typed by hand and a playbook that names things the model has never heard of.
What is checked
SHACL shapes on every class. A SKILL.md whose knowledge.requires names a class the ontology does not have fails to compile. Code that invents a term fails the build.
What is not authority
Any of it. The archetype, the card and the playbook are consulted by no verifier. The coach reads Alice's hands under a Study Grant she signed at her Home — and loses them the moment she revokes it.
09 Operations
Service keys as revocable delegates (never the identity), budget-routed model selection, live verification gates that run nightly against the real estate, `ap conform` for A2A and MCP.
How they compose
Ring 0 is packages and contracts. Products live in their own repositories and import the packages: the Home and its estate in ap-home, the single-chain shared services (naming, the public graph, registries) in ap-town, the cross-chain public ground in ap-federation, and your application in yours. Integrations with other people's protocols (ERC-8004, ANS, HCS, DNS-AID, OASF) live outside too, importing inward, never the reverse.
That is what lets you take one offering without the rest, and what keeps a vertical's vocabulary out of the primitives: the packages are generic trust building blocks; branding, verticals and deployment specifics are the application's job.
Package map and quickstartGame Night uses Identity, Authority, Harness, Edge, Registry Kit, Evidence, Coordination and Operations — in a card room.