Make a cleanup step safe to apply more than once — what should the operator record?
A cleanup routine may run again after a retry or handoff. If each pass trims meaningful characters or repeats text substitutions, the table drifts away from the returned evidence. Define the narrow normalization goal and test repeat application before using the routine on an operational artifact.
Test that repeated local normalization does not repeatedly alter already-normalized evidence.
Specify the exact permitted change, such as normalizing line-ending representation in a derived display field, while preserving raw source text. A rule such as normalizing CRLF to LF in display_excerpt has a narrow testable purpose; a broad improve-text command has no reproducible operational meaning.
Attach the normalization rule to the table manifest and leave unsupported transformations blocked rather than calling every altered cell a harmless cleanup. The manifest can record cleanup_revision c2 and the affected fields, making it clear that the evidence was reformatted locally rather than corrected by its publisher.Bound the cleanup rule
Specify the exact permitted change, such as normalizing line-ending representation in a derived display field, while preserving raw source text. A rule such as normalizing CRLF to LF in display_excerpt has a narrow testable purpose; a broad improve-text command has no reproducible operational meaning.
Separate normalization from interpretation
Do not combine cosmetic cleanup with entity resolution, translation or inclusion decisions under one unreviewable clean-data command. A trim operation can remove meaningful whitespace in code or quoted material, so keep the source representation unchanged and restrict cleanup to explicitly approved display fields.
Test repeat application
Apply the local operation twice to labeled fixtures and compare outputs; the second pass should not introduce further intended changes. Test a string already normalized, one requiring a single conversion and one containing meaningful repeated punctuation; the last case should remain unchanged unless specifically in scope.
Inspect exceptions and collisions
Check whether distinct raw values collapse to the same normalized form, preserving separate identities and recording ambiguity where the display form collides. If distinct raw strings collapse to one display value, that collision should not change qualified keys, source membership or a deduplication decision made elsewhere.
Version the safe operation
Attach the normalization rule to the table manifest and leave unsupported transformations blocked rather than calling every altered cell a harmless cleanup. The manifest can record cleanup_revision c2 and the affected fields, making it clear that the evidence was reformatted locally rather than corrected by its publisher.
Keep the boundaries clear.
- Test that repeated local normalization does not repeatedly alter already-normalized evidence.
- Operational record: Bound the cleanup rule. Context badges do not certify access.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.