Add Review Documents
Add documents to an existing review — in one call.
Use this to RESPOND to a review’s findings. Upload the filled Flightline
working doc and its marked decisions are applied automatically (cleared,
disputed, …); upload supporting evidence and it is attached and the review is
re-assessed. The body is JUST documents (multipart/form-data or JSON
signed source URLs) — exactly like creating a review. The working doc itself
carries the dispositions; there is nothing else to send.
Path Parameters
Response
Successful Response
The POST /reviews/{id}/documents response.
Reports how the uploaded documents were handled: how many were ingested as new evidence (and trigger a re-assessment), and — if a Flightline working doc was among them — the per-finding outcome of applying its marked dispositions.
Customer-facing review lifecycle.
A deliberately coarse projection of the internal CaseStatus. Internal
states that are not meaningful to a customer (e.g. the admin-release gate
pending_review, the publication-blocker state) collapse to
processing so we never surface internal workflow detail or
verdict-adjacent signal before the publication gate passes.
queued, awaiting_documents, processing, completed, failed New evidence documents added (excludes the working doc itself).
