Case 22 — QC checklist: prioritise observable faults over pixel hunting
Limit of the answer in “QC checklist: prioritise observable faults over pixel hunting”: “Start with function, legibility, assembly 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.
Case 34 — 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.
Record wrist circumference, removable links and the clasp adjustment range in millimetres. Request the closed bracelet circumference rather than inferring it from marketing dimensions.
Case 4 — First QC request: the minimum useful information
Summary draft for “First QC request: the minimum useful information”: the answer addresses “State the model configuration, the specific concern and…”; the related point is “Include complete instrument settings where relevant and say…”. 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.
Clarification for “Strap compatibility: width is only the first measurement”: the point beginning “Measure the lug opening and document bar diameter,…” 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 37 — Forum comparison archive: link the evidence and the correction · source wording exercise
Method note for “Forum comparison archive: link the evidence and the correction”: use “Preserve the reasoning trail instead of silently replacing an…” 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. Retain the source wording beside any paraphrase.
Case 19 — 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.
Summary draft for “Reading a timegrapher recording without losing the context”: the answer addresses “Keep the complete recording and ask for the…”; the related point is “A single number cannot establish service condition, movement identity…”. 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 17 — QC photographs: perspective or a genuinely tilted index?
A marker can look tilted when the camera is above the dial axis. What extra image would separate perspective from an assembly issue?
Exercise RWF-18141/17: address this question within its stated limits.
Case 20 — Maintenance question: how do I tell if an automatic actually needs service?
Clarifying question first: do you have a baseline? If you've never recorded the watch's rate or power reserve, 'drifting' is hard to judge. Start a simple log now with daily offset against a reference time for a week, and the hours it runs from full wind. Once you have that, later changes mean something.
Clarification for “QC checklist: prioritise observable faults over pixel hunting”: the point beginning “Start with function, legibility, assembly and…” 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.
Method note for “What a water-resistance claim does and does not establish”: use “Ask a qualified watchmaker about a suitable test for that individual…” 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 2 — 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-11968/2: address this question within its stated limits.
Ask for photographs with the light moved and retain the same viewing angle. A mark should be assessed across multiple views; aggressive polishing is not an appropriate diagnostic test.
Case 166 — Seller review template: facts, dates and unresolved questions · uncertainty exercise
Limit of the answer in “Seller review template: facts, dates and unresolved questions”: “Use fields for order date, promised terms, dated…” 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: uncertainty. Leave the unresolved part visible instead of supplying a result.