Case 22 — Beginner glossary Q&A: complication, caliber, jewel count, power reserve
For a two-watch comparison, the practical order is usually case dimensions first, then power reserve if you rotate, then caliber for serviceability. Jewel count comes last. Complications only matter if you'll use them. Can you say what the two candidates are, in generic terms like 'dive style vs dress style'? The priorities shift a lot between those.
Clarification for “Model comparison: dive bezel action and alignment, how to compare fairly”: the point beginning “Separate three properties: click count (60 or 120 positions), feel (how…” 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.
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: source wording. Retain the source wording beside any paraphrase.
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 114 — Crown operation: when a forum cannot diagnose the resistance · documentation exercise
Method note for “Crown operation: when a forum cannot diagnose the resistance”: use “Stop forcing it and arrange inspection rather than trying…” 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. Distinguish an original record from a proposed record format.
Clarification for “Shipping timeline: separate dispatch, handover and scan events”: the point beginning “Distinguish label creation from physical acceptance and retain dated…” 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.
Clarification for “Case finishing: distinguish a reflection from a surface mark”: the point beginning “Ask for photographs with the light moved 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.
Case 42 — Case finishing: distinguish a reflection from a surface mark · source wording exercise
Correction note for “Case finishing: distinguish a reflection from a surface mark”: retain the wording beginning “A mark should be assessed across multiple views; aggressive polishing…” 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.
Case 29 — Clasp photographs: what to request before judging alignment
Clarification for “Clasp photographs: what to request before judging alignment”: the point beginning “Request open and closed views from both sides,…” 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 9 — QC checklist: prioritise observable faults over pixel hunting
Summary draft for “QC checklist: prioritise observable faults over pixel hunting”: the answer addresses “Start with function, legibility, assembly and…”; the related point is “Explain what the full-size image shows, what the crop adds and…”. 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 9 — Forum comparison archive: link the evidence and the correction
A comparison has been corrected after a new photograph arrived. How should the original thread remain useful?
Exercise RWF-17271/9: address this question within its stated limits.
Case 33 — Magnetism and rate: record evidence before naming a cause
A sudden rate change is being attributed to magnetism without a measurement. How should the discussion be structured?
Exercise RWF-16019/33: address this question within its stated limits.
Case 21 — Crystal reflections: why a dark patch is not a coating test
Method note for “Crystal reflections: why a dark patch is not a coating test”: use “No single lighting setup settles…” 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.
Method note for “Maintenance question: how do I tell if an automatic actually needs service?”: use “Useful signs, in rough order of seriousness: power reserve noticeably shorter…” 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 “Seller review template: facts, dates and unresolved questions”: the answer addresses “Use fields for order date, promised terms, dated…”; the related point is “Leave unsupported fields blank and separate observations from opinions; this…”. 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.