01 · The stack you would buy
An agentic solution takes 29 products. Or one substrate.
Sign-in. Wallets. Accounts and custody. Scoped permissions. Private data. Credentials. An agent loop. Durable workflows. Tools. Agent-to-agent calls. Payments. Admission. Names. Discovery. Evidence. Each is a product you select, contract for, integrate — and then reconcile with the others, because each brings its own idea of who a user is, what a permission is, and what a log line means. We built it that way first. Below is the wall of products it took, band by band, with the seam each band drags in — and beside it the same needs as slots in one model.
Stitched — what it took the first time
On the substrate — now
The nightmare was never any one product. It was the thirty seams between them, every one of which was where a person became a token, the token became a row, and the row became a log line nobody could trace back to a decision.
Product by product — what you would buy, what you would buy instead, and the packages that cover it here
Every one of the 77 packages appears below exactly once, against the product it stands in for. Not because each row is impossible elsewhere — because here every row shares one identity, one delegation model and one evidence trail, and the seams between rows are where stitched stacks leak authority.
01Sign-in and identity
seam · identity model #1 — a user id in a vendor’s directory02Accounts, keys and custody
seam · identity model #2 — a wallet address, joined to the user id by a table you write03Permissions and delegation
seam · permission shape #1 — roles and policies in a database; shape #2 — session keys on chain; nothing joins them04Private data and credentials
seam · the third copy of every identity — as a row key, a DID and a credential subject05Agent runtime and protocols
seam · authority as application code — a callback the framework calls if the code remembers to06Edge, naming and discovery
seam · reachability mistaken for authority — an API key at the gateway, a row in a registry07Evidence, vocabulary and tooling
seam · evidence format #1 spans · #2 log lines · #3 attestations — joined by ids you inventAnd the 40 contracts you would otherwise write, fork or audit — already written, under audit, deployed as one set
Account
6ERC-4337 · ERC-7579 modular core · ERC-1271 / 6492 · P-256 passkeys
Delegation
9ERC-7710 manager + caveat enforcers; the intent digest is ours
Naming
5.agent root · ten typed subregistries (.me .org .team .svc .workspace .treasury .registry .church .circle .household)
Registry kit · profile · relationships
8What registries are built from; SA-anchored facets
Ontology on chain
3Terms, shapes and typed attributes anchored for public facts
Commerce · evidence · governance
5Receipts and agreements on chain; governance of the deployment itself
Libraries
4Ported patterns, no runtime dependency
Solidity 0.8.28 · ERC-4337 · ERC-7579 · ERC-7710 · ERC-1271 / 6492 · EIP-712 · P-256 / WebAuthn. Ported patterns, no runtime dependency on any third-party multisig or account kit. Deployed to faithchain with the ten typed name subregistries; deployable to any EVM.
The bill of materials, need by need — what you would assemble, what you would configure, where it bites, and what covers it hereshow
- — an identity vendor (Auth0 · Okta · Clerk)
- — a WebAuthn library
- — an embedded-wallet SDK (Privy · Dynamic · Web3Auth)
One Smart Agent per person, organization and service. Passkeys and wallets are rotating credentials on it; the address never changes.
- — a multisig (Safe)
- — a guardian / social-recovery product
- — a cloud KMS
Custody is an ERC-7579 module on the account: thresholds, guardians, recovery, approvals — governed on chain, one policy.
- — a policy engine (OPA · Cerbos · Permit.io)
- — a session-key or delegation toolkit (ZeroDev · MetaMask DTK)
- — your own roles table
One grant mechanism: an ERC-7710 delegation with caveats that are enforcer code, verified at redemption, revoked in one transaction.
- — an agent framework (LangGraph · MAF · ADK)
- — a tracing product (LangSmith · Langfuse)
- — a memory store
- — a model gateway
Planner proposes, mandate authorizes, executor acts, receipt proves — the loop is a Ring-0 package; every step is verified outside the model.
- — an MCP server framework
- — an OAuth authorization server for MCP
- — a per-tool secrets scheme
MCP is a private capability interface behind an admitted runtime; OAuth is the envelope; the on-chain grant is the authority; the service key is a revocable delegate.
- — an A2A SDK
- — a message bus
- — an API gateway
- — mTLS / SPIFFE tooling
- — an agent-card you type
A2A over HTTPS with admission always required; mTLS optional transport evidence; agent cards projected from the profile and signed; the edge admits, it does not orchestrate.
- — a payments processor (Stripe · Circle)
- — a paymaster / bundler (Pimlico · Alchemy)
- — a spend-control product
- — a reconciliation job
A treasury is a Service Agent. A payment is a delegation with a PaymentEnforcer caveat; the paymaster sponsors gas; the receipt is anchored.
- — a Slack / Teams approvals bot
- — a workflow tool (Jira · ServiceNow)
- — a signing UI you build
The approval is a signature: the confirmation IS the mandate, bound to the digest of the exact intent, verified at redemption.
- — OpenTelemetry
- — a SIEM (Datadog · Splunk)
- — an LLM-tracing product
- — an attestation scheme (EAS)
One PROV-O graph: a span IS an activity; every protected step leaves a receipt the owner carries; a trace id is correlation, never trust.
- — a database
- — a field-encryption library
- — a KMS
- — a consent-management platform
Vaults are the record: encrypted envelopes with per-record scope, released only under a delegation the owner signed; the KB holds only what the chain already says.
- — an org / team model in your DB
- — a project tool (Linear · Jira)
- — a workflow engine (Temporal)
Organizations are Smart Agents; relationships and roles are on-chain records and vault situations; coordination plans are signed and adopted by decision.
- — ENS or DNS
- — an internal directory
- — a search index
- — an ERC-8004 registry
- — sync jobs between them
Typed names on chain (`.me .org .svc .treasury`); a registry kit with pluggable membership; discovery projected only from chain state; resolution grants that are never authority.
- — — nothing. It lives in prompts, in tables, and in the heads of two engineers.
One ontology, bound by IRI, checked at build. Vault records, Ask vocabulary, agent cards and playbooks are projections of it.
- — an RPC provider
- — a block indexer
- — a secrets manager
- — CI you write for nightly checks
Typed chain reads with no log scans on hot paths; service keys as revocable delegates; live gates run nightly against the real estate; `ap doctor` and `ap conform`.