Definition Of Done

A maintainer-binary change is done when the command contract, governed input, governed output, and proof all describe the same repository-maintenance rule. The binary can enforce reviewable mechanics; it cannot replace human judgment or become a product API.

Completion Gate

changed surface	done means	proof to start from
audit-allowlist	advisory exceptions remain explicit, attributable, linked, and time-bounded	command test plus audit policy
deny-policy-deviations	local cargo-deny deviations still name owner, reason, review link, and expiry	command test plus governance file guide
audit-ignore-args	generated ignore flags come only from the reviewed allowlist	command behavior plus workflow guide
bench-compare	benchmark output, normalized snapshot, baseline comparison, and strict-mode behavior remain documented	benchmark guide and output proof
command inventory	public command names and inputs match the binary and docs	command guide and guardrail tests

Proof Flow

flowchart TD
    change[maintainer binary change] --> command[documented command]
    command --> input[governed input]
    command --> output[governed output]
    input --> proof[test or policy validation]
    output --> proof
    proof --> done[reader can see the same rule in docs, code, and result]

Reader Questions Before Commit

• Which documented command changed?
• Which governed input file or output path changed?
• Is the command still maintainer-only?
• Does the proof check the documented rule rather than only exercising code?
• If reusable behavior is needed, which product or policy crate should own it?

Proof Route

1. Read the maintainer boundary guide.
2. Read the command guide, workflow guide, and output guide.
3. Inspect command implementation.
4. Run the narrow check named in the maintainer test guide.

Do not call a maintainer workflow done because it is convenient locally. It is done only when the repository rule remains explicit, reviewable, and enforced by the binary contract.