Define the boundary.
Scope actions by tenant, identity, resource and executor. Apply expiration and optional currency and amount limits.
Explore the request flow →
v0.5.3 Open-source beta
Give agents
Give agents
autonomy.
Keep control.
A security gate between AI agents and real-world actions. Set the policy, authorize each request, and verify what happened.
pip install tempus-ddbTHE ACTION BOUNDARY01 — 04
github.create_issueIllustrative flow
- 01AGENTSIGNED
“Create an issue.”
Signs the exact intent.
- 02TEMPUS GATEALLOWED
Policy decides.
Issues a short-lived, single-use permit.
- 03ISOLATED EXECUTORUSED ONCE
One permitted action.
Holds the credential. Performs the effect.
- 04VERIFIABLE RECEIPTLINKED
The evidence stays linked.
Intent, permit and signed outcome.
The agent requests. The policy authorizes. The executor acts.
Built around verifiable evidenceEd25519 signaturesSingle-use permitsIsolated credentials
01 / The protocol
Every action has
a chain of evidence.
Connect an agent through MCP or Python. Tempus evaluates signed policy; an executor enforces the permit before calling an external service.
Keep credentials separate.
Executors verify permit binding and consumption state. Protect their credentials and signing keys from the requesting agent.
Set up an executor →Inspect the outcome.
Cryptographic receipts link the request, authorization and result. Alter a bound field and verification detects the mismatch.
Test tamper detection →02 / Integrations
Put a gate in front
of the tools you use.
Packaged adapters share one authorization protocol. Start with a supported action, then build your own executor at the transport boundary.
PACKAGED ADAPTER
GitHub
Create issues and pull requests with allowlisted arguments and an isolated token.
DevOps blueprint ↗ PACKAGED ADAPTERHTTP & webhooks
Mediate HTTPS POST and PUT requests while keeping authorization headers separate.
Integration guide → PACKAGED ADAPTERSlack
Send channel messages and alerts through a credential-isolated executor.
Integration guide → REFERENCE ADAPTERPayments
Enforce a money contract. Includes a mock transport; connect your own payment provider.
Payments blueprint ↗04 / Project status
Open source.
Explicit boundaries.
Tempus DDB is in beta. Evaluate the implementation and deployment assumptions for your workload.
Read the roadmap ↗Implemented locally
Signed policies, mediated executors, identity rotation and revocation, event streams, and signed checkpoints.
Enforce credential isolation
The agent must not be able to read executor secrets. Rollback detection requires independently retained checkpoints.
Distributed operations
Multi-container gate deployment is on the roadmap. Current single-instance protections do not establish distributed replay safety.
Questions, answered
Before you integrate.
Is this a human approval workflow?
No. Operators provision identities and policy; agents, the gate and executors handle the runtime flow. Humans can inspect the evidence without approving every action.
Does connecting MCP protect every tool automatically?
No. Supported actions must pass through a mediated executor that exclusively holds the downstream credential. An agent with direct access to that credential can bypass the boundary.
What does a verified trace prove?
That the checked evidence is authentic and linked. It does not independently prove the executor truthfully reported an external event. A failed action can still produce a verified trace.
Is the playground connected to a real account?
No. It uses a synthetic fixture with embedded sample public keys. It checks hashes, signatures and record links locally; it cannot create GitHub issues, send messages or move funds.
Build with Tempus
Start with one bounded action.
Run the local demo. Understand the boundary. Connect your executor.