Define what humans and agents may do with deterministic policy, strict evidence requirements, and machine-verifiable outcomes.
/covenant.yml.allow, warn, deny.This matrix summarizes Covenant's canonical actions across actor kinds. Hover selected headers and action names for quick field explanations.
| Interaction | Human | Agent | Manager | Typical Controls |
|---|---|---|---|---|
issue.open | allow/warn/deny | allow/warn/deny | allow | templates, labels, attestation |
issue.comment | allow/warn/deny | allow/warn/deny | allow | thread mode control |
issue.label | allow/warn/deny | allow/warn/deny | allow | auto-label policy |
issue.solve | allow/warn/deny | allow/warn/deny | allow | evidence policy |
pull_request.open | allow/warn/deny | allow/warn/deny | allow | provenance and tests |
pull_request.update | allow/warn/deny | allow/warn/deny | allow | re-attestation |
pull_request.review.submit | allow/warn/deny | allow/warn/deny | allow | reviewer policy |
pull_request.review.approve | allow/warn/deny | allow/warn/deny | allow | human-only gates |
pull_request.merge | allow/warn/deny | allow/warn/deny | allow | branch and ruleset checks |
conversation.intervene_human_thread | allow/warn/deny | allow/warn/deny | allow | human thread protection |
conversation.intervene_agent_thread | allow/warn/deny | allow/warn/deny | allow | agent thread policy |
maintenance.cleanup | allow/warn/deny | allow/warn/deny | allow | close PR, delete branch |
routing.to_develop_bot | allow/warn/deny | allow/warn/deny | allow | reroute to develop-bot branch |
Paste covenant.yml and a canonical event JSON payload. The playground validates policy shape and simulates deterministic evaluation.
Browser playground validates structure and rule matching. Cryptographic attestation must be verified in CI/CLI.
Every Covenant-enabled repository exposes five governance badges. This section renders every possible state, stacked by category, so maintainers can compare policy posture at a glance and avoid ambiguous badge usage.
Help text below focuses on the four policy-decision badges; covenant-enabled is always enabled when Covenant is active.
agent-pr-policyShows the strictest policy outcome for agent-authored pull requests.
Practical example: a human asks an agent to open a PR; allow means it can proceed, warn means it opens with policy warnings, and deny means the PR is blocked.
provenance-policyShows whether a default provenance profile enforces evidence fields.
Practical example: an agent opens a PR; with required it must include evidence like model and provider, while none means those fields are not enforced.
attestation-requiredIndicates whether cryptographic attestation signatures are required.
Practical example: when an agent submits a PR, required or agents means it must attach a valid signed attestation payload or policy checks fail.
thread-intervention-policyShows whether intervention in human threads is restricted.
Practical example: in a human-only incident thread, controlled means an agent comment is warned or denied unless explicitly allowed.
Embed these directly from GitHub raw URLs in READMEs, docs, and dashboards. See docs/BADGES.md for copy/paste snippets.
/covenant.yml before any action.covenant.attestation.v1 payload.