LEVERFRAME

PLATE 01 / SIGNAL-BOX

LEVERFRAME

Agent infrastructure. Your fleet, on one panel — bridge the runtimes, supervise the actions, agree on the record.

The Leverframe lever throw
3PRODUCTS
2RUNTIMES BRIDGED
6MCP TOOLS
5GUARDRAILS
K-OF-NSIGNED RECEIPTS

PLATE 02 · FRAME / PRODUCTS

PLATE 03 · THE INTERLOCK

01

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.

02

SUPERVISE

Supervisors supervise. wranglebot makes thrashing expensive: dangerous constructs denied before execution, runaway loops killed on deterministic counts, everything recorded.

03

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
  └───────────────────────────────────────────────┘
IN DAILY PRODUCTION USE ON A MULTI-AGENT FLEET ◆ DOCS BUILT FROM SOURCE — EVERY PAGE CITES ITS FILES ◆ LICENSES PER PRODUCT — MIT / BUSL-1.1