┌──────────────────────────────────────────────────────────────────────────────────┐
│  K L A U Z  ·  H O W   I T   W O R K S  ────────────  four moves · one dossier   │
│  obsidian void  ·  bone serif  ·  holographic chrome  ──────  truss-node-01     │
└──────────────────────────────────────────────────────────────────────────────────┘

▸ how it works · four moves · one dossier

From draft to signed, on-chain, in four moves.

The pipeline is short because every step is load-bearing. No magic step. No black-box step. No "AI does it" step.

Walk through itFeatures detail

// pipeline · v1.0

  1. 01

    Open the counterparty's draft

    Paste a counterparty MSA, drop a PDF, or start from a Klauz template. The workbench parses it into clauses and runs each against the EDGAR corpus for market-average comps.

  2. 02

    Redline with citations

    Every redline carries ≥3 EDGAR citations. The diff is deterministic — the same input produces the same output. Surface a citation we can't resolve, and the request fails closed.

  3. 03

    Sign the dossier, not the PDF

    Counterparties co-sign the same artifact. The SHA-256 of the dossier is anchored on-chain. The receipt is the transaction hash — the PDF is just one of its renderings.

  4. 04

    Release milestones in stablecoin

    Escrow stablecoin against named milestones. Multi-sig release. The dashboard mirrors the chain — it does not author it.