Correction note for “Comparing versions without mixing case sizes”: retain the wording beginning “Match reference, dimensions 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 32 — What a water-resistance claim does and does not establish
Clarification for “What a water-resistance claim does and does not establish”: the point beginning “Ask a qualified watchmaker about a suitable test for that individual…” 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.
Reader check for “Lug-to-lug and end-link overhang in wrist photographs”: distinguish the discussion point “Record lug-to-lug and the effective span…” from its proposed application. The thread offers a way to reason about the question, without adding a personal experience or a newly observed outcome. Review focus: scope. Keep the stated question separate from any broader claim.
Case 43 — Comparing versions without mixing case sizes · source wording exercise
Two purported versions differ in case diameter and bracelet. How can the comparison avoid attributing every difference to a revision?
Review focus: source wording. Retain the source wording beside any paraphrase. Use the original answer fragment “List confirmed differences separately from seller descriptions and date the comparison…” as the discussion anchor; no new event or result is supplied.
Exercise RWF-29254/43: address this question within its stated limits.
Case 16 — A maintenance log that remains useful after a sale
Clarification for “A maintenance log that remains useful after a sale”: the point beginning “Keep the date, work performed, provider invoice reference…” 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 3 — QC photographs: perspective or a genuinely tilted index?
Clarification for “QC photographs: perspective or a genuinely tilted index?”: the point beginning “Request a level straight-on image with the hands…” 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 1 — Reading a timegrapher recording without losing the context
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.
Method note for “Crystal types: sapphire, mineral and acrylic trade-offs for daily wear”: use “The core trade-off is scratch resistance…” 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.
State the lighting and white-balance limitations. Compare controlled images where available and avoid calling a colour defect from differently processed photographs.
Case 30 — Forum comparison archive: link the evidence and the correction
Limit of the answer in “Forum comparison archive: link the evidence and the correction”: “Add a dated correction near the original conclusion…” 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 42 — Lume comparison: keep exposure and charging conditions consistent · source wording exercise
Reader check for “Lume comparison: keep exposure and charging conditions consistent”: distinguish the discussion point “Repeat with equal light source, charging duration, elapsed time and camera…” from its proposed application. The thread offers a way to reason about the question, without adding a personal experience or a newly observed outcome. Review focus: source wording. Retain the source wording beside any paraphrase.
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 3 — Lume questions: why does my lume fade so quickly, and how should I compare it?
Lume photos are close to useless for comparison unless exposure is fixed. Phones raise exposure automatically in the dark, so a dim watch can look as bright as a strong one. For a fair photo comparison: same charge method, same delay after charging, manual exposure, and both watches in the same frame.
Clarification for “Crystal reflections: why a dark patch is not a coating test”: the point beginning “No single lighting setup settles…” 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 10 — 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.