What should a rejected-counterexample log retain?
Imagine this review situation: a team excludes several apparent challenges to a fold-flat storage box claim. Without reasons, those exclusions can look selective and become difficult to revisit. A rejected-counterexample log records the actual eligibility decisions while preserving unresolved candidates instead of forcing every awkward example into accepted or rejected.
Worksheet columns: candidate_url; apparent_challenge; identity_passage; eligibility_rule; disposition; reviewer_reason; unresolved_context.
Decision check: Ask another reviewer to inspect borderline exclusions without the desired conclusion. Record disagreements about identity or conditions.Define the decision unit
Define the folding claim narrowly enough to distinguish storage folding from crushing under load. Record which model and folding action matter. The log should test relevance to that proposition, not defend a preferred product verdict against every possible criticism.
Choose admissible evidence
List each candidate challenge considered, including later exclusions. Keep original links and the relevant passage from Montage results when inspectable. Do not delete an inconvenient example after learning it concerns a different model; the exclusion decision is part of the review record.
Build the working record
Give a factual exclusion reason such as an explicitly identified rigid variant. Link the identifying passage. Similar appearance alone does not establish model identity, and an unavailable source belongs in pending rather than being rejected as if its contents were known.
Test the claim boundary
Ask another reviewer to inspect borderline exclusions without the desired conclusion. Record disagreements about identity or conditions. If the available context cannot resolve them, retain an unresolved state instead of choosing whichever classification strengthens the preferred claim.
Deliver the review artifact
Deliver the log with accepted challenges and the surviving wording. The owner can assess both evidence and fairness of selection. Explain that rejected means outside this claim's eligibility rule, not false, dishonest, unimportant or evidence that no problem exists.
Keep the boundaries clear.
- Explain that rejected means outside this claim's eligibility rule, not false, dishonest, unimportant or evidence that no problem exists.
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.