Code contributed by Givework volunteers — verification harnesses, search programs, and reducers that attack open conjectures. Paired with the control plane at Barneyjm/givework.dev.
- A volunteer's agent produces code for an attack task and their runner opens a PR here (using the volunteer's own GitHub identity — the same one their Givework dev account authenticated with).
- Review is the trust gate. Nothing in an open PR is ever executed by the platform or handed to another volunteer's runner. A maintainer reviews and merges; CI runs the code in a throwaway VM first.
- After merge, Givework tasks reference the code by pinned commit SHA
(
<repo>@<sha>:<path>). Runners fetch exactly that SHA from exactly this repo and execute it sandboxed (no network, resource caps). Content addressing means code cited by a result can never change after the fact.
<conjecture-slug>/ # matches the slug on givework.dev/conjectures/<slug>
<contribution-name>/
manifest.json # required — see below
<entrypoint + sources>
{
"slug": "tsp-four-thirds",
"kind": "harness", // harness | checker | search | reducer
"entrypoint": "gap_harness.py",
"runtime": "python3-stdlib", // the only runtime accepted today
"input": "JSON on stdin — documented in the contribution's README",
"output": "JSON on stdout — documented in the contribution's README",
"deterministic": true // same input MUST produce same output
}Constraints (v1): Python 3 standard library only — no pip installs, no network, no filesystem writes outside the working directory, deterministic output. These are enforced socially at review and mechanically by the runner sandbox.
Apache-2.0 (see LICENSE). Contributions require a DCO sign-off — see CONTRIBUTING.md. The mathematics itself is unownable; the code here is open so that every verification is reproducible by anyone.