Separate three properties: click count (60 or 120 positions), feel (how firm each click is, and whether there's back-play), and alignment (whether the pip lines up with the 12 o'clock marker at rest). Crisp vs mushy is mostly about feel and back-play. Alignment can be measured, so treat it separately.
Forum Replies Created
Clarification for “Magnetism and rate: record evidence before naming a cause”: the point beginning “Record the change and the circumstances without treating…” 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 13 — Date window centring: compare the same date at the same angle
Summary draft for “Date window centring: compare the same date at the same angle”: the answer addresses “Use the same numeral, camera axis…”; the related point is “Keep the uncropped originals alongside the detail crops and distinguish…”. 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 141 — What a water-resistance claim does and does not establish · documentation exercise
Method note for “What a water-resistance claim does and does not establish”: use “A photograph or a caseback engraving is not…” 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.
Case 13 — Service enquiry: information a watchmaker can use
A service question only says that the watch stops occasionally. Which observations make an initial enquiry more useful?
Exercise RWF-24631/13: address this question within its stated limits.
Case 24 — Service enquiry: information a watchmaker can use
Limit of the answer in “Service enquiry: information a watchmaker can use”: “Document when it stops, winding behaviour, recent impacts 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.
Limit of the answer in “Packing photographs: document condition without exposing an address”: “Photograph the item and protective packing…” 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 3 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?
Regulation is possible if you want it closer. On many movements it's a quick adjustment by a watchmaker. Can you check whether the losing rate is consistent or getting worse? A stable -8 is a good candidate for simple regulation. A growing loss points to something else, such as falling amplitude, and regulation alone won't fix that.
Reader check for “Clasp photographs: what to request before judging alignment”: distinguish the discussion point “Request open and closed views from both sides,…” 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.
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.
Case 1 — QC checklist: prioritise observable faults over pixel hunting
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 48 — Comparing dial colour under different lighting · source wording exercise
Limit of the answer in “Comparing dial colour under different lighting”: “Compare controlled images where available and avoid calling a…” 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.
Case 9 — 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-12476/9: address this question within its stated limits.
Case 24 — Magnetism and rate: record evidence before naming a cause
Correction note for “Magnetism and rate: record evidence before naming a cause”: retain the wording beginning “Record the change and the circumstances without treating…” 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.
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.