Case 256 — Seller review template: facts, dates and unresolved questions · reader check exercise
Correction note for “Seller review template: facts, dates and unresolved questions”: retain the wording beginning “Leave unsupported fields blank and separate observations from opinions; this…” in the record. If later material changes it, add the date, the changed wording and the source for that change; do not invent a completed correction here. State what a new reader can and cannot infer from this exercise.
Case 42 — Seller review template: facts, dates and unresolved questions · source wording exercise
Reader check for “Seller review template: facts, dates and unresolved questions”: distinguish the discussion point “Leave unsupported fields blank and separate observations from opinions; this…” from its proposed application. The thread offers a way to reason about the question, without adding a personal experience or a newly observed outcome. Review focus: source wording. Retain the source wording beside any paraphrase.
Case 28 — Lume questions: why does my lume fade so quickly, and how should I compare it?
Use a consistent charge, fixed exposure and several elapsed-time observations. Record readability and the conditions rather than applying an unsupported universal fade-time threshold.
Case 20 — Strap compatibility: width is only the first measurement
Correction note for “Strap compatibility: width is only the first measurement”: retain the wording beginning “Measure the lug opening and document bar diameter,…” in the record. If later material changes it, add the date, the changed wording and the source for that change; do not invent a completed correction here. Keep the stated question separate from any broader claim.
A complication is any function beyond hours, minutes and seconds. A date window counts, technically, and so do a chronograph, GMT hand or moon phase. More complications usually mean more parts, more thickness and more service cost. For a first everyday watch, decide which functions you'd really use before treating them as value.
Reader check for “QC checklist: prioritise observable faults over pixel hunting”: distinguish the discussion point “Start with function, legibility, assembly and…” from its proposed application. The thread offers a way to reason about the question, without adding a personal experience or a newly observed outcome. Review focus: scope. Keep the stated question separate from any broader claim.
Case 8 — Clasp photographs: what to request before judging alignment
Request open and closed views from both sides, with the watch supported safely. Separate cosmetic alignment from whether the clasp engages reliably; functional concerns need hands-on inspection.
Case 30 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log
Use a correction row with date, old value, revised value and evidence. A worked example could change a lug-width entry from 20 to 22 mm; do not present that example as a correction to a real model.
Case 20 — Crystal reflections: why a dark patch is not a coating test
No single lighting setup settles that question. Compare multiple controlled angles and describe the visible observation without asserting material specifications that have not been verified.
Summary draft for “Packing photographs: document condition without exposing an address”: the answer addresses “Remove names, addresses, barcodes and tracking tokens from public…”; the related point is “Photograph the item and protective packing…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: scope. Keep the stated question separate from any broader claim.
Case 30 — Comparing dial colour under different lighting
Correction note for “Comparing dial colour under different lighting”: retain the wording beginning “State the lighting and…” in the record. If later material changes it, add the date, the changed wording and the source for that change; do not invent a completed correction here. Keep the stated question separate from any broader claim.
Case 12 — QC checklist: prioritise observable faults over pixel hunting
A large crop makes tiny differences look dramatic. How can a checklist remain proportionate?
Exercise RWF-10026/12: address this question within its stated limits.
Limit of the answer in “Case finishing: distinguish a reflection from a surface mark”: “Ask for photographs with the light moved and…” is an excerpt from the discussion, not an independent verification. A reader needs the relevant original material before treating an interpretation as established. Review focus: scope. Keep the stated question separate from any broader claim.
Method note for “Magnetism and rate: record evidence before naming a cause”: use “Record the change and the circumstances without treating…” as a row heading in a proposed working record. Put the statement, its supporting source or measurement, and any unresolved detail in separate fields. This proposes a format; it supplies no additional evidence. Keep the stated question separate from any broader claim.
Case 23 — First QC request: the minimum useful information
Correction note for “First QC request: the minimum useful information”: retain the wording beginning “State the model configuration, the specific concern and…” in the record. If later material changes it, add the date, the changed wording and the source for that change; do not invent a completed correction here. Keep the stated question separate from any broader claim.