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.
Photograph the item and protective packing separately from the label. Remove names, addresses, barcodes and tracking tokens from public images while keeping originals privately.
Correction note for “Magnetism and rate: record evidence before naming a cause”: retain the wording beginning “A competent watchmaker can test and diagnose it; random adjustment…” 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 32 — Forum comparison archive: link the evidence and the correction
Summary draft for “Forum comparison archive: link the evidence and the correction”: the answer addresses “Add a dated correction near the original conclusion…”; the related point is “Preserve the reasoning trail instead of silently replacing an…”. 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 161 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log · uncertainty exercise
Clarification for “Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log”: the point beginning “State whether thickness includes the highest point…” 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: uncertainty. Leave the unresolved part visible instead of supplying a result.
Case 33 — 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-24631/33: address this question within its stated limits.
Case 44 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me? · source wording exercise
Correction note for “Timegrapher reading context: what do rate, amplitude and beat error actually tell me?”: retain the wording beginning “Without those fields, the rate, amplitude and beat-error values lack…” 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. Retain the source wording beside any paraphrase.
Case 23 — Magnetism and rate: record evidence before naming a cause
Limit of the answer in “Magnetism and rate: record evidence before naming a cause”: “Record the change and the circumstances without treating…” 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.
Clarification for “Seller review template: facts, dates and unresolved questions”: the point beginning “Use fields for order date, promised terms, 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 11 — 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 21 — QC photographs: perspective or a genuinely tilted index?
Method note for “QC photographs: perspective or a genuinely tilted index?”: use “Request a level straight-on image with the hands…” 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.
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 29 — Crystal types: sapphire, mineral and acrylic trade-offs for daily wear
Spec sheets list sapphire, mineral or acrylic crystals, and opinions in threads are very strong. For a daily-wear watch, what are the real trade-offs, and is an anti-reflective coating worth paying for?
Exercise RWF-12476/29: address this question within its stated limits.
Domed crystals of any material add distortion at the edges, which some people like and others find hard to read at angles. Box-shaped or high-domed crystals also add thickness. If you're comparing two otherwise similar watches, check total thickness against crystal profile before assuming the case itself is thicker.
One more term that will come up is 'hacking', meaning the seconds hand stops when you pull the crown so you can set the time to the second. It's minor, but beginners often assume every automatic has it, and not all do. That rounds out the glossary: caliber means what, complication means extra functions, jewels mean bearings, power reserve means how long it runs, hacking means precise setting.