Case 30 — 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-26765/30: address this question within its stated limits.
Clarification for “Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?”: the point beginning “Comparing against a phone clock once a day for a week,…” 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 32 — 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.
Case 15 — Packing photographs: document condition without exposing an address
A condition record is useful but a shipping label contains personal information. How can the record be shared safely?
Exercise RWF-20359/15: address this question within its stated limits.
Case 12 — Disputed observation: is this dial colour shift real or just lighting?
Batch variation on coloured dials does happen in general. Plating, lacquer thickness and supplier changes can all shift tone, so the claim isn't implausible. Plausible isn't the same as confirmed, though. The thread should keep 'possible' and 'shown' as separate statuses rather than letting repetition turn a hypothesis into accepted fact.
Case 15 — First QC request: the minimum useful information
Correction note for “First QC request: the minimum useful information”: retain the wording beginning “State the model configuration, the specific concern 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.
Limit of the answer in “Strap compatibility: width is only the first measurement”: “Avoid forcing an assembly that does not fit and…” 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.
Batch variation on coloured dials does happen in general. Plating, lacquer thickness and supplier changes can all shift tone, so the claim isn't implausible. Plausible isn't the same as confirmed, though. The thread should keep 'possible' and 'shown' as separate statuses rather than letting repetition turn a hypothesis into accepted fact.
Method note for “Lume questions: why does my lume fade so quickly, and how should I compare it?”: use “Afterglow fades fastest in the first minutes and then settles to…” 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.
Treat the comparison as inconclusive. Repeat with equal light source, charging duration, elapsed time and camera settings; disclose conditions rather than assigning an unsupported quality score.
Case 161 — Service enquiry: information a watchmaker can use · uncertainty exercise
Reader check for “Service enquiry: information a watchmaker can use”: distinguish the discussion point “Document when it stops, winding behaviour, recent impacts and…” 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: uncertainty. Leave the unresolved part visible instead of supplying a result.
Case 47 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log · source wording exercise
Clarification for “Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log”: the point beginning “Diameter alone tells you little…” 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.
Case 45 — Clasp photographs: what to request before judging alignment · source wording exercise
Method note for “Clasp photographs: what to request before judging alignment”: use “Separate cosmetic alignment from whether the clasp engages reliably;…” 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. Retain the source wording beside any paraphrase.
Clarification for “Comparing dial colour under different lighting”: the point beginning “State the lighting 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.
Limit of the answer in “Crown operation: when a forum cannot diagnose the resistance”: “Describe whether resistance occurs during winding or setting and…” 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.