List the pending work in this API key's authoring capability's scope
The pending review and activation work (the GET /v1/work/pending items) for the policy version the calling key’s governing authoring capability names and, at most, the ONE earlier draft that version’s next seal is bound to (included only when a grant of the same capability chain names it); the return that next seal must name as answers_record_id, if any; and the unanswered returns in view that no seal can answer, as information. The scope comes only from the key’s signed grants: the request takes no path, body or query parameters. Nothing in the response names who acts next or grants anything; review, ratify and activate stay human.
Reachable only by a credential holding the authoring:capability scope and no policies:read / policies:write, whose capability grants BOTH policy.read and review.retrieve (after any intent narrowing). A broad key and a human session receive 403 FORBIDDEN; a capability that is missing, revoked or exhausted (anywhere in its chain), expired, not yet valid or fails integrity receives the gate’s 403 AUTHORING_CAPABILITY_* code; a grant lacking either action receives 403 AUTHORING_CAPABILITY_OUT_OF_SCOPE; a key holding policies:read or policies:write beside the carrier scope, or a capability carried to a successor while the read ran, receives 403 AUTHORING_CAPABILITY_OBJECT_MISMATCH.
Not a snapshot: several statements, and a seal, return or record can commit between them. Re-read the exact subject before acting. Poll no more than once a minute while something is pending, backing off to five minutes when nothing changes. Writes nothing.
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.
Response
Default Response
The grant whose signed chain scoped this read: the grant governing the key when the read ran. Compare it with the grant you hold; a difference means the capability was carried.
The grant that chain starts at (equal to capability_id unless it was carried).
The governing grant's policy.
The governing grant's policy version: the head.
x >= 1Server time at the start of the read. It is NOT a snapshot time: the read is several statements, and a seal, return or record can commit between them. Before acting, re-read the exact subject.
SW-201 pending-work items for the head and, at most, the ONE earlier draft the head's next seal is bound to (the lineage-previous version, when a grant of this capability's chain names it). Always present; may be empty. Names no actor and no eligibility.
Unanswered returns in view that no seal is required to answer and none can. Information, not a task. Always present; may be empty.
The one return the NEXT SEAL OF THIS VERSION must name as answers_record_id, whoever makes it. Present exactly when the lineage-previous submission (the same lookup the seal route refuses on) was returned and this version is draft or submitted. Absent otherwise.
Present when this version's draft-supersession lineage could not be followed back (a cycle, more than 64 links, or a dangling link) at ANY point — the same meaning as on the review-submission list read. The absence of next_seal_answers, of an earlier draft's item, or of a return then says nothing. Only when no sealed version was reached before the failure is the next seal refused 409 LINEAGE_UNRESOLVED; a failure beyond the sealed version the next seal answers does not refuse it, and next_seal_answers is then still given.
true Present when the lineage-previous version (the one the next seal is bound to) was found but no grant of this capability's chain names it, so that version's items are not listed. The seal is not refused for this reason, which is why next_seal_answers is still given. It can appear together with lineage_unresolved when the walk failed only BEYOND that version.
true