Skip to main content
GET
List the pending work in this API key's authoring capability's scope

Authorizations

Authorization
string
header
required

MeshQu API key passed as a bearer token: Authorization: Bearer mqu_…. Mint one in the console (Settings → API keys).

X-MeshQu-Tenant-Id
string
header
required

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

capability_id
string<uuid>
required

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.

root_capability_id
string<uuid>
required

The grant that chain starts at (equal to capability_id unless it was carried).

policy_id
string<uuid>
required

The governing grant's policy.

policy_version_id
string<uuid>
required

The governing grant's policy version: the head.

policy_version_number
integer
required
Required range: x >= 1
observed_at
string<date-time>
required

Server 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.

items
object[]
required

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.

returns_not_answerable
object[]
required

Unanswered returns in view that no seal is required to answer and none can. Information, not a task. Always present; may be empty.

next_seal_answers
object

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.

lineage_unresolved
enum<boolean>

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.

Available options:
true
lineage_not_backed_by_grant
enum<boolean>

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.

Available options:
true