Review Feedback

Review feedback is evidence about one system, not a patch queue. Determine whether the reported problem is real, find why the system permits it, and choose the lowest-cost system state before editing.

Hold the edit gate

Read-only inspection, reproduction, and tests may begin immediately. Do not edit production code until the next user-visible progress update contains a decision ledger covering every review comment. If you have already started editing, stop, inspect the diff as evidence only, and complete the ledger before continuing.

The ledger may group comments with one cause, but it must map every original comment to a group. For each group state:

• verdict: Verified, Disproved, or Evidence gap;
• reach: normal user path, reasonable failure/retry/concurrency/recovery path, attacker-controlled trust boundary, or contrived unsupported path;
• severity: P0, P1, P2, P3, or No finding;
• decisive evidence;
• root cause, violated invariant, natural owner, and the smallest single-owner end state that covers the group;
• outcome: Delete or simplify, Fix at owner, Fix locally, Defer, or Push back.

When feedback targets an existing diff or follows an earlier review round, also state its scope relation: required by the original change, regression caused by this diff, unrelated drift already in the diff, or pre-existing/adjacent.