fix-report

A FIX_REPORT.md standardizes remediation by documenting changes, rationale, and impact assessments for validation failures. It enforces contract and ADR compliance while maintaining one commit per root cause for traceable decisions.

For multiple validation failures sharing root causes, you draft a fix plan template capturing the root-cause analysis and proposed changes. The plan respects CONTRACTS.md and relevant ADRs, ensuring traceable decisions with one commit per root cause.

A FIX_REPORT.md is a standardized document recording what was changed during remediation and why. You need it when diagnosing validation failures and proposing targeted fixes, ensuring contract and ADR compliance in phase-aligned workflows.

Yes, fix-report requires adherence to CONTRACTS.md and relevant ADRs. This compliance ensures proposed changes, impact assessments, and traceable decisions respect established architectural constraints during validation failure remediation.

The best way to standardize fix plans is using structured templates capturing root-cause analyses, proposed changes, constraints, and impact assessments. This enforces contract and ADR compliance for phase-aligned remediation workflows.

Separating fix plans per root cause ensures traceable decisions and targeted fixes. This approach maintains one commit per root cause, keeping remediation actions isolated and verifiable against CONTRACTS.md and relevant ADRs.