The earlier prototype, on film

One delivery. A fail, then a pass.

A seller's CRM build was tested in a sealed room against three clauses both sides locked first. Version 1.3 failed one clause; version 1.4 passed all three. Each side kept its data and code to itself.

62 s · both runs are real · recorded 2 October 2026, before the room moved to AWS

1 · Watch62 seconds. Works with the sound off.
2 · ReadA fail on clause C2, then a pass on the fix.
3 · Check, if you likeVerify each signature in this page, in your browser.

The two receipts it made.

aarloven receiptfail

r-62d6b6 · build v1.3 · 2 oct 2026, 12:26 utc

c1a person without permission cannot turn a lead into a customeryes
c2when the same customer already exists, conversion stopsnoif it fails → hold milestone 2. 10-day fix window, then retest.
c3after conversion, the lead is marked convertedyes

wall: network blocked · writes blocked · reads blocked
inputs: build 8ddd…e634 · tests 9b76…0109 · data 6dd5…c427
lock: 63f7…6e04, the same clauses for both runs
workspace: deleted after the run · proof: none yet
chain: previous receipt 08af…224f
signed: ed25519 · key 6967c16b56f94b95

next: clause c2 names the action. milestone 2 is held, the seller gets a 10-day fix window, then the same locked clauses run again.

download the json

aarloven receiptpass

r-3f7f34 · build v1.4 · 2 oct 2026, 12:26 utc

c1a person without permission cannot turn a lead into a customeryes
c2when the same customer already exists, conversion stopsyes
c3after conversion, the lead is marked convertedyes

wall: network blocked · writes blocked · reads blocked
inputs: build f83c…7d59 · tests 9b76…0109 · data 6dd5…c427
lock: 63f7…6e04, the same clauses for both runs
workspace: deleted after the run · proof: none yet
chain: chained to the fail receipt r-62d6b6, so the failed run stays on record
signed: ed25519 · key 6967c16b56f94b95

next: the buyer decides whether to sign and accept.

download the json

A receipt holds fingerprints of the build, the tests, the data, the locked clauses, each clause's output and the room's own code. Both receipts in full.

Honest about the boundaries.

	These two receipts	The room now
Who runs it	We run it for you (operator-run)	We run it for you; a self-serve sealed API is Next
Where	Our own machine	AWS Stockholm (eu-north-1). Still AWS's cloud.
Isolation	macOS sandbox: network off, writes only in the workspace	AWS Nitro Enclave: diskless, login-free, one channel to its host
Trust root	Ed25519-signed, hash-chained receipts; room code hash self-reported	Enclave measurement (PCR0) + KMS key policy: the key opens only for that measurement; an unlock attempt by our own admin role was refused (checked), though admins can still change the policy. Every receipt signed inside the enclave and vouched for by AWS's hardware, checked offline with our verifier
Deletion	Workspace deleted by our code; unverified	Diskless; temporary files deleted per request; unverified
Sample	EspoCRM lead → customer, synthetic leads	The published sample case; your delivery and test rows in a pilot