Ingest & deliveries

Composed from GET /corridors, GET /schedule?shape=matrix (for the stream list), GET /ingest-batches, GET /corridors/{id}/surveys and one GET /ingest-batches/{id} per batch that holds refused rows. There is no one-shot deliveries endpoint, so figures may be seconds apart and each panel fails on its own and says so — a panel that could not load is never drawn as "nothing here".

Ingest a vendor file

step 1 of 2 · every field labelled · nothing is written until you have read the receipt

Dry-run receipt

step 2 · what would happen — read it before anything is written

Recent batches

every commit leaves a receipt · read → accepted / quarantined / duplicate / unparseable

Quarantine triage

grouped by the RULE that fired, never one refused row at a time

Vendor deliveries

a survey is the delivery · a batch is one file of it