Roadmap: publish your own zero-human badge from your own box

[lodar]

The zero-human badge on this README is computed by the digest and republished daily by scripts/publish-zero-human.sh. Generalize that into one command so any box can publish the same badge, datapoint and append-only history for its own company, to its own repo. Methodology stays shared: docs/zero-human.md.

[lodar]

Design settled (epic OSS-17 closed into a build): the verb is 5dive proof — proof publish [--dry-run] / proof on --repo=<url> [--at=HH] / proof off / proof status, mirroring the digest on/off pattern. Numbers come from 5dive digest --json verbatim with no edit path, append-only history on your own repo's status branch, visible-staleness failure mode — the same invariants as this repo's badge. scripts/publish-zero-human.sh stays as a back-compat shim. Build is in progress; first publish will print the copy-paste README badge snippet for your own repo.

[lodar]

Shipped in v0.10. The generalized verb is live as 5dive proof: proof publish [--dry-run], proof on --repo=<url> [--branch=status] [--at=<0-23>], proof off, proof status, plus a proof tick cron driver. Numbers come verbatim from 5dive digest --json with no edit path, published to your own repo's status branch as badge.json + zero-human.json + an append-only history.jsonl, with the same visible-staleness failure mode as this repo. Methodology stays shared in docs/zero-human.md. So any box can now publish the same badge, datapoint and history for its own company.