The control plane for
autonomous agents.
Dragons gives every agent a cryptographic identity, a signed lease for every action, a hash-chained receipt anyone can replay, and a heartbeat that catches a stalled agent before you do. Four mechanisms. One trust loop.
What the control plane does.
Four questions every governed agent must answer: who is it, what may it do, what did it do, and is it still alive. Dragons closes all four with cryptographic primitives and continuous enforcement. No human babysitting.
No anonymous processes.
Every agent is a versioned, named entity. Its manifest_hash is a
SHA-256 fingerprint of the agent's code, config, and declared capabilities. Not the PR hash --
the agent hash. No two agents share an identity. No agent runs without
having been that exact version.
The manifest_hash is the cryptographic anchor: the proof that the agent that docked is the agent that was authorized. Version rollback is auditable. Every identity traces to a dock binding a tenant to an authorized scope.
A signed grant, not a handshake.
An agent runs only inside a signed lease: a time-bounded, scope-restricted authorization record. No lease, no execution. Expired lease: Dragons degrades the agent automatically. Every action traces to a lease. Every lease traces to an operator key.
Scope is explicit -- read:payments, write:ledger -- per tenant,
per TTL. Expiry is enforced, not advisory. When the TTL hits zero, the control plane
degrades the agent. No human page required.
Reconstruct an incident in minutes.
Every governed action produces a signed, hash-chained receipt linking goal to action to outcome. The WorkLedger holds the full chain. Each entry links to the prior one via hash -- tamper with one and the chain breaks downstream.
Export a compliance-ready evidence pack for any session, any agent, any time window. Any third party can replay it without private trust. The auditor replays; they do not believe you.
Stalls heal before they page you.
Every agent emits a compulsory heartbeat. Dragons tracks organism state -- running, degraded, autohealing, quarantined -- not binary alive/dead. A stalled agent degrades at 30 minutes, autoheals at 60. No human page. No 3 AM restart.
MTBOI (mean time between operator interventions, rolling 30 days) is the metric that proves the fleet runs itself. The control plane moves agents through states; the operator intervenes only when quarantine escalates.
The proof loop.
Every activation follows the same four-step loop. The output is a signed receipt any third party can verify without trusting Dragons.
Operator defines the objective. Explicit scope, recorded before execution begins.
Agent executes inside a signed lease. Every governed action appends a receipt to the WorkLedger, hash-chained to the prior entry.
Signed record of identity, authorization, evidence, and liveness state. Tamper-evident. Exportable. Compliance-ready.
Third party replays the chain: goal to action to evidence to outcome. No private trust required.
Recompute the chain root in your browser. The math is open.
Show the canonical JSON I am hashing
(verify to populate)
Composes with your stack.
Dragons governs. It does not schedule, trace, or monitor. Each tool does one job; Dragons slots into the trust layer between your agents and the systems that run them.
Temporal handles execution order, retries, and durable workflows. Dragons records which agent ran which step, under which lease, with which manifest_hash. Temporal schedules; Dragons proves who did it.
LangSmith traces LLM chains, token usage, and latency. Dragons records the agent identity and authorization context around those calls. LangSmith traces the model; Dragons proves who called it.
Datadog monitors CPU, memory, and infra health. Dragons tracks organism state: the semantic lifecycle of the agent, not a PID. Datadog monitors the box; Dragons governs the agent.
What Dragons does not do.
Scope precision is the reason Dragons is trustworthy. It closes one gap -- the trust gap -- and nothing else.
manifest_hash + signed instance_idauthorized_by
Your agents are running right now.
Can you prove what they did?
Run Dragons side-by-side with your existing fleet for 30 days. At day 30, it reports what it caught that your current watchdog missed. Numbers, not claims.