External Feedback Triage

Turn feedback into an evidence-backed disposition and complete the warranted work. A correct observation does not automatically justify the proposed remedy; a poor remedy does not invalidate the underlying defect.

Triage and act

1. Separate the claims: identify the observed behavior, inferred cause/impact, and proposed change. Split mixed feedback into independently checkable items; consolidate duplicates without counting them as corroboration.
2. Locate the current context: inspect the affected code or artifact, contract, version, configuration and existing decisions. Check nearby dependencies when they matter; a valid finding need not sit on a changed line.
3. Test the claim: use the smallest meaningful inspection, reproduction or test. Assess impact and confidence separately; distinguish defects, preferences and optional improvements. A severity label or authoritative tone is not evidence. If direct verification is unavailable, preserve that uncertainty.
4. Choose the disposition: use the table below. Check the proposed remedy against the actual cause, compatibility, edge cases and maintenance cost. Resolve contradictory suggestions against evidence and project requirements.
5. Finish accepted work: apply the smallest sufficient fix within the task's authorization, then verify the affected behavior and relevant regressions. Continue independent accepted items while another needs clarification. Do not stop at a proposed patch when implementation is already requested.
6. Report the outcome: state what was applied, adapted, deferred or rejected, why, and what evidence or check supports it. Name unresolved risk without inflating it. For several items, a compact disposition table can help.