Bring the customer contract
Name the result the customer should get. Keep those checks outside the candidate's execution environment.
Repair a broken business rule. Keep the customer's original contract. Then finish the order in a real browser.
Browser sandbox included. No wallet needed to test a candidate.
Name the result the customer should get. Keep those checks outside the candidate's execution environment.
Paste your own candidate or connect the local service to buy fresh repair code through Telegraph.
Run the original cases in the sandbox. An accepted checkout candidate can complete the demo order.
The included checkout deliberately contains that defect. Its repair must preserve express shipping, pickup and invalid-order handling too.
See the acceptance boundary ↗The local agent asks Telegraph for repair code only after the current implementation fails the contract. Every authorization has a quote and a testnet spending ceiling.
Connect the local agent ↗Test a candidate against the customer's unchanged acceptance contract.
The example candidate is a supplied correction, not an autonomous purchase. All checks run for real.
The candidate only receives input values. It cannot edit this contract or its expected results.
A real browser flow using the selected implementation. No goods are sold and no money moves.
Run evidence binds the source, candidate and original contract. Paid runs add the request, signal commitment and settlement evidence.
The candidate returned the expected JSON for every supplied case without changing the input. The included checkout also has varied boundary and delivery cases. This is scoped evidence, not proof that all possible inputs or all pages work.
Expected results, acceptance decisions, payments and evidence files remain in the host. QuickJS receives only the candidate source and one input at a time. Each case has a fresh context.
The included merchant and its broken shipping rule are controlled demo fixtures. Manual checking runs the real sandbox. An example correction is not presented as purchased code. A paid run is verified only after its actual request, receipt, signal commitment and on-chain transfer pass the checks.
Repository-wide edits, third-party checkout systems, private customer data and production purchases are outside this first release. A local repair is accepted only for the contract supplied by the operator.
Node 22 or newer. The browser-only workspace needs no wallet. The local service keeps the signer on your machine.
npm ci npm run build npm start # Open http://127.0.0.1:4318
Set HOUSE_WALLET_PRIVATE_KEY in the environment at launch. Use an Ethereum Sepolia wallet with test USDC. The service accepts only the configured testnet asset and refuses quotes over 0.02 test USDC. Daily authorizations stop at 0.05.
Open the repair workspace, load a failing contract and choose Buy a repair locally. Inspect and approve the exact quote. There is no retry after a signed request fails.
./verify.sh
The gate runs strict type checking, sandbox and protocol tests, a production browser walkthrough and the dependency audit.
A complete JavaScript function, one input per case and plain JSON outputs. No imports, host functions or network access are provided.
{
"version": 1,
"name": "A customer-owned outcome",
"entrypoint": "calculate",
"specification": "Return the input amount plus one.",
"cases": [
{"id": "first", "input": 4, "expected": 5}
]
}Source is capped at 16 KB, contracts at 32 KB and cases at 64. Each input is passed into a new isolated runtime. You own the specification and expected results.
QuickJS compiled to WebAssembly runs the candidate with no host callbacks. It has an 8 MB heap, a bounded stack and an interruption deadline. A separate worker adds a hard deadline. In the local service the worker receives an empty environment.
Only the trusted local payment process sees the signer. No key is copied into a candidate, report, browser or repository. The service binds to loopback and rejects unexpected Host and Origin headers.
Quotes are single-use. Economic terms are checked again before signing. Authorizations are reserved before payment and remain counted if the request later fails. Receipt hashes identify calls; batched transaction hashes do not identify a call by themselves.
The host and contract author are trusted. QuickJS is a dependency, not a formal security proof. The demo order is not a production merchant transaction. Testnet use and independent customer adoption are reported separately.