Case 113 — Lume comparison: keep exposure and charging conditions consistent · documentation exercise
Summary draft for “Lume comparison: keep exposure and charging conditions consistent”: the answer addresses “Repeat with equal light source, charging duration, elapsed time and camera…”; the related point is “Treat the comparison…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: documentation. Distinguish an original record from a proposed record format.
Case 3 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log
Use a correction row with date, old value, revised value and evidence. A worked example could change a lug-width entry from 20 to 22 mm; do not present that example as a correction to a real model.
Case 14 — Crystal types: sapphire, mineral and acrylic trade-offs for daily wear
Spec sheets list sapphire, mineral or acrylic crystals, and opinions in threads are very strong. For a daily-wear watch, what are the real trade-offs, and is an anti-reflective coating worth paying for?
Exercise RWF-25919/14: address this question within its stated limits.
A dated note in the frame can support a claim that photographs are recent, but it is not conclusive proof of ownership, authenticity or an honest transaction. Treat it as one limited check alongside independent verification.
Case 6 — Model comparison: dive bezel action and alignment, how to compare fairly
Separate three properties: click count (60 or 120 positions), feel (how firm each click is, and whether there's back-play), and alignment (whether the pip lines up with the 12 o'clock marker at rest). Crisp vs mushy is mostly about feel and back-play. Alignment can be measured, so treat it separately.
Case 31 — Strap compatibility: width is only the first measurement
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 32 — Magnetism and rate: record evidence before naming a cause
Limit of the answer in “Magnetism and rate: record evidence before naming a cause”: “Record the change and the circumstances without treating…” 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 30 — QC photography: what photos actually help verify a pre-owned listing?
Ask for profile shots of both case sides and a lug-top shot at an angle. Polishing shows as rounded edges, softened bevels or lug holes that look shallower than they should. Compare against a known-good reference image of the same model, not memory. A side-by-side tells you far more than a description.
Case 9 — Movement identification: the limits of a rotor photograph
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 “First QC request: the minimum useful information”: the point beginning “State the model configuration, the specific concern 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 17 — 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.
Clarification for “Lug-to-lug and end-link overhang in wrist photographs”: the point beginning “Record lug-to-lug and the effective span…” 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 “Request a level straight-on image with the hands…” 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 “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.
Case 9 — Shipping timeline: separate dispatch, handover and scan events
Summary draft for “Shipping timeline: separate dispatch, handover and scan events”: the answer addresses “Distinguish label creation from physical acceptance and retain dated…”; the related point is “Ask the sender or carrier for clarification; missing scans alone…”. 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.