Completion target
A reviewable transformation record containing the untouched source reference, exact input/output contracts, authorized rules, Tool outputs, validation and diff evidence, unresolved exceptions, rollback route, and owner decision.
Data Transformation Decision Record
Transform one governed text or data set while preserving source bytes, meaning, structure, privacy, validation evidence, reversibility, and owner acceptance.
Before you begin
- • Named decision owner
- • Authorized source reference
Risks to control
- • Secrets, personal, regulated, licensed, contractual, or production data can exceed the allowed processing boundary.
- • A local copy may be stale, incomplete, tampered with, or not the system of record.
- • A valid parse can still coerce identifiers, dates, decimals, time zones, nulls, Unicode, or nested values.
- • A fixed sample size can miss rare but consequential records.
Choose your path
Built around the job you need to finish
Transform one governed text or data set from an exact recoverable source contract to one destination contract with field-level rules, round-trip and diff evidence, exceptions, recovery, downstream testing and named acceptance.
Data owner authorizing one transformation
Protect purpose, privacy, rights, source integrity, affected people and recovery while allowing a bounded change.
Name owners and source of truth, freeze source/destination contracts, approve field rules and review the exception and retention record.
Authorizes one downstream use or keeps exact gaps open without calling a parsed export universally clean.
Analyst or developer running the Tools
Apply case, whitespace, replacement, duplicate, sort and format operations without corrupting semantics or hiding coercion.
Version each rule, retain exact Tool input/settings/output, map nonrepresentable values, round-trip where meaningful and classify every material diff.
Produces reproducible evidence and a reversal route rather than an undocumented cleaned file.
Downstream importer or reviewer
Know whether the artifact matches the actual parser, schema, access, integrity and business rules.
Reproduce selected transformations, validate invariants and exceptions, run an isolated destination test and record rejects, logs and rollback.
Accepts only the bounded artifact/version proven in the target context.
Authoritative checks for this workflow
Outputs and checklists are planning aids. Review the linked current authorities and the records, terms, instructions, and requirements that apply to your exact situation before a consequential decision.
- Model for Tabular Data and Metadata on the WebWorld Wide Web Consortium · Official tabular-data model and CSV-variant context for exact dialect, schema, metadata and validation records; a successful parse does not establish semantic preservation.
- Unicode Normalization Forms — UAX #15Unicode Consortium · Current normative Unicode 17 normalization forms, equivalence, versioning and conformance context; compatibility normalization can change distinctions and must be explicitly authorized.
- Data Integrity: Detecting and Responding to Ransomware and Other Destructive EventsNational Institute of Standards and Technology · Official identify, protect, detect, respond and recover context supporting integrity checks, known-good copies, monitoring, response and recovery beyond parser validation.
- NIST Privacy FrameworkNational Institute of Standards and Technology · Official privacy-risk governance route for data processing purpose, affected people, minimization, control, communication and lifecycle decisions.
- CSV InjectionOWASP Foundation · Current defensive context for spreadsheet formula injection and unsafe CSV values; opening or handing off untrusted exports requires destination-specific controls.
- Cross Site Scripting Prevention Cheat SheetOWASP Foundation · Current output-encoding, sanitization and safe-sink context for converted markup; Markdown-to-HTML output is not automatically safe to render.