Case 8 — Strap compatibility: width is only the first measurement
Two straps share the same nominal width but differ in thickness and spring-bar clearance. Which dimensions need checking?
Exercise RWF-30722/8: address this question within its stated limits.
Case 1 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log
State whether thickness includes the highest point of a domed crystal. Different measurement methods can produce different figures, so keep both the source and method beside each dimension.
Case 3 — Strap compatibility: width is only the first measurement
Method note for “Strap compatibility: width is only the first measurement”: use “Measure the lug opening and document bar diameter,…” 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.
Measure the lug opening and document bar diameter, shoulder position and strap thickness. Avoid forcing an assembly that does not fit and let a watchmaker check uncertain clearances.
Correction note for “Timegrapher reading context: what do rate, amplitude and beat error actually tell me?”: retain the wording beginning “First identify the caliber, lift-angle setting, winding…” 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 21 — Seller review template: facts, dates and unresolved questions
Correction note for “Seller review template: facts, dates and unresolved questions”: retain the wording beginning “Use fields for order date, promised terms, dated…” 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 25 — QC photographs: perspective or a genuinely tilted index?
Method note for “QC photographs: perspective or a genuinely tilted index?”: use “Request a level straight-on image with the hands…” 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 23 — Case finishing: distinguish a reflection from a surface mark
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.
Case 13 — First QC request: the minimum useful information
Limit of the answer in “First QC request: the minimum useful information”: “State the model configuration, the specific concern 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.
Case 18 — Lug-to-lug and end-link overhang in wrist photographs
Record lug-to-lug and the effective span including rigid end links. Use a similar camera distance and neutral wrist position; photographs support fit discussion but do not replace measurements.
Clarification for “Reading a timegrapher recording without losing the context”: the point beginning “Keep the complete recording and ask for the…” 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 26 — Movement identification: the limits of a rotor photograph
Clarification for “Movement identification: the limits of a rotor photograph”: the point beginning “Describe visible bridge shapes and markings separately…” 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 18 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
Amplitude depends on the movement and measurement setup. Compare it with appropriate specifications and a qualified watchmaker’s assessment; a universal pass/fail threshold would be misleading.
Method note for “Strap compatibility: width is only the first measurement”: use “Avoid forcing an assembly that does not fit 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.
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.