prove-the-fix-held

# Prove the fix held ## What it does Runs the rule again only after the source has been fixed, reads it on its cadence across a watch period, and tightens it where the failure showed the rule was too loose. Records still failing go back to the trace, because there was more than one source. ## Where it happens The agent does this in three activities across one reference process. Each one names the activity as that process words it. - **Run the Rule Again** - `ref/rev/fix-a-data-quality-failure`, activity 12 - [Fix a Data Quality Failure](../../../../processes/revenue-operations/fix-a-data-quality-failure.md) - **Tighten the Rule** - `ref/rev/fix-a-data-quality-failure`, activity 14 - [Fix a Data Quality Failure](../../../../processes/revenue-operations/fix-a-data-quality-failure.md) - **Watch That the Fix Held** - `ref/rev/fix-a-data-quality-failure`, activity 13 - [Fix a Data Quality Failure](../../../../processes/revenue-operations/fix-a-data-quality-failure.md) ## What to record Per rule: the rule at a version, split into refuse, warn and report, and the count of records already held that would fail it with the kinds of record they are. The date it went live, and the failing count on its cadence until the backfill deadline. Per failure: which rule, what it measures, since when it has been failing and how far past its threshold it sits; the re-run that showed whether the failure was in the data or in the query; the failing records by object, owner and date; the day it first failed set beside what shipped that week; the system, form or person that wrote the failing values, with the evidence that it was that one; the rule's result on the corrected records and on the records written since the source was fixed; and the rule read on its cadence across the watch period. A rule changed or retired lands at a new version with the reason written down. Per merge: the record counts, the related record counts and the affected reports read before and after, with anything that did not reconcile. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.