Correction note for “Strap compatibility: width is only the first measurement”: retain the wording beginning “Avoid forcing an assembly that does not fit 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.
Forum Replies Created
Case 22 — QC checklist: prioritise observable faults over pixel hunting
Limit of the answer in “QC checklist: prioritise observable faults over pixel hunting”: “Start with function, legibility, assembly 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.
Limit of the answer in “Movement identification: the limits of a rotor photograph”: “Describe visible bridge shapes and markings separately…” 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 32 — Lume comparison: keep exposure and charging conditions consistent
Method note for “Lume comparison: keep exposure and charging conditions consistent”: use “Treat the comparison…” 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.
Correction to a common shortcut: don't measure lug width on an existing strap. Leather and rubber straps compress or swell, and some are made slightly undersized on purpose. Always measure between the lugs themselves, with the strap removed if possible.
Case 4 — QC photographs: perspective or a genuinely tilted index?
Limit of the answer in “QC photographs: perspective or a genuinely tilted index?”: “Request a level straight-on image with the hands…” 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 36 — QC checklist: prioritise observable faults over pixel hunting
Clarification for “QC checklist: prioritise observable faults over pixel hunting”: the point beginning “Start with function, legibility, assembly 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.
First, a clarifying question: how many links are on each side of the clasp right now? Fit often improves by moving one link from the 6 o'clock side to the 12 o'clock side, or the reverse. That doesn't change length, but it shifts where the clasp sits under the wrist, and a centred clasp feels less tight.
Case 26 — QC checklist: prioritise observable faults over pixel hunting
Correction note for “QC checklist: prioritise observable faults over pixel hunting”: retain the wording beginning “Start with function, legibility, assembly 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.
Case 1 — Crystal reflections: why a dark patch is not a coating test
Method note for “Crystal reflections: why a dark patch is not a coating test”: use “No single lighting setup settles…” 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 20 — QC checklist: prioritise observable faults over pixel hunting
Correction note for “QC checklist: prioritise observable faults over pixel hunting”: retain the wording beginning “Start with function, legibility, assembly 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.
Case 2 — Date window centring: compare the same date at the same angle
Different numerals have different optical centres. A comparison mixes two dates and unequal magnification. How can the evidence be improved?
Exercise RWF-16431/2: address this question within its stated limits.
Summary draft for “Clasp photographs: what to request before judging alignment”: the answer addresses “Request open and closed views from both sides,…”; the related point is “Separate cosmetic alignment from whether the clasp engages reliably;…”. 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.
Case 3 — Comparing dial colour under different lighting
Clarification for “Comparing dial colour under different lighting”: the point beginning “State the lighting 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.
Correction note for “QC photographs: perspective or a genuinely tilted index?”: retain the wording beginning “Compare two independently aligned images before drawing a conclusion; an overlay…” 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.