Buyer-side acceptance

Their code ran in a sealed room. Your data stayed.

Real sample data never goes to the vendor. You lock claims, run their program on your side, and reject on a finding — not a slide deck. See a red-light run.

Tradeoff

Buyer

Wants the data kept secure. Needs a rejectable record after the contract is signed, before daily use.

Vendor

Doesn't want to overspend on later drift maintenance. Runs day to day once acceptance clears.

Why you can reject on evidence

Hardware trust chain and sealed-room data flow Chip root connects to sealed room, claim lock, then receipt. Their program enters the sealed room; sample data stays inside; only the result and receipt leave. Chip root Sealed room Claim lock Receipt

Their code ran in a sealed room. Your data stayed.

Only the result and a receipt came out.

Sealed room

“Sealed room” here means a trusted execution environment (TEE) — same class of isolation as Apple Private Cloud Compute or Azure Confidential VMs. Analogy, not a partnership. It relocates the trust boundary; it doesn't erase residual ops risk.

If you need the technical receipts / upgrade path

Cryptographic commitments bind the program, the sample set, and the result. Same inputs produce the same result hash.

AMD SEV-SNP guest attestation is an upgrade path. We have a dry-run (OUR_RUN) in Azure germanywestcentral — not a Norway colo claim, not Bulk/GM live.

Norway jurisdiction / colo is on the roadmap as an upgrade tier. This marketing page does not claim it is live.

The public demo uses local quarantine isolation today so counsel can read a rejectable miss without waiting on live TEE hardware. Evidence pack says so plainly.