Case 8 — 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.
Case 33 — Forum comparison archive: link the evidence and the correction
Method note for “Forum comparison archive: link the evidence and the correction”: use “Add a dated correction near the original conclusion…” 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.
Limit of the answer in “Strap compatibility: width is only the first measurement”: “Avoid forcing an assembly that does not fit 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.
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.
Request open and closed views from both sides, with the watch supported safely. Separate cosmetic alignment from whether the clasp engages reliably; functional concerns need hands-on inspection.
Case 31 — Disputed observation: is this dial colour shift real or just lighting?
Suggested protocol. 1) Both dials in one frame. 2) Diffuse daylight, no direct sun, plus a second shot under neutral indoor light. 3) Grey card visible. 4) No filters, no editing. 5) State camera settings if known. If both shots show the same direction of difference, the claim is supported. If the difference flips between lighting conditions, it's most likely lighting.
Summary draft for “Lume comparison: keep exposure and charging conditions consistent”: the answer addresses “Treat the comparison…”; the related point is “Repeat with equal light source, charging duration, elapsed time and camera…”. 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 28 — Crown operation: when a forum cannot diagnose the resistance
Method note for “Crown operation: when a forum cannot diagnose the resistance”: use “Describe whether resistance occurs during winding or setting 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.
Clarification for “Comparing versions without mixing case sizes”: the point beginning “Match reference, dimensions 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 16 — Strap compatibility: width is only the first measurement
Summary draft for “Strap compatibility: width is only the first measurement”: the answer addresses “Measure the lug opening and document bar diameter,…”; the related point is “Avoid forcing an assembly that does not fit 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.
Case 23 — Reading a timegrapher recording without losing the context
Method note for “Reading a timegrapher recording without losing the context”: use “Keep the complete recording and ask for the…” 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 note for “What a water-resistance claim does and does not establish”: retain the wording beginning “Ask a qualified watchmaker about a suitable test for that individual…” 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.
Start with how you measured it. Comparing against a phone clock once a day for a week, at the same time, and noting the offset is reliable enough. One 24-hour reading isn't, because rate depends on wrist time, position overnight and state of wind. Average across several days before deciding anything.
Batch variation on coloured dials does happen in general. Plating, lacquer thickness and supplier changes can all shift tone, so the claim isn't implausible. Plausible isn't the same as confirmed, though. The thread should keep 'possible' and 'shown' as separate statuses rather than letting repetition turn a hypothesis into accepted fact.
Case 35 — 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.