Case 8 — Model comparison: dive bezel action and alignment, how to compare fairly
On alignment, a clarifying point: is the misalignment visible straight on, or only from an angle? Parallax on a raised bezel can make a perfectly aligned pip look half a click off when viewed slightly from the side. Photograph straight above the dial before calling it misaligned.
Request a level straight-on image with the hands clear of the marker. Compare two independently aligned images before drawing a conclusion; an overlay cannot correct an oblique camera angle.
Case 20 — Date window centring: compare the same date at the same angle
Method note for “Date window centring: compare the same date at the same angle”: use “Use the same numeral, camera axis…” 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 8 — Clasp photographs: what to request before judging alignment
Request open and closed views from both sides, with the watch supported safely. Separate cosmetic alignment from whether the clasp engages reliably; functional concerns need hands-on inspection.
Case 21 — Date window centring: compare the same date at the same angle
Limit of the answer in “Date window centring: compare the same date at the same angle”: “Use the same numeral, camera axis…” 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.
Limit of the answer in “Bracelet fit: half-links, micro-adjust holes and the 'between sizes' problem”: “Fit often improves by moving one link from the 6 o'clock…” 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 34 — Disputed observation: is this dial colour shift real or just lighting?
Clarifying question: does anyone in the thread have access to both versions at once? Without simultaneous comparison, every claim either way is weak evidence. If not, the next best option is photos with a grey card in frame and white balance locked or set manually, which at least makes separate photos roughly comparable.
Case 1 — 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 21 — 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.
Case 11 — Seller review template: facts, dates and unresolved questions
Limit of the answer in “Seller review template: facts, dates and unresolved questions”: “Use fields for order date, promised terms, dated…” 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 53 — Case finishing: distinguish a reflection from a surface mark · source wording 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: source wording. Retain the source wording beside any paraphrase.
Case 11 — Crown operation: when a forum cannot diagnose the resistance
Correction note for “Crown operation: when a forum cannot diagnose the resistance”: retain the wording beginning “Describe whether resistance occurs during winding or setting 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.
Summary draft for “Strap dimensions: lug width, taper, thickness and spring bar diameter explained”: the answer addresses “Lug width is the essential one: the inside distance between…”; the related point is “Measure with a ruler marked in millimetres, ideally…”. 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.
Clarification for “A maintenance log that remains useful after a sale”: the point beginning “Keep the date, work performed, provider invoice reference…” 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 — Disputed observation: is this dial colour shift real or just lighting?
Status for now: unresolved. The claim is plausible, but no controlled comparison has been posted. Until one appears, describe it as 'reported, not verified'. When someone posts a same-frame, grey-card comparison under two lighting conditions, the thread can update the status with a date and a link to that post.