Correction note for “Bracelet fit: measuring the usable clasp adjustment”: retain the wording beginning “Record wrist circumference, removable links and the clasp…” 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.
Forum Replies Created
Case 23 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
Amplitude depends on the movement and measurement setup. Compare it with appropriate specifications and a qualified watchmaker’s assessment; a universal pass/fail threshold would be misleading.
Reader check for “Model comparison: dive bezel action and alignment, how to compare fairly”: distinguish the discussion point “Separate three properties: click count (60 or 120 positions), feel (how…” 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.
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 115 — Case finishing: distinguish a reflection from a surface mark · documentation exercise
Clarification for “Case finishing: distinguish a reflection from a surface mark”: the point beginning “A mark should be assessed across multiple views; aggressive polishing…” 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: documentation. Distinguish an original record from a proposed record format.
Clarification for “Date window centring: compare the same date at the same angle”: the point beginning “Use the same numeral, camera axis…” 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 “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 43 — Comparing versions without mixing case sizes · source wording exercise
Limit of the answer in “Comparing versions without mixing case sizes”: “List confirmed differences separately from seller descriptions and date the comparison…” 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: source wording. Retain the source wording beside any paraphrase.
Case 30 — Magnetism and rate: record evidence before naming a cause
Record the change and the circumstances without treating the suspected cause as established. A competent watchmaker can test and diagnose it; random adjustment is not a substitute for assessment.
Case 10 — 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 9 — 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 33 — Magnetism and rate: record evidence before naming a cause
Summary draft for “Magnetism and rate: record evidence before naming a cause”: the answer addresses “Record the change and the circumstances without treating…”; the related point is “A competent watchmaker can test and diagnose it; random adjustment…”. 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 22 — 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.
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.
Summary draft for “Seller review template: facts, dates and unresolved questions”: the answer addresses “Leave unsupported fields blank and separate observations from opinions; this…”; the related point is “Use fields for order date, promised terms, dated…”. 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.