Case 104 — Lume questions: why does my lume fade so quickly, and how should I compare it? · comparison exercise
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.
Review focus: comparison. Make the basis of a comparison explicit before interpreting it. Use the original answer fragment “The real question is whether it's readable after an hour in…” as the discussion anchor; no new event or result is supplied.
Exercise RWF-28599/104: address this question within its stated limits.
Case 4 — Crystal types: sapphire, mineral and acrylic trade-offs for daily wear
Clarifying question: what does daily wear mean for you? Desk work, manual labour or sports change the answer. For desk use, sapphire's scratch resistance is the main benefit. For work with frequent knocks, a slightly domed acrylic that you can polish may last longer in practice, despite the scratches.
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.
Case 34 — Lume comparison: keep exposure and charging conditions consistent
Summary draft for “Lume comparison: keep exposure and charging conditions consistent”: the answer addresses “Treat the comparison…”; the related point is “Repeat with equal light source, charging duration, elapsed time and camera…”. 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 9 — Movement identification: the limits of a rotor photograph
Limit of the answer in “Movement identification: the limits of a rotor photograph”: “Describe visible bridge shapes and markings separately…” 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 14 — 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 24 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log
Before the table goes live, a question: are you comparing current production only, or older references too? Dial printing, lume colour and crown signing often changed between batches. If older pieces are in scope, add a production-period column, or every disagreement will look like an error when it's really a running change.
Case 6 — Clasp photographs: what to request before judging alignment
Correction note for “Clasp photographs: what to request before judging alignment”: retain the wording beginning “Request open and closed views from both sides,…” 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.
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 “Comparing dial colour under different lighting”: use “Compare controlled images where available and avoid calling a…” 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 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.
Case 12 — 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.
If the manufacturer provides a suitable procedure, a running-time log can support a service enquiry. State the winding method and stop time. A shortened run does not identify the cause by itself.
Case 31 — Movement identification: the limits of a rotor photograph
Describe visible bridge shapes and markings separately from the proposed identification. Ask a qualified watchmaker to inspect it if identification matters for servicing; do not open the case merely for a forum answer.
Case 24 — Strap dimensions: lug width, taper, thickness and spring bar diameter explained
Document spring-bar diameter, end-tip fit and the strap’s clearance using appropriate measuring tools. If dimensions or compatibility are uncertain, ask a watchmaker rather than forcing a bar or substituting an unsuitable part.