Case 37 — Crystal reflections: why a dark patch is not a coating test · source wording exercise
Limit of the answer in “Crystal reflections: why a dark patch is not a coating test”: “Compare multiple controlled angles and describe the visible observation without asserting…” 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 34 — Crown operation: when a forum cannot diagnose the resistance
Correction note for “Crown operation: when a forum cannot diagnose the resistance”: retain the wording beginning “Describe whether resistance occurs during winding or setting and…” 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.
Clarification for “Service enquiry: information a watchmaker can use”: the point beginning “Document when it stops, winding behaviour, recent impacts 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.
Limit of the answer in “Lume comparison: keep exposure and charging conditions consistent”: “Treat the comparison…” 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.
Record wrist circumference, removable links and the clasp adjustment range in millimetres. Request the closed bracelet circumference rather than inferring it from marketing dimensions.
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 3 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log
I'm putting together a side-by-side of the 38mm and 40mm versions of a common three-hand field watch design. The aim is a reference post we can fix over time instead of repeating the same arguments. Corrections go in a dated log at the bottom. What should the table include besides case diameter, and which specs are usually misreported?
Exercise RWF-20267/3: address this question within its stated limits.
Case 19 — A maintenance log that remains useful after a sale
Limit of the answer in “A maintenance log that remains useful after a sale”: “Keep the date, work performed, provider invoice reference…” 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.
Before the table goes live, a question: are you comparing current production only, or older references too? Dial printing, lume colour and crown signing often changed between batches. If older pieces are in scope, add a production-period column, or every disagreement will look like an error when it's really a running change.
Method note for “Comparing versions without mixing case sizes”: use “Match reference, dimensions 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 25 — Strap compatibility: width is only the first measurement
Correction note for “Strap compatibility: width is only the first measurement”: retain the wording beginning “Measure the lug opening and document bar diameter,…” 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 38 — A maintenance log that remains useful after a sale · source wording exercise
Clarification for “A maintenance log that remains useful after a sale”: the point beginning “Redact addresses and payment information; do not invent service…” 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 14 — Shipping timeline: separate dispatch, handover and scan events
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.
Case 61 — Case finishing: distinguish a reflection from a surface mark · source wording exercise
Clarification for “Case finishing: distinguish a reflection from a surface mark”: the point beginning “A mark should be assessed across multiple views; aggressive polishing…” 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 29 — A maintenance log that remains useful after a sale
Which information should a transferable maintenance log retain while protecting the owner’s identity?
Exercise RWF-08320/29: address this question within its stated limits.