archivist-finding-triage

Audit finding triage classifies each item into Accept, Reject, Defer, or Needs investigation based on report evidence. It outputs a structured artifact guiding the smallest safe fix, affected files, risk, tests, and branch naming without code edits.

The best way to prioritize audit findings is evidence-based triage evaluating risk, affected docs, and cleanup-task suitability. It produces a structured artifact identifying the smallest safe fix, likely touched files, and test checklists for remediation.

Yes, you can classify a specific finding ID without modifying code. The process evaluates report evidence to guide remediation, outputting a structured triage artifact detailing risk, branch naming, test checklists, and documentation affected.

Yes, audit finding triage requires evidence from the original audit reports. It enforces evidence-based judgments to classify findings into Accept, Reject, Defer, or Needs investigation, ensuring accurate risk assessment and safe remediation planning.

You should defer an audit finding when evidence is insufficient for immediate remediation, classifying it as Needs investigation. This ensures the smallest safe fix is identified without premature code edits or inaccurate risk assessment.

A key limitation when classifying audit findings for cleanup-task suitability is that no code edits are performed. The process outputs a structured triage artifact for documentation and remediation planning based strictly on report evidence.