Skip to content

Maintain a category coverage matrix beside a returned table

Show which requested result kinds returned evidence, remained pending or were unavailable.

Guides

Maintain a category coverage matrix beside a returned table — what should the operator record?

A combined response can contain several evidence kinds with different operational states. One overall success label may hide a category that never returned usable records. Maintain a matrix tied to the original request and actual receipt so recipients can see category-level limitations without converting missing coverage into a negative source finding.

Practical operations check
Show which requested result kinds returned evidence, remained pending or were unavailable.
Start from the actual brief and documented tool scope, not every category the table renderer could theoretically display. Include category_key and requested_state without inventing unsupported source types or assuming every request can read private workspace content.
Place the coverage matrix reference in the manifest and include a checked receipt time. A recipient filtering to one category should still be able to find its specific limitation rather than inherit an overly broad all-results-complete statement.
01 / Guides

List requested categories

Start from the actual brief and documented tool scope, not every category the table renderer could theoretically display. Include category_key and requested_state without inventing unsupported source types or assuming every request can read private workspace content.

02 / Guides

Map actual response states

For each category, record returned rows, explicit errors and any supported pending condition. If no status explains an empty category, use unresolved-empty rather than asserting that the source contains no eligible items or that collection finished exhaustively.

03 / Guides

Connect admitted membership

Link each category's actual valid keys to the working table revision. Keep returned row counts separate from admitted unique objects, especially where one category expands nested references or shares source objects with another representation of the same evidence.

04 / Guides

Test mixed-state output

Use a labeled fixture with one populated category, one explicit failure and one unexplained empty category. Verify all three remain distinguishable in the matrix and that a top-level success cannot automatically relabel them equally complete.

05 / Guides

Release matrix and table together

Place the coverage matrix reference in the manifest and include a checked receipt time. A recipient filtering to one category should still be able to find its specific limitation rather than inherit an overly broad all-results-complete statement.

Keep the boundaries clear.

  • Show which requested result kinds returned evidence, remained pending or were unavailable.
  • Operational record: List requested categories. 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