Import dry-run reports

2 min readReferenceUpdated 2026-05-19

What you'll find here

The three records that compose a dry-run report — candidate records, mapped records, and the assembled report — plus the boundary that keeps dry runs from mutating state.

Compatibility report, not a write.

Dry runs do not write tasks, memory, skills, config, receipts, or artifacts. They are compatibility reports for operator review.

Records

Record

Captures

Fields

ImportCandidateRecord

per source

Source id · source type · redacted summary · redaction status.

ImportMappedRecord

per mapping

Source id · target schema · target id · status (mapped / warning / error / unsupported) · warnings · errors.

ImportDryRunReport

per dry run

Source name & kind · candidate records · mapped records · warnings · errors · mutated_state: false · redaction status · policy envelope id · evidence ids · receipt ids.

Boundary

Warnings vs. errors.

Warnings indicate records needing review before import. Errors and unsupported mappings prevent import until the source data or migration map is changed.

Dry-run reports preserve policy, evidence, and receipt links so migration decisions remain auditable.

What's next

ReferenceMigration mapsThe field-level mapping dry runs consume.ReferenceAdjacent-tool migrationThe assessment that precedes a dry run.ReferenceSecret migration policyWhy secrets stay outside imports.