Gate a research release on explicit coverage assertions — what should the operator record?
A technically valid table can still fail the brief because its window, count or source scope does not meet an explicit requirement. Add release assertions tied to those constraints and actual returned evidence. A failure should remain visible; do not weaken the requirement or pad records solely to produce a green readiness label for a handoff.
Check requested constraints and returned limitations before marking an artifact ready.
Record required_count, required_window and allowed_source_contexts only where the brief establishes them. Keep ambiguous constraints unresolved for owner clarification rather than inventing a permissive interpretation that makes the current returned table appear to satisfy an unstated or relaxed version of the user's request.
Record each assertion as passed, failed or unverified for the checked artifact revision. A conditional release needs explicit limitations and owner acceptance; passing schema tests alone does not authorize a done claim when the table still fails an active hard constraint from the brief.Extract hard constraints
Record required_count, required_window and allowed_source_contexts only where the brief establishes them. Keep ambiguous constraints unresolved for owner clarification rather than inventing a permissive interpretation that makes the current returned table appear to satisfy an unstated or relaxed version of the user's request.
Map evidence to each assertion
Use actual admitted membership, validated timestamps and source context fields, including coverage limitations from the receipt. A renderer's card count or a request limit cannot substitute for distinct eligible evidence membership when the requirement concerns accounts, posts or other specific source objects in the artifact.
Test an unmet requirement
Create a labeled fixture below the required membership target and verify readiness becomes blocked-shortfall or explicitly partial. The validator must not copy duplicate rows, fill unknown timestamps or replace withheld identities to make the artifact pass an exact count or window condition by appearance.
Handle conflicting gates
If privacy requires withholding a row, respect that boundary even when it prevents meeting the count. Report the unsupported requirement and its cause to the accountable owner rather than prioritizing a numerical completion claim over permissions or disguising the withheld slot as an eligible visible record.
Publish the actual readiness state
Record each assertion as passed, failed or unverified for the checked artifact revision. A conditional release needs explicit limitations and owner acceptance; passing schema tests alone does not authorize a done claim when the table still fails an active hard constraint from the brief.
Keep the boundaries clear.
- Check requested constraints and returned limitations before marking an artifact ready.
- Operational record: Extract hard constraints. 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.