Verification is evidence, not marketing

CI runs the public job protocol, not just import checks:

Area	Executed contract	Not implied
Broker	Authentication, permissions, concurrent claims, lease expiry/retry/cancel, replay rejection, persistence, proof verification	HA, tenant isolation, security certification
Desktop	Actual CPU worker through HTTP-shaped API; inference contract for vLLM/SGLang	Live GPU performance
Browser	Real Chromium Web Worker, CPU task, stop/consent controls at desktop and mobile widths	Physical Android/iPhone validation
Slurm	Approved-profile dispatch and cancellation against deterministic CLI fixtures	A real cluster or driver installation
Package	Wheel build/install and static app inclusion	Native app distribution
Docs	Strict MkDocs build, navigation and Pages artifact	A live site before Pages is enabled

The browser-Gemma adapter requires separate WebGPU/model-download validation. No device utilization, training benchmark or competitor comparison is invented.

Run checks

pip install -e '.[dev,docs,browser]'
ruff check open_compute tests
ruff format --check open_compute tests
pytest -q tests/test_broker.py tests/test_slurm.py
playwright install chromium
pytest -q tests/test_browser.py
mkdocs build --strict

The public documentation site does not run a broker or store task data or credentials. To host a community, follow setup and use your own reachable HTTPS broker address for OPEN_COMPUTE_PUBLIC_URL.