Find a counterparty, agree the terms, and authorize the release in one place -- the surface settles the transaction only against a two-party verified number. The deal, the verification, and the receipt all live on one ledger-anchored graph, so nobody re-keys it and nobody can dispute it.
Why it matters
Most marketplaces stop at the handshake -- they match buyers and sellers and leave the money to a separate system no one can reconcile. This surface carries the deal through settlement on the same graph. You discover counterparties by role, agree terms, and authorize the release in one place.
Three real controls stand behind every settlement. The marketplace trades Cascade recipes -- configuration snapshots that install below your node with FLOOR and INTERSECT safety, and never include security-sensitive domains. The money-firewall imports no payment client, so no code path can move funds on its own, and any wired rail can reach only an allowlisted destination.
The work, split
The agent works the calm 80 percent. It surfaces matching recipes and counterparties by role across the shared graph, assembles the transaction, runs the payment-blocking checklist, and recomputes separation-of-duties and ledger accreditation straight from the record -- never from a flag. What reaches you is a settlement already proven or already halted.
You make the one call that moves the number: you authorize the release. Because the gate requires a verifier distinct from every submitter, your approval is the second signature it demands -- not a rubber stamp. The instant you release, the verdict is anchored to the ledger as a receipt, with the amount, the parties, and the proof attached.
How it works
Bring a deal you actually run. We will take it from counterparty match to a ledger-anchored receipt -- on the same graph your seat and your community already use.