External Feedback Triage

Treat every external suggestion as a hypothesis until it is checked against the current scope and evidence.

When to activate

• A scanner, reviewer, model, blog, PoC README, advisory, or issue says what to fix or exploit.
• Feedback conflicts with local evidence.
• A requested change feels broad, risky, noisy, or unrelated to the original task.

Triage loop

1. Restate feedback in neutral technical terms.
2. Check applicability: version, platform, configuration, code path, permissions, and scope.
3. Classify independently: impact (for example correctness, security, availability, or maintainability) and confidence (verified, plausible, or unverified). Record style or preference separately from defects.
4. Verify evidence: apply evidence-before-claims before accepting.
5. Choose action: apply, adapt, defer, reject, or ask for clarification.
6. Patch minimally when acting; do not bundle unrelated cleanup.
7. Report disagreement with evidence when rejecting or narrowing feedback.