Review policy

A repository can declare its review ground once, in a committed .wuming.yml at the repo root, so reviewers start from settled decisions instead of rediscovering them every wave. Declared ground is soft context: the agents are told what the maintainers have decided and why, and asked not to re-raise it unless a changed hunk genuinely makes the decision unsafe — in which case they must say why. It is never mechanical suppression; findings are never dropped before the agents see them.

Example

context: >
  This project prefers explicit, readable code over abstraction;
  debug logging in scripts is a documented feature.

rules:
  - paths: [".forgejo/workflows/*.yml"]
    note: >
      Action pinning to release tags is a deliberate trade-off here;
      don't raise it.
  - paths: ["scripts/**"]
    note: >
      Debug logging in scripts is intentional and documented in the
      README.

• context — free prose every agent sees, regardless of which files it reviews.
• rules[] — each carries paths (a list of glob patterns, matched fnmatch-style) and note (free prose). A rule reaches only the agents whose routed files match at least one of its globs.

The file is read from the repository's default branch — never from the pull request under review, so the PR author cannot shape the context of their own review. Policy changes take effect when they land on the default branch, and you review them like any other commit.

How it relates to the settled-decisions ledger

They stack, and neither depends on the other:

• The ledger records decisions you make in PR threads (wuming: declined — … replies). Exact repeats of a settled finding are dropped mechanically; near-identical equivalents are suppressed through prompt context. See settled decisions.
• The policy file is ground you declare up front, without waiting for a finding to be raised first.

Both feed the same prompt discipline: agents may raise a settled thing again only when the code genuinely changed the picture, and must say why.

Writing one

Authoring is intentionally low-ceremony: the file is a few prose notes behind path globs. On repos maintained with an agent account, a natural workflow is to have the agent draft the policy from the repository's settled threads and ledger, and review the diff yourself before committing it.

Failure behaviour

Everything is fail-open: a repository without .wuming.yml reviews exactly as before; a malformed file is logged with a warning and the review proceeds without the policy; a rule missing its note is skipped while its siblings survive. A broken policy can never break a review.