PLATE 01 / SIGNAL-BOX
LEVERFRAME
Agent infrastructure. Your fleet, on one panel — bridge the runtimes, supervise the actions, agree on the record.
PLATE 02 · FRAME / PRODUCTS
One tool surface across OpenClaw gateway agents and Hermes agents. Any MCP client — Zed, Claude Code — sees a single roster and pulls any agent by name.
Sits between your coding agent and its tools. Dangerous constructs gated before they execute, runaway loops killed by deterministic signals, every decision in a .curt record.
Three agents debate, each signs its own stance, and the result ships as a k-of-n signed receipt anyone can verify — forever.
PLATE 03 · THE INTERLOCK
BRIDGE
Runtimes don't talk. OpenClaw gateways speak HTTP chat, Hermes speaks ssh. fleet-bridge makes them one roster behind one tool surface — cross-runtime by construction.
SUPERVISE
Supervisors supervise. wranglebot makes thrashing expensive: dangerous constructs denied before execution, runaway loops killed on deterministic counts, everything recorded.
AGREE
Frameworks coordinate. Tractum agrees: per-agent signed stances, quorum-verifiable receipts you can hand to an auditor, a regulator, or a future teammate.
PLATE 04 · HOW IT FITS
YOUR AGENT (Claude Code / Codex / Zed / any MCP client)
│
▼
┌─ wranglebot ──────────────────────────────────┐
│ ast-gate → loop-breaker → scope-guard │──▶ deny / warn / .curt record
└───────────────────────────────────────────────┘
│ allowed
▼
┌─ fleet-bridge ────────────────────────────────┐
│ one roster, two runtimes: │
│ OpenClaw agents (HTTP chat/completions) │──▶ invoke by name, sessions server-side
│ Hermes agents (ssh -z) │
└───────────────────────────────────────────────┘
│ agents disagree?
▼
┌─ tractum ─────────────────────────────────────┐
│ debate → each stance signed → k-of-n receipt │──▶ verify forever, publish NIP-78
└───────────────────────────────────────────────┘