Repeatability
High
The transformation logic is structurally identical every month: same carriers, same target schema, same validation rules. This is a pure ETL pipeline with no judgment variation run to run.
Ambiguity Tolerance
High
Success criteria are crisp — eight named output columns, standardized formats, and explicit flagging rules for invalid or missing dates. A non-human can verify completeness and schema conformance automatically.
Data & Tool Availability
High
Sample data is provided, carrier feed formats are known, and the task requires only file I/O and parsing libraries — no external APIs or permissions beyond access to the raw feed files.
Error Cost
Medium
A bad normalization (e.g., swapped origin/destination or silently dropped rows) could corrupt downstream logistics reporting, but the output is a CSV reviewed before use and errors are detectable via row counts and spot checks — not irreversible.
Human Judgment Required
Low
Every decision — field mapping, date parsing, validation flags — is rule-based and deterministic. No taste, ethics, or relationship context is involved.