Method note for “Magnetism and rate: record evidence before naming a cause”: use “A competent watchmaker can test and diagnose it; random adjustment…” 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.
Forum Replies Created
Case 31 — Comparing versions without mixing case sizes
Two purported versions differ in case diameter and bracelet. How can the comparison avoid attributing every difference to a revision?
Exercise RWF-28150/31: address this question within its stated limits.
Case 36 — Crystal reflections: why a dark patch is not a coating test
Correction note for “Crystal reflections: why a dark patch is not a coating test”: retain the wording beginning “No single lighting setup settles…” 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 78 — Crown operation: when a forum cannot diagnose the resistance · comparison exercise
A description of stiffness does not establish the cause. What information is safe and useful to collect before an inspection?
Review focus: comparison. Make the basis of a comparison explicit before interpreting it. Use the original answer fragment “Describe whether resistance occurs during winding or setting and…” as the discussion anchor; no new event or result is supplied.
Exercise RWF-25905/78: address this question within its stated limits.
Case 1 — Model comparison: dive bezel action and alignment, how to compare fairly
People keep comparing the bezels on two similar dive-style watches. One is called crisp, the other mushy, and alignment complaints come up for both. What would a fair comparison look like, and what is actually a defect versus a preference?
Exercise RWF-24597/1: address this question within its stated limits.
Clarification for “What a water-resistance claim does and does not establish”: the point beginning “Ask a qualified watchmaker about a suitable test for that individual…” 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 photography: what photos actually help verify a pre-owned listing?
Ask for profile shots of both case sides and a lug-top shot at an angle. Polishing shows as rounded edges, softened bevels or lug holes that look shallower than they should. Compare against a known-good reference image of the same model, not memory. A side-by-side tells you far more than a description.
Case 6 — Case finishing: distinguish a reflection from a surface mark
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.
Distinguish label creation from physical acceptance and retain dated event text with personal details removed. Ask the sender or carrier for clarification; missing scans alone do not establish loss or seizure.
Clarifying question: does anyone in the thread have access to both versions at once? Without simultaneous comparison, every claim either way is weak evidence. If not, the next best option is photos with a grey card in frame and white balance locked or set manually, which at least makes separate photos roughly comparable.
Case 36 — Crown operation: when a forum cannot diagnose the resistance
Describe whether resistance occurs during winding or setting and whether the crown engages consistently. Stop forcing it and arrange inspection rather than trying an unverified repair from a thread.
Clarification for “QC photographs: perspective or a genuinely tilted index?”: the point beginning “Request a level straight-on image with the hands…” 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 “QC checklist: prioritise observable faults over pixel hunting”: use “Start with function, legibility, assembly and…” 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 39 — Reading a timegrapher recording without losing the context · source wording exercise
Correction note for “Reading a timegrapher recording without losing the context”: retain the wording beginning “A single number cannot establish service condition, movement identity…” 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 37 — Clasp photographs: what to request before judging alignment · source wording exercise
Summary draft for “Clasp photographs: what to request before judging alignment”: the answer addresses “Separate cosmetic alignment from whether the clasp engages reliably;…”; the related point is “Request open and closed views from both sides,…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: source wording. Retain the source wording beside any paraphrase.