Request human disposal of a sealed review submission
Appends an immutable record that the caller asked for this submission to be withdrawn from review.
RECORDS who asked, for which sealed submission, when, and why.
CHANGES NOTHING. The sealed submission is untouched, nothing is unsealed, and no policy version changes status. This is not a recall: disposal is a human act that this route neither performs nor schedules.
Reachable only by a credential holding the authoring:capability scope, bound by the server to one assigned policy version. A policies:write key and a human session both receive 403: this route is the machine’s way to ask, and a human disposes of a submission directly rather than requesting it.
Bounded write (MCP-034): the server abandons this write if any one lock wait exceeds 2000 ms, or if it is not ready to commit 4000 ms after the server began handling the request. An abandoned write is rolled back — nothing is written — and answered 503 AUTHORING_WRITE_CONTENDED with details.committed: false and a Retry-After header. That answer is a definite non-commit, safe to retry; it is distinct from a lost response or any other 5xx, whose outcome is unknown. The bound is counted from when THIS SERVER began handling the request, which a client cannot observe, and nothing bounds how late a request reaches the server: a client whose request timed out cannot conclude from any wait that it did not commit.
Authorizations
MeshQu API key passed as a bearer token: Authorization: Bearer mqu_…. Mint one in the console (Settings → API keys).
Tenant UUID for multi-tenant isolation. Required on all authenticated routes — validated before authentication (middleware/tenant.ts), so a missing or non-UUID header returns 400 (MISSING_TENANT_ID / INVALID_TENANT_ID) before the API key is checked.
Path Parameters
Body
1 - 2000Response
A recorded request that a human dispose of a sealed review submission. Records the request; changes no state.