What should an exact example-count receipt make inspectable?
In a hypothetical editorial case, a brief requests exactly twelve inspectable examples of public discussion about adjustable storage, but fewer cases qualify. A count receipt must show the shortfall rather than silently weakening the request. It keeps accepted examples, unresolved supply and any proposed scope change distinct so a useful partial file cannot masquerade as completion.
Editorial worksheet: requested_count; counting_unit; accepted_ids; exclusions; unresolved_supply; shortfall; original_requirement_state; owner_choice.
Decision check: Report the shortfall before offering alternatives. Ask the owner whether to wait, authorize another scope or accept an incomplete deliverable.Establish the review object
Copy the requested count and define the counted unit before listing cases. Clarify whether a conversation, claim or described incident counts once. Do not allow multiple snippets from one conversation to become separate examples merely because the deliverable is short of its target.
Inspect the relevant support
Include only inspectable eligible units; exclude duplicates and missing-context candidates with reasons. Read Montage coverage and keep unavailable originals separate. Unavailable supply is not zero occurrences of the phenomenon, but it also cannot be counted as an accepted inspectable example.
Record the decision logic
Reconcile accepted identifiers against the requirement. Record overlapping or uncertain relationships rather than forcing them into convenient totals. Preserve exact arithmetic for the defined unit and avoid converting public accounts into a count of distinct people when identity has not been established.
Apply the bounded disposition
Report the shortfall before offering alternatives. Ask the owner whether to wait, authorize another scope or accept an incomplete deliverable. A proposal to relax eligibility must remain a proposal; the researcher cannot silently replace hard conditions with easier substitutes to reach the count.
Hand over the evidence state
Deliver the receipt with accepted cases and unmet original requirement. Record any later owner change separately so both task versions remain reviewable. Do not claim completion because the JSON is valid, the discovery list is large or the partial examples are especially detailed.
Keep the boundaries clear.
- Do not claim completion because the JSON is valid, the discovery list is large or the partial examples are especially detailed.
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.