Revision Policy

This is the source-of-truth behavior for revision approval, stale handling, and author reputation impact.

Open revision queue Confidence model User types and badges About The Community Cookbook

1. Revision Model

Every submitted revision is based on a specific base revision. A proposal only becomes live when it is finalized as approved and set as the recipe's current revision.

2. Voting and Finalization

Votes are weighted by reviewer reputation. A revision can finalize only after at least 3 unique reviewers vote. Approval requires confidence at or above 0.65; rejection requires confidence at or below -0.65.

Finalization also requires at least 1 trusted author reviewer vote. Trusted author status is earned by reputation threshold or assigned by an admin.

To reduce brigade risk, finalization also requires at least 2 established reviewer votes. Established reviewers are trusted authors, moderators/admins, or accounts older than 7 days.

Authors cannot vote on their own revisions. Reject votes require rationale and the rationale is recorded in discussion for auditability.

3. Precedence and Simultaneous Revisions

If multiple revisions are open on the same recipe, precedence is determined by finalization against the current base. If a revision reaches finalize-time after the base has already moved, it is superseded and does not become the live version.

4. Stale, Renew, and Withdraw

A pending revision becomes stale when its base no longer matches the recipe's current revision. Authors can attempt auto-renew from stale state. Auto-renew succeeds only when changed fields can merge cleanly.

If conflicts exist, the UI shows an explicit conflict report and blocks auto-renew until the author submits a fresh revision. Authors can withdraw stale revisions without reputation penalty.

5. Reputation Impact Rules

Reputation is quality-weighted and not a pure volume score. It considers accepted outcomes, acceptance rate, peer-trust signals, and contribution history.

No-penalty stale self-withdrawals are excluded from penalized rejection accounting. Moderation events are logged separately and do not silently alter revision outcomes.