signetKeep the source of authority.
Your vault holds the root keys. Your agent operates within the access you grant. Delegation begins with you.
The personal authority layer
Your agent.
Your authority.
An agent can act on your behalf.
The authority should never stop being yours.
Signet combines a private vault, selective proofs, and explicit policy. Build authority into how your agent works.
OPEN SOURCE. LOCALLY CONTROLLED. YOURS BY DESIGN.
Authority belongs to you.DELEGATED WITH INTENT. BOUNDED BY DESIGN.
PERSONAL SOVEREIGN AGENT STACKSIGNET
RUST / NINE CRATESCRYPTOGRAPHIC VAULTMCP INTEGRATIONMIT / APACHE 2.0
01 / The principle
Autonomy requires
boundaries.
As agents gain the ability to act, permission can no longer be implied. It needs an owner, a scope, and a way to say no. Signet starts with the person the agent represents.
Disclose only what is needed.
A service may need to verify a claim. That does not entitle it to the complete record behind the claim.
Make permission explicit.
Define the context. Evaluate the request. Record the decision. Sensitive access should have a boundary you can inspect.
A very old idea. A necessary new layer.
The seal travels.
The authority stays.
A signet let a trusted representative act in someone's name. The same distinction matters now: your agent carries a specific mandate. You remain the source of its authority.
02 / The architecture
One root of trust.
Clear lines of access.
Signet brings a local vault, a policy engine, and a proof pipeline into one Rust workspace. The trust model makes each participant's role explicit.
Your vault.
Encrypted storage and a key hierarchy separate what the agent can access from what requires your authorization.
Your agent.
An MCP interface connects the agent to the policy and proof layers. Requests are evaluated within that boundary.
The service.
Verification binds a capability to its expected issuer, domain, purpose, and validity window.
Explore the three tiers
Over 21. That is all.
age_over_21: trueThe request needs an age threshold. A proof can disclose the claim while keeping the date of birth private.
A model of the trust boundaries. No real data, proof generation, or authorization is used in this illustration.
Capability issuance requires a trusted issuer. One-time generic capabilities remain disabled pending a consumption ledger. Read the implementation boundary ↗
03 / For builders
Put authority
in the architecture.
Start with the vault and its MCP interface. For tool-call enforcement in your coding agent, the companion Signet Eval has its own installation and policy.
The personal authority stack.
Explore encrypted storage, tiered access, policy evaluation, and capability verification. Build from the repository's locked dependencies.
cargo install --locked --git https://github.com/jmcentire/signet.git signetA boundary for agent actions.
Evaluate agent tool calls against explicit rules. The standalone policy engine is a separate project within the Signet family.
cargo install signet-evalSignet is under active development. Review the security model and source before integrating sensitive workloads. Release availability is not a claim of production custody readiness.
The next layer of the agent stack