Create Flag
Flag a run finding (run review / drawer). The locator is validated against the spec §3 grammar; surface.number is 0-indexed here.
Design-plane linkage (frontend audit finding 1): flagging a run OWNED BY A
LIVE design session is a design-plane input — the flag row and a user
activity event land in ONE transaction (the ingest job_completed
pattern) and the tick is enqueued after commit, so the brain sees the flag
on its next turn. Execution-plane flags (no session) stay row-only, and so
do flags on terminal (published/archived) sessions — a frozen session’s
transcript never grows and its brain never wakes; the row still feeds the
review queue and rides a future reopen (R6).
Authorizations
Body
The canonical reference shape (frontend spec §3, backend plan A3).
Anchor (run_id/doc_name) → source chain (surface → block_id → cell/word_range/bbox) → semantic axis (field_path | check_id | rule_id | segment) → trace turn. Everything is optional; axes co-occur (an extraction citation = field_path + surface + block_id).
1 - 4000Response
Successful Response
Public processor id (slug).
The canonical reference shape (frontend spec §3, backend plan A3).
Anchor (run_id/doc_name) → source chain (surface → block_id → cell/word_range/bbox) → semantic axis (field_path | check_id | rule_id | segment) → trace turn. Everything is optional; axes co-occur (an extraction citation = field_path + surface + block_id).
open, resolved