comparison-report-writer

To document discrepancies for an audit trail, you populate a standardized comparison report template by collecting baseline and regenerated outputs, classifying each delta by severity and root cause, and saving the final report in a dated run folder for traceability.

The best way to classify output discrepancies by severity and root cause is to apply a standardized comparison report template, categorizing each delta as critical, major, or minor, and identifying its root cause to produce a structured, auditable comparison record.

You create an auditable comparison record for post-analysis scenarios by identifying and documenting discrepancies between two versions of outputs, classifying each delta by severity and root cause, and storing the formal report in a dated run folder.

Yes, you need to populate the COMPARE_RESULTS_TEMPLATE.md file with observed differences between baseline and regenerated outputs to ensure your comparison record is structured, auditable, and ready for formal handoff.

You should store completed comparison reports in a dated run folder, such as 03_outputs/reports/run_YYYYMMDD_HHMM/comparison_report.md, to ensure proper traceability and seamless handoff of your discrepancy documentation.

Yes, this manual-only approach is designed specifically for discrepancy reporting, helping you capture and classify deltas between baseline and regenerated outputs to enable structured, auditable decision-making across different versions.