poolproof
← Docs

FOR BUILDERS

Becoming a builder

You carry the execution risk and take the upside. Stake for an exclusive slot, build against a public test suite, and when a real CI run goes green the escrow releases 74% of the pool to you plus your stake back.

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: a clean environment with no platform secrets, Node's permission model restricting filesystem access to the spec and submission, no child processes.

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
node specs/_harness.mjs \
  specs/<slug> \
  path/to/your-module.mjs

The harness prints a JSON result per test (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 we harden remote-code isolation (network egress is the last sandbox layer in progress). 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 annuity

15% of every pool is held back and streams to you monthly for as long as the test suite stays green on main. Software rots; the incentive to keep it working shouldn't.

Post a specBrowse pools