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: source wording. Retain the source wording beside any paraphrase.
Forum Replies Created
Case 21 — Movement identification: the limits of a rotor photograph
Only part of the movement is visible and the rotor hides several bridges. Which details can be described without claiming certainty?
Exercise RWF-28150/21: address this question within its stated limits.
Case 25 — Shipping timeline: separate dispatch, handover and scan events
Method note for “Shipping timeline: separate dispatch, handover and scan events”: use “Distinguish label creation from physical acceptance and retain dated…” 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 66 — 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.
Method note for “Movement identification: the limits of a rotor photograph”: use “Describe visible bridge shapes and markings separately…” 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.
Clarification for “Crystal reflections: why a dark patch is not a coating test”: the point beginning “No single lighting setup settles…” 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 “Case finishing: distinguish a reflection from a surface mark”: use “A mark should be assessed across multiple views; aggressive polishing…” 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.
Summary draft for “Forum comparison archive: link the evidence and the correction”: the answer addresses “Preserve the reasoning trail instead of silently replacing an…”; the related point is “Add a dated correction near the original conclusion…”. 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.
Correction note for “Case finishing: distinguish a reflection from a surface mark”: retain the wording beginning “A mark should be assessed across multiple views; aggressive polishing…” 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 “Strap compatibility: width is only the first measurement”: the point beginning “Measure the lug opening and document bar diameter,…” 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 24 — Reading a timegrapher recording without losing the context
Correction note for “Reading a timegrapher recording without losing the context”: retain the wording beginning “Keep the complete recording and ask for the…” 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 27 — QC checklist: prioritise observable faults over pixel hunting
Summary draft for “QC checklist: prioritise observable faults over pixel hunting”: the answer addresses “Start with function, legibility, assembly and…”; the related point is “Explain what the full-size image shows, what the crop adds and…”. 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.
Keep a baseline log, describe changes in rate or running time and stop forcing rough winding. Follow the manufacturer’s guidance and arrange professional assessment when operation changes. A forum cannot prescribe a universal service interval.
Case 28 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
First identify the caliber, lift-angle setting, winding state and measurement position. Without those fields, the rate, amplitude and beat-error values lack enough context for a useful comparison.
Case 26 — Service enquiry: information a watchmaker can use
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.