Clarification for “Lume comparison: keep exposure and charging conditions consistent”: the point beginning “Treat the comparison…” 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.
Forum Replies Created
Case 49 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log · source wording exercise
I'm putting together a side-by-side of the 38mm and 40mm versions of a common three-hand field watch design. The aim is a reference post we can fix over time instead of repeating the same arguments. Corrections go in a dated log at the bottom. What should the table include besides case diameter, and which specs are usually misreported?
Review focus: source wording. Retain the source wording beside any paraphrase. Use the original answer fragment “Diameter alone tells you little…” as the discussion anchor; no new event or result is supplied.
Exercise RWF-29941/49: address this question within its stated limits.
Case 16 — Strap dimensions: lug width, taper, thickness and spring bar diameter explained
Correction to a common shortcut: don't measure lug width on an existing strap. Leather and rubber straps compress or swell, and some are made slightly undersized on purpose. Always measure between the lugs themselves, with the strap removed if possible.
Case 49 — QC checklist: prioritise observable faults over pixel hunting · source wording exercise
Clarification for “QC checklist: prioritise observable faults over pixel hunting”: the point beginning “Explain what the full-size image shows, what the crop adds 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: source wording. Retain the source wording beside any paraphrase.
Distinguish label creation from physical acceptance and retain dated event text with personal details removed. Ask the sender or carrier for clarification; missing scans alone do not establish loss or seizure.
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.
Case 23 — Disputed observation: is this dial colour shift real or just lighting?
Something to keep apart: sunburst and gradient dials can look like different colours depending on viewing angle, even on the same piece. A shift that appears only at certain angles is a finish effect, not a batch difference. Include a straight-on shot and one tilted shot so readers can tell the two apart.
Limit of the answer in “Reading a timegrapher recording without losing the context”: “A single number cannot establish service condition, movement identity…” 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 31 — Packing photographs: document condition without exposing an address
Photograph the item and protective packing separately from the label. Remove names, addresses, barcodes and tracking tokens from public images while keeping originals privately.
Summary draft for “First QC request: the minimum useful information”: the answer addresses “State the model configuration, the specific concern and…”; the related point is “Include complete instrument settings where relevant and say…”. 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 6 — QC checklist: prioritise observable faults over pixel hunting
Method note for “QC checklist: prioritise observable faults over pixel hunting”: use “Start with function, legibility, assembly 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.
Case 16 — Strap compatibility: width is only the first measurement
Two straps share the same nominal width but differ in thickness and spring-bar clearance. Which dimensions need checking?
Exercise RWF-15162/16: address this question within its stated limits.
Clarification for “Shipping timeline: separate dispatch, handover and scan events”: the point beginning “Ask the sender or carrier for clarification; missing scans alone…” 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 31 — Service enquiry: information a watchmaker can use
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.
Method note for “What a water-resistance claim does and does not establish”: use “Ask a qualified watchmaker about a suitable test for that individual…” 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.