Repository navigation
Onus v0.7.0
Phase 4 complete: risk lanes and the verifying judge (ADR 0009, onus help lanes).
onus submitbundles a change for review: the intent, Onus's report, changed paths, test runs to re-run, the token's scope, escalations, approvals and the agent setup, and nothing of the author's reasoning.onus classifyputs a change in a lane (auto-merge,judge,human,blocked). The lane comes from a policy in onus.yaml (lanes:) and hard floors no policy can lower: secrets, out-of-scope writes and unapproved weakened tests are blocked; sensitive code, rules of the game and intent mismatches go to a person. New agent setups cannot auto-merge, and a share of auto-merges is audited by a person.onus judgeverifies before it judges: it re-runs the evidence in containers, then checks intent, contracts and tests, then runs held-out checks. An optional taste reviewer can raise concerns but never approve. The verdict is approve, reject (with reasons the agent can act on) or escalate.- The action's
lanes,apply-laneandauto-mergeinputs show the lane, label the pull request, fail blocked changes and enable GitHub's auto-merge. onus outcomes record|summarytrack outcomes per agent setup and judge configuration, including the audit miss rate and the human-lane share.
Install
brew install onushq/tap/onus
curl -fsSL https://onushq.com/install.sh | shOr in a workflow: uses: onushq/onus/action@v0.7.0. Each archive is attested: gh attestation verify <archive> --repo onushq/onus.