Case 26 — Bracelet fit: half-links, micro-adjust holes and the 'between sizes' problem
Resolution checklist. 1) Rebalance links around the clasp. 2) Test every micro-adjust hole with each link count. 3) Check fit morning and afternoon. 4) Look for half-links by bracelet reference. 5) Accept slightly loose if the head is light. If none of that works, a strap with finer hole spacing is a reasonable conclusion, not a failure.
Use the same numeral, camera axis and approximate image scale. Keep the uncropped originals alongside the detail crops and distinguish optical balance from physical window alignment.
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 120 — A maintenance log that remains useful after a sale · documentation exercise
Which information should a transferable maintenance log retain while protecting the owner’s identity?
Review focus: documentation. Distinguish an original record from a proposed record format. Use the original answer fragment “Redact addresses and payment information; do not invent service…” as the discussion anchor; no new event or result is supplied.
Exercise RWF-25905/120: address this question within its stated limits.
Start with function, legibility, assembly and clear visible damage. Explain what the full-size image shows, what the crop adds and what remains uncertain; do not turn an overlay into an automatic verdict.
Clarification for “Shipping timeline: separate dispatch, handover and scan events”: the point beginning “Distinguish label creation from physical acceptance and retain dated…” 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 3 — Crystal reflections: why a dark patch is not a coating test
Clarification for “Crystal reflections: why a dark patch is not a coating test”: the point beginning “No single lighting setup settles…” 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 35 — First QC request: the minimum useful information
What should an initial QC request include so replies can address the actual question?
Exercise RWF-19586/35: address this question within its stated limits.
Case 15 — Forum comparison archive: link the evidence and the correction
Limit of the answer in “Forum comparison archive: link the evidence and the correction”: “Add a dated correction near the original conclusion…” 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 — QC photography: what photos actually help verify a pre-owned listing?
A caution: photos can't settle everything. Water resistance, timekeeping and internal condition aren't visible in any image. A short timegrapher video or a stated recent rate test adds information, but treat it as a seller claim unless an independent party confirms it. Photos narrow the risk. They don't remove it.
Case 38 — First QC request: the minimum useful information · source wording exercise
Summary draft for “First QC request: the minimum useful information”: the answer addresses “Include complete instrument settings where relevant and say…”; the related point is “State the model configuration, the specific concern and…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: source wording. Retain the source wording beside any paraphrase.
A bright initial glow followed by a steep drop is normal for photoluminescent pigments. Afterglow fades fastest in the first minutes and then settles to a dim, long-lasting level that dark-adapted eyes can still read. The real question is whether it's readable after an hour in darkness, not how it looks right after charging.
Case 27 — QC photography: what photos actually help verify a pre-owned listing?
Ask for a straight-on dial photo with diffuse light and no flash, the full dial in frame, and the hands placed away from the indices (10:10 isn't ideal, because it covers the upper markers). Flash flattens printing and hides lume condition. Diffuse light shows print edges, alignment and any spotting.
Case 3 — 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.
Clarification for “Reading a timegrapher recording without losing the context”: the point beginning “A single number cannot establish service condition, movement identity…” 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.