Case 17 — A maintenance log that remains useful after a sale
Clarification for “A maintenance log that remains useful after a sale”: the point beginning “Keep the date, work performed, provider invoice reference…” belongs to the question as written. It should not be read as a report that a new check, purchase or experiment has been completed. Review focus: scope. Keep the stated question separate from any broader claim.
Case 21 — Shipping timeline: separate dispatch, handover and scan events
Method note for “Shipping timeline: separate dispatch, handover and scan events”: use “Distinguish label creation from physical acceptance and retain dated…” 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.
Summary draft for “Crystal reflections: why a dark patch is not a coating test”: the answer addresses “Compare multiple controlled angles and describe the visible observation without asserting…”; the related point is “No single lighting setup settles…”. 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.
Summary draft for “A maintenance log that remains useful after a sale”: the answer addresses “Redact addresses and payment information; do not invent service…”; the related point is “Keep the date, work performed, provider invoice reference…”. 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 19 — A maintenance log that remains useful after a sale
Limit of the answer in “A maintenance log that remains useful after a sale”: “Keep the date, work performed, provider invoice reference…” 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.
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 16 — Reading a timegrapher recording without losing the context
Method note for “Reading a timegrapher recording without losing the context”: use “Keep the complete recording and ask for the…” 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 31 — What a water-resistance claim does and does not establish
A listing describes a water-resistance rating but provides no test record for the individual watch. What evidence would address the gap?
Exercise RWF-18239/31: address this question within its stated limits.
Case 4 — Model comparison: dive bezel action and alignment, how to compare fairly
Summary table proposal: click count, back-play (none, slight, noticeable), click consistency around the rotation, and alignment (straight-on photo, offset in fractions of a click). With that, the thread can compare actual properties instead of trading adjectives. Dated corrections welcome below.
Case 11 — Beginner glossary Q&A: complication, caliber, jewel count, power reserve
Jewel count describes bearings used in a movement design; it is not a quality ranking. Compare the documented movement architecture and service support rather than assuming a higher count makes one watch better.
Case 41 — First QC request: the minimum useful information · source wording exercise
Clarification for “First QC request: the minimum useful information”: the point beginning “Include complete instrument settings where relevant and say…” belongs to the question as written. It should not be read as a report that a new check, purchase or experiment has been completed. Review focus: source wording. Retain the source wording beside any paraphrase.
Case 23 — QC checklist: prioritise observable faults over pixel hunting
A large crop makes tiny differences look dramatic. How can a checklist remain proportionate?
Exercise RWF-13435/23: address this question within its stated limits.
Reader check for “Case finishing: distinguish a reflection from a surface mark”: distinguish the discussion point “Ask for photographs with the light moved 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 23 — Bracelet fit: measuring the usable clasp adjustment
Clarification for “Bracelet fit: measuring the usable clasp adjustment”: the point beginning “Record wrist circumference, removable links and the clasp…” belongs to the question as written. It should not be read as a report that a new check, purchase or experiment has been completed. Review focus: scope. Keep the stated question separate from any broader claim.
Case 42 — QC photographs: perspective or a genuinely tilted index? · source wording exercise
Correction note for “QC photographs: perspective or a genuinely tilted index?”: retain the wording beginning “Compare two independently aligned images before drawing a conclusion; an overlay…” 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. Retain the source wording beside any paraphrase.