Becoming a builder

How a build slot works

• A project with a full pool opens a build slot. You stake 5% of the pool for a 7-day exclusive slot — no wasteful racing, one builder at a time.
• Go green before the deadline → stake returned + 74% of the pool. Time out → part of the stake burns and the slot passes to the next builder in queue.
• Your compute is your cost. That's the point: execution risk sits with you.

What green means

Green is not an AI reading your diff. The verification runner executes every acceptance test in an isolated child process — the public suite you can see plus hidden holdout tests that catch code written only to the visible tests. All tests pass, or nothing moves.

The runner is hardened: candidate code runs in a separate realm with no imports, process, host objects, filesystem, or network global. The parent accepts only a signed complete manifest.

Run the suite locally before you stake

Every spec's public suite is downloadable from its project page. The harness is open — clone the repo and run any spec against a candidate module:

git clone https://github.com/Barac9492/poolproof
cd poolproof

# run the public suite for a spec against your module
PP_RESULT_SECRET=0123456789abcdef0123456789abcdef \
  node --experimental-vm-modules specs/_harness.mjs \
  specs/<slug> path/to/your-module.mjs

The harness emits a signed result envelope (pass/fail + detail). Iterate until the public suite is all-green locally, then submit — knowing the holdouts still have to pass on the server.

Anatomy of a submission

A submission is a JS module that exports whatever the spec's contract card promises (e.g. renderAlerts(markdown), parseDuration(input)). The suite imports it and asserts behavior. Nothing else — no framework, no boilerplate.

Submitting a build

During the public beta, builds are submitted through us while an external OS sandbox is added as defense in depth. To claim a slot and coordinate a submission, stake on an open project and reach out via GitHub Discussions. Self-serve git-connected submission is the next milestone — track it there.

The maintenance reserve

15% of every pool is moved into a platform-managed maintenance reserve when escrow releases. Monthly streaming is not active in the public beta; any future maintenance program will be documented before it can move reserve credits.