Two steps
Ingest (validate)
Upload a file. A sandbox ingest run parses it, matches an ingestion spec (or one
you force), writes to temporary tables, and produces findings.
Findings
Each finding has a severity —error, warning, or info — and a stage where it
arose (detect, parse, map, loader, strict scan, quarantine). Common finding codes include
coercion loss, extra fields, shape drift, loader exception, row validation, parse error,
and “no spec matched”. The run keeps the top findings and full logs.
Run statuses
Both ingest and promote runs move throughPENDING → RUNNING → SUCCESS / FAILED.
A promote run can finish as SUCCESS but aborted — it ran cleanly yet declined to
copy because the ingest had errors and you didn’t allow promotion with errors. That’s a
safe refusal, not a failure. You can re-run allowing errors if you intend to proceed.

