Concepts

Seams is key, credential, and policy infrastructure for digital authority. It helps applications prove who is acting, bind what they approved to a typed intent, enforce policy before execution, and preserve an audit trail afterward.

Prove who is acting.
Prove what they approved.
Enforce what they can do.

Wallet signing is the first execution surface. The same model extends to payment rails, merchant APIs, marketplace APIs, agent tools, and delegated device actions.

For wallet teams, Seams provides self-hostable threshold embedded wallets that deploy to Cloudflare.

System Layers

Layer	Role
Proof layer	Passkeys, Email OTP, VoiceID, device proof, org proof, wallet proof, and configured external credentials.
Policy and mandate layer	Signed mandates, typed intent digests, policy epochs, budgets, expiry, revocation, and audit state.
Key infrastructure	Holder shares, server shares, Router A/B, SigningWorker, export, recovery, delegation, and rotation.
Enforcement gateway	Allows, denies, escalates, or requires human approval before money, authority, inventory, or API state moves.
Execution adapters	Wallet signatures, payments, merchant APIs, marketplaces, agent tools, and future device actions.

Reading Order

1. Architecture for the source-of-truth component map.
2. Wallet Infrastructure Comparison for deployment and cost tradeoffs.
3. Policy for mandates, proofs, and authorization.
4. Custody for who can hold or open key material.
5. Threshold Signing for Router A/B, Streaming Yao, and signing shares.
6. Sessions for signing lanes and bounded runtime authority.
7. Auth Methods for passkeys, Email OTP, and VoiceID.
8. Delegation for linked devices, agents, and rotation.
9. Advanced for protocol, ceremony, and deployment details.

Short Version

Give agents permission to act without giving them unlimited authority.

Define what an agent may do. Bind it to signed intent. Enforce it before money, inventory, or authority moves.