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.
Forum Replies Created
Case 34 — 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.
Case 44 — Crystal reflections: why a dark patch is not a coating test · source wording exercise
Method note for “Crystal reflections: why a dark patch is not a coating test”: use “Compare multiple controlled angles and describe the visible observation without asserting…” 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.
Clarification for “Bracelet fit: measuring the usable clasp adjustment”: the point beginning “Request the closed bracelet circumference rather than inferring…” 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 22 — A maintenance log that remains useful after a sale
Summary draft for “A maintenance log that remains useful after a sale”: the answer addresses “Keep the date, work performed, provider invoice reference…”; the related point is “Redact addresses and payment information; do not invent service…”. 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.
Reader check for “Comparing versions without mixing case sizes”: distinguish the discussion point “Match reference, dimensions 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 15 — QC photographs: perspective or a genuinely tilted index?
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.
Case 15 — 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-19445/15: address this question within its stated limits.
Case 20 — QC photographs: perspective or a genuinely tilted index?
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.
Limit of the answer in “Bracelet fit: measuring the usable clasp adjustment”: “Record wrist circumference, removable links and the clasp…” 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 25 — Model comparison: dive bezel action and alignment, how to compare fairly
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.
Case 36 — Magnetism and rate: record evidence before naming a cause
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 19 — Forum comparison archive: link the evidence and the correction
Clarification for “Forum comparison archive: link the evidence and the correction”: the point beginning “Add a dated correction near the original conclusion…” 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 5 — Model comparison: dive bezel action and alignment, how to compare fairly
Correction to earlier posts in similar threads: 120-click bezels aren't automatically worse. More positions means smaller steps, which can feel less pronounced. Comparing a 60-click and a 120-click bezel on crispness alone is apples to oranges. Compare same-click-count designs, or note the difference clearly.
Clarification for “Lume comparison: keep exposure and charging conditions consistent”: the point beginning “Treat the comparison…” 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.