Case 14 — Strap dimensions: lug width, taper, thickness and spring bar diameter explained
A notation like 20/16 means 20mm at the lugs, tapering to 16mm at the buckle. Taper affects look and comfort more than fit. A strong taper suits smaller and dressier cases, a straight strap suits sport watches. Your buckle or clasp also has to match the narrow end, so check that if you want to reuse an existing buckle.
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.
Case 45 — Bracelet fit: half-links, micro-adjust holes and the 'between sizes' problem · source wording exercise
Correction note for “Bracelet fit: half-links, micro-adjust holes and the 'between sizes' problem”: retain the wording beginning “Fit often improves by moving one link from the 6 o'clock…” 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 — Strap compatibility: width is only the first measurement
Summary draft for “Strap compatibility: width is only the first measurement”: the answer addresses “Measure the lug opening and document bar diameter,…”; the related point is “Avoid forcing an assembly that does not fit and…”. 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 8 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log
Use a correction row with date, old value, revised value and evidence. A worked example could change a lug-width entry from 20 to 22 mm; do not present that example as a correction to a real model.
Case 28 — Comparing versions without mixing case sizes
Method note for “Comparing versions without mixing case sizes”: use “Match reference, dimensions 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.
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.
Measure the lug opening and document bar diameter, shoulder position and strap thickness. Avoid forcing an assembly that does not fit and let a watchmaker check uncertain clearances.
Method note for “Crystal reflections: why a dark patch is not a coating test”: use “No single lighting setup settles…” 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 27 — 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.
Case 10 — Maintenance question: how do I tell if an automatic actually needs service?
The calendar interval is a conservative default, not a rule. Useful signs, in rough order of seriousness: power reserve noticeably shorter than spec from full wind, rate drifting outside its usual range, the watch stopping on the wrist, gritty or rough winding, and the date changing slowly or late.
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.
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.
Case 33 — Seller review template: facts, dates and unresolved questions
Correction note for “Seller review template: facts, dates and unresolved questions”: retain the wording beginning “Use fields for order date, promised terms, dated…” 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 11 — Movement identification: the limits of a rotor photograph
Limit of the answer in “Movement identification: the limits of a rotor photograph”: “Describe visible bridge shapes and markings separately…” 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.