ValidStitch surfaces three responses for every finding. Accept the suggested fix, override with a note, or mark ignore-and-document. The right response depends on the finding type, your judgment, and how much trust your shop has built up with the validator's defaults.
Accept the suggested fix
Use this when the validator offers a deterministic remediation and the suggested change is what you would have done by hand. Density-thinning a single over-threshold fill region, snapping a design back inside the hoop's safe-stitch area, splitting a long satin — these are the kinds of finds where Accept is the right default. The change is applied to a new file revision, the original is preserved in the project history.
Override with a note
Use this when the validator suggests a fix but you know something it doesn't — the buyer specifically requested the long satin for visual reasons, the design is going on canvas instead of the project's default fabric, or the suggestion would conflict with a customer-approved proof. Add a one-line note explaining the override. The note travels with the project and appears on the setup sheet so the operator knows why the report disagrees with the file.
Ignore and document
Use this for warnings or info-level findings you've decided are acceptable — they'll still appear in the report (you can't pretend they didn't exist), but they won't block export and the operator's setup sheet will show them as 'reviewed and accepted'. Errors cannot be ignored; they have to be either accepted or overridden.
The audit trail
Every accept / override / ignore action records who, when, and (for overrides) why. The audit trail is visible on the project page and exported with the setup sheet. For shops that need it for customer disputes or quality audits, the full per-project history is downloadable as a CSV.