Case 3 — Lume questions: why does my lume fade so quickly, and how should I compare it?
My watch's lume is bright for a few minutes and then barely visible. Is that normal? People post lume shots of different watches, but they all seem to use different charging and exposure, so I can't tell what's actually better.
Exercise RWF-27800/3: address this question within its stated limits.
Case 13 — QC checklist: prioritise observable faults over pixel hunting
Clarification for “QC checklist: prioritise observable faults over pixel hunting”: the point beginning “Start with function, legibility, assembly 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.
Case 32 — Disputed observation: is this dial colour shift real or just lighting?
The difficulty is that phone cameras adjust white balance automatically, and blue dials are especially sensitive. Two photos of the same dial under different light can easily look like a 'batch difference'. Any comparison needs both dials in the same frame, under the same light, ideally next to a neutral grey or white reference card.
Reader check for “What a water-resistance claim does and does not establish”: distinguish the discussion point “A photograph or a caseback engraving is not…” 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 15 — QC photographs: perspective or a genuinely tilted index?
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.
Case 19 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
I ran a watch on a basic timegrapher and got +6 s/d, 245 degrees amplitude and 0.8 ms beat error, dial up, about an hour after winding. Is this good, bad or normal? I don't want to send it for service on a single reading.
Exercise RWF-16869/19: address this question within its stated limits.
State the model configuration, the specific concern and links to clear redacted images. Include complete instrument settings where relevant and say explicitly what evidence is missing.
Case 31 — 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 32 — What a water-resistance claim does and does not establish
Summary draft for “What a water-resistance claim does and does not establish”: the answer addresses “Ask a qualified watchmaker about a suitable test for that individual…”; the related point is “A photograph or a caseback engraving is not…”. 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 25 — QC checklist: prioritise observable faults over pixel hunting
A large crop makes tiny differences look dramatic. How can a checklist remain proportionate?
Exercise RWF-10625/25: address this question within its stated limits.
Case 144 — Beginner glossary Q&A: complication, caliber, jewel count, power reserve · documentation exercise
Reader check for “Beginner glossary Q&A: complication, caliber, jewel count, power reserve”: distinguish the discussion point “It doesn't tell you how well that…” 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: documentation. Distinguish an original record from a proposed record format.
Case 30 — Lug-to-lug and end-link overhang in wrist photographs
Record lug-to-lug and the effective span including rigid end links. Use a similar camera distance and neutral wrist position; photographs support fit discussion but do not replace measurements.
Case 28 — 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.
Add lug-to-lug, thickness and lug width as separate rows. Diameter alone tells you little about wearability. Two cases 2mm apart in diameter can be within 1mm of each other lug to lug, and that number decides whether the watch overhangs a small wrist. Also give the source for each figure: manufacturer sheet, caliper measurement, or catalogue listing.