Skip to content

Create a review queue with actionable operational states

Use issue type, artifact revision and closure evidence instead of vague review flags.

Guides

Create a review queue with actionable operational states — what should the operator record?

A queue becomes unmanageable when every row simply says needs review. Give each item a concrete operational failure and a testable closure condition. This helps reviewers work on the intended artifact without mistaking a completed formatting check for confirmation that the underlying source claim is true.

Practical operations check
Use issue type, artifact revision and closure evidence instead of vague review flags.
Use issue_key, artifact_revision, row_reference, issue_type and closure_requirement so one item represents one bounded check. A row-reference can be an authorized operational alias, allowing schema triage without embedding a handle or full source passage in every review item.
Give reviewers state definitions and expected evidence, with clear examples of what the queue does not certify about source accuracy. Use a short queue example showing both a resolved formatting issue and an unresolved provenance issue, demonstrating why clearing one does not automatically clear the other.
01 / Guides

Define the queue grain

Use issue_key, artifact_revision, row_reference, issue_type and closure_requirement so one item represents one bounded check. A row-reference can be an authorized operational alias, allowing schema triage without embedding a handle or full source passage in every review item.

02 / Guides

Name allowed states

Separate unassigned, assigned, blocked, awaiting-decision and resolved, explaining which transitions require an accountable reviewer rather than an automated update. Assigned means someone accepted responsibility, not that they gained access or completed the check; keep those distinctions visible in queue filters and status summaries.

03 / Guides

Test an ordinary item

Walk a missing-column issue through the queue using a corrected table revision as closure evidence, not just a done comment. For a missing optional column, the correct resolution may be a documented projection change rather than another retrieval; the closure requirement should reflect the actual contract.

04 / Guides

Check blocked transitions

Ensure an access-denied item cannot move directly to resolved unless the supported outcome actually addresses or explicitly accepts the remaining blocker. A supported disposition such as access-blocked-accepted-for-scope needs an accountable decision and explicit limitations, not a silent conversion of denied evidence into verified data.

05 / Guides

Publish the operating contract

Give reviewers state definitions and expected evidence, with clear examples of what the queue does not certify about source accuracy. Use a short queue example showing both a resolved formatting issue and an unresolved provenance issue, demonstrating why clearing one does not automatically clear the other.

Keep the boundaries clear.

  • Use issue type, artifact revision and closure evidence instead of vague review flags.
  • Operational record: Define the queue grain. Context badges do not certify access.

Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.

Primary references

Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.

Know what social media shows about you.
Start with a question.

Get started
montage