Case 19 — Crown operation: when a forum cannot diagnose the resistance
A description of stiffness does not establish the cause. What information is safe and useful to collect before an inspection?
Exercise RWF-29888/19: address this question within its stated limits.
Case 32 — Forum comparison archive: link the evidence and the correction
Add a dated correction near the original conclusion and link the new evidence. Preserve the reasoning trail instead of silently replacing an uncertain claim with a confident one.
Case 106 — Bracelet fit: measuring the usable clasp adjustment · comparison exercise
A nominal case diameter says little about a bracelet that cannot be shortened enough. How should a sizing question be documented?
Review focus: comparison. Make the basis of a comparison explicit before interpreting it. Use the original answer fragment “Record wrist circumference, removable links and the clasp…” as the discussion anchor; no new event or result is supplied.
Exercise RWF-28278/106: address this question within its stated limits.
Reader check for “Seller review template: facts, dates and unresolved questions”: distinguish the discussion point “Use fields for order date, promised terms, dated…” 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 4 — Beginner glossary Q&A: complication, caliber, jewel count, power reserve
Power reserve is how long the watch runs from full wind until it stops. It matters if you rotate watches: a 38-hour reserve may stop over a weekend off the wrist, while 70-plus hours may not. One clarifying point is that rate stability often gets worse near the end of the reserve, so the full figure is not all precision-grade running time.
Summary draft for “Shipping timeline: separate dispatch, handover and scan events”: the answer addresses “Ask the sender or carrier for clarification; missing scans alone…”; the related point is “Distinguish label creation from physical acceptance and retain dated…”. 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.
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 21 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?
A correction to a common belief: an automatic doesn't need to match a quartz watch to be healthy. Consistency matters more than the absolute figure. A watch that's reliably -8 every day is easy to live with, since you correct it once a week. One that swings from +10 to -15 is the real concern.
Case 23 — Lume comparison: keep exposure and charging conditions consistent
Two glowing dials are shown with different camera exposure and unknown charging time. What can the images establish?
Exercise RWF-20916/23: address this question within its stated limits.
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 20 — Clasp photographs: what to request before judging alignment
Correction note for “Clasp photographs: what to request before judging alignment”: retain the wording beginning “Request open and closed views from both sides,…” 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.
Reader check for “Disputed observation: is this dial colour shift real or just lighting?”: distinguish the discussion point “The difficulty is that phone cameras adjust white balance automatically,…” 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 48 — Crystal reflections: why a dark patch is not a coating test · source wording exercise
Clarification for “Crystal reflections: why a dark patch is not a coating test”: the point beginning “Compare multiple controlled angles and describe the visible observation without asserting…” 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: source wording. Retain the source wording beside any paraphrase.
Case 7 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
The reported numbers alone do not establish damage or the need for service. Confirm the setup, collect comparable readings and ask a watchmaker to assess a concerning or changing pattern.
State the model configuration, the specific concern and links to clear redacted images. Include complete instrument settings where relevant and say explicitly what evidence is missing.