Verify.

Without verification.
Trust is just a claim.

The same question gets answered again. The same decision gets revisited. The same scope gets re-explained.

You waste time re-deciding work that was already accepted. You need to know requirements were actually met. Not just claimed.

With verification.
Trust becomes tangible.

At acceptance, required checks run. The verifier is pinned from a trusted reference, so execution cannot modify the rules it's judged by. No manual review. No "trust me."

The receipt binds contract, verification output, and evidence hashes. It records what was accepted and when. It travels with the work across boundaries, handoffs, and audits.

The Ledger is optional. When work crosses boundaries, either side can request attestation. The receipt is the evidence. The Ledger only stamps it.

Local acceptance is authoritative.

Peer to peer.
No intermediary.

Imagine using Claude Code to buy IP from someone else. An algorithm. A video. A celebrity likeness. Anything with a work contract.

You define the work requirements and validation. They accept the contract and do the work. Verification runs. The receipt proves delivery. No platform in the middle. No intermediary taking a cut.

The optional ledger acts as a neutral third party. A tiebreaker if there's a dispute. It doesn't route the work. It doesn't decide acceptance. It just timestamps the receipt.

This doesn't add new protocols. Just definition, verification, and a signed receipt.

Proof you can verify.

Download a proof pack and verify offline. If the artifact is changed, verification fails closed.

# download and verify
$ unzip -q motus-proof-pack-hello.zip -d proof
$ cd proof && ./verify.sh
PASS  receipt verified

# tamper -> FAIL
$ echo "tampered" >> artifact/hello.html
$ ./verify.sh
FAIL  artifact hash mismatch