Case 33 — Movement identification: the limits of a rotor photograph
Correction note for “Movement identification: the limits of a rotor photograph”: retain the wording beginning “Describe visible bridge shapes and markings separately…” 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 5 — Strap compatibility: width is only the first measurement
Limit of the answer in “Strap compatibility: width is only the first measurement”: “Measure the lug opening and document bar diameter,…” 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.
Correction note for “Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log”: retain the wording beginning “Add lug-to-lug, thickness and lug width…” 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.
Method note for “Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log”: use “Diameter alone tells you little…” 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.
Ask for photographs with the light moved and retain the same viewing angle. A mark should be assessed across multiple views; aggressive polishing is not an appropriate diagnostic test.
Case 40 — Reading a timegrapher recording without losing the context · source wording exercise
Method note for “Reading a timegrapher recording without losing the context”: use “A single number cannot establish service condition, movement identity…” 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. Retain the source wording beside any paraphrase.
Case 18 — 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 30 — Lume questions: why does my lume fade so quickly, and how should I compare it?
A practical test without a camera: charge both watches the same way, sit in a dark room, and check readability at 5 minutes, 30 minutes and 2 hours. Write down which you can still read the time on. It's subjective but repeatable, and more useful than a single photo.
Match reference, dimensions and configuration first. List confirmed differences separately from seller descriptions and date the comparison so later readers understand its scope.
Method note for “Lume comparison: keep exposure and charging conditions consistent”: use “Repeat with equal light source, charging duration, elapsed time and camera…” 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.
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.
Case 28 — 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.
Case 2 — 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.
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.
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.