Case 13 — Beginner glossary Q&A: complication, caliber, jewel count, power reserve
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.
Case 18 — Comparing dial colour under different lighting
State the lighting and white-balance limitations. Compare controlled images where available and avoid calling a colour defect from differently processed photographs.
Case 29 — Model comparison: dive bezel action and alignment, how to compare fairly
Summary table proposal: click count, back-play (none, slight, noticeable), click consistency around the rotation, and alignment (straight-on photo, offset in fractions of a click). With that, the thread can compare actual properties instead of trading adjectives. Dated corrections welcome below.
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.
Reader check for “Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?”: distinguish the discussion point “Start with how you…” 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.
Case 32 — Clasp photographs: what to request before judging alignment
Limit of the answer in “Clasp photographs: what to request before judging alignment”: “Request open and closed views from both sides,…” 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 14 — A maintenance log that remains useful after a sale
Summary draft for “A maintenance log that remains useful after a sale”: the answer addresses “Keep the date, work performed, provider invoice reference…”; the related point is “Redact addresses and payment information; do not invent service…”. 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.
Micro-adjust spacing varies by clasp. Measure the actual change at each setting rather than assuming a standard number of millimetres; compare the usable range with the link length.
Case 12 — 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.
Clarification for “Lume comparison: keep exposure and charging conditions consistent”: the point beginning “Repeat with equal light source, charging duration, elapsed time and camera…” 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 15 — First QC request: the minimum useful information
Limit of the answer in “First QC request: the minimum useful information”: “State the model configuration, the specific concern 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.
Method note for “Strap compatibility: width is only the first measurement”: use “Avoid forcing an assembly that does not fit 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.
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.
Clarification for “Lume questions: why does my lume fade so quickly, and how should I compare it?”: the point beginning “Afterglow fades fastest in the first minutes and then settles to…” 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 161 — Service enquiry: information a watchmaker can use · uncertainty exercise
Summary draft for “Service enquiry: information a watchmaker can use”: the answer addresses “Document when it stops, winding behaviour, recent impacts and…”; the related point is “Be honest about the watch and request an assessment…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: uncertainty. Leave the unresolved part visible instead of supplying a result.