Case 11 — Bracelet fit: measuring the usable clasp adjustment
Clarification for “Bracelet fit: measuring the usable clasp adjustment”: the point beginning “Record wrist circumference, removable links and the clasp…” 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.
Reader check for “QC checklist: prioritise observable faults over pixel hunting”: distinguish the discussion point “Start with function, legibility, assembly 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: scope. Keep the stated question separate from any broader claim.
Add a dated correction near the original conclusion and link the new evidence. Preserve the reasoning trail instead of silently replacing an uncertain claim with a confident one.
Case 21 — Maintenance question: how do I tell if an automatic actually needs service?
Sealing and movement performance are separate questions. Ask a qualified watchmaker about inspection and testing appropriate to the particular watch and its intended use; a healthy rate does not establish water resistance.
Method note for “Strap dimensions: lug width, taper, thickness and spring bar diameter explained”: use “Lug width is the essential one: the inside distance between…” 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.
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.
Case 11 — Forum comparison archive: link the evidence and the correction
Clarification for “Forum comparison archive: link the evidence and the correction”: the point beginning “Add a dated correction near the original conclusion…” 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 13 — QC photography: what photos actually help verify a pre-owned listing?
Ask for profile shots of both case sides and a lug-top shot at an angle. Polishing shows as rounded edges, softened bevels or lug holes that look shallower than they should. Compare against a known-good reference image of the same model, not memory. A side-by-side tells you far more than a description.
Case 38 — Bracelet fit: measuring the usable clasp adjustment · source wording exercise
Reader check for “Bracelet fit: measuring the usable clasp adjustment”: distinguish the discussion point “Request the closed bracelet circumference rather than inferring…” 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: source wording. Retain the source wording beside any paraphrase.
Case 1 — Magnetism and rate: record evidence before naming a cause
Method note for “Magnetism and rate: record evidence before naming a cause”: use “Record the change and the circumstances without treating…” 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 29 — 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.
Clarification for “Lume comparison: keep exposure and charging conditions consistent”: the point beginning “Treat the comparison…” 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 39 — Magnetism and rate: record evidence before naming a cause · source wording exercise
Reader check for “Magnetism and rate: record evidence before naming a cause”: distinguish the discussion point “A competent watchmaker can test and diagnose it; random adjustment…” 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: source wording. Retain the source wording beside any paraphrase.
Case 13 — 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.
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.