Case 2 — 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.
State whether thickness includes the highest point of a domed crystal. Different measurement methods can produce different figures, so keep both the source and method beside each dimension.
Case 30 — 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.
Photograph the item and protective packing separately from the label. Remove names, addresses, barcodes and tracking tokens from public images while keeping originals privately.
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 3 — Seller review template: facts, dates and unresolved questions
Summary draft for “Seller review template: facts, dates and unresolved questions”: the answer addresses “Use fields for order date, promised terms, dated…”; the related point is “Leave unsupported fields blank and separate observations from opinions; this…”. 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.
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 23 — Bracelet fit: measuring the usable clasp adjustment
Summary draft for “Bracelet fit: measuring the usable clasp adjustment”: the answer addresses “Record wrist circumference, removable links and the clasp…”; the related point is “Request the closed bracelet circumference rather than inferring…”. 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 11 — 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.
Correction note for “Maintenance question: how do I tell if an automatic actually needs service?”: retain the wording beginning “The calendar interval is a conservative…” 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 49 — Lume comparison: keep exposure and charging conditions consistent · source wording exercise
Limit of the answer in “Lume comparison: keep exposure and charging conditions consistent”: “Repeat with equal light source, charging duration, elapsed time and camera…” 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: source wording. Retain the source wording beside any paraphrase.
Case 20 — Maintenance question: how do I tell if an automatic actually needs service?
Common advice says service every five years, but service is expensive and some people run watches much longer. What observable signs actually indicate a mechanical watch needs attention, as opposed to just being due on a calendar?
Exercise RWF-14062/20: address this question within its stated limits.
Case 11 — 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.
Case 35 — Model comparison: dive bezel action and alignment, how to compare fairly
On alignment, a clarifying point: is the misalignment visible straight on, or only from an angle? Parallax on a raised bezel can make a perfectly aligned pip look half a click off when viewed slightly from the side. Photograph straight above the dial before calling it misaligned.
Case 3 — Disputed observation: is this dial colour shift real or just lighting?
Status for now: unresolved. The claim is plausible, but no controlled comparison has been posted. Until one appears, describe it as 'reported, not verified'. When someone posts a same-frame, grey-card comparison under two lighting conditions, the thread can update the status with a date and a link to that post.