transformlisted

## Intent Transform data from one format or schema to another while tracking what information is preserved, modified, or lost during conversion. Ensure output conforms to target schema with full provenance. **Success criteria:** - Output conforms to target schema - All fields mapped correctly or explicitly marked as lost - Transformation is deterministic and reproducible - Loss/distortion explicitly documented - Evidence anchors trace source to output **Compatible schemas:** - `schemas/output_schema.yaml` ## Inputs | Parameter | Required | Type | Description | |-----------|----------|------|-------------| | `source` | Yes | string or object | Input data to transform | | `target_schema` | Yes | string or object | Schema or format specification for output | | `mapping` | No | object | Explicit field mappings (source -> target) | | `preserve_unknown` | No | boolean | Keep fields not in mapping (default: false) | | `strict` | No | boolean | Fail on any mapping ambiguity (default: false) | | `default_values` | No | object | Defaults for missing required fields | ## Procedure 1) **Parse source data**: Load and validate input - Identify source format (JSON, YAML, XML, CSV, etc.) - Parse into internal representation - Detect encoding and special characters - Record source structure for provenance 2) **Analyze target schema**: Understand destination requirements - Load target schema specification - Identify required vs optional fields - Note type constrain