Case 13 — Crystal reflections: why a dark patch is not a coating test
Summary draft for “Crystal reflections: why a dark patch is not a coating test”: the answer addresses “No single lighting setup settles…”; the related point is “Compare multiple controlled angles and describe the visible observation without asserting…”. 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.
Correction note for “Movement identification: the limits of a rotor photograph”: retain the wording beginning “Describe visible bridge shapes and markings separately…” 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 42 — Case finishing: distinguish a reflection from a surface mark · source wording exercise
Correction note for “Case finishing: distinguish a reflection from a surface mark”: retain the wording beginning “A mark should be assessed across multiple views; aggressive polishing…” 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.
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.
Jewel count describes bearings used in a movement design; it is not a quality ranking. Compare the documented movement architecture and service support rather than assuming a higher count makes one watch better.
Reader check for “Strap compatibility: width is only the first measurement”: distinguish the discussion point “Measure the lug opening and document bar diameter,…” 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 26 — First QC request: the minimum useful information
Summary draft for “First QC request: the minimum useful information”: the answer addresses “State the model configuration, the specific concern and…”; the related point is “Include complete instrument settings where relevant and say…”. 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 26 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
First identify the caliber, lift-angle setting, winding state and measurement position. Without those fields, the rate, amplitude and beat-error values lack enough context for a useful comparison.
Case 7 — Lume comparison: keep exposure and charging conditions consistent
Summary draft for “Lume comparison: keep exposure and charging conditions consistent”: the answer addresses “Treat the comparison…”; the related point is “Repeat with equal light source, charging duration, elapsed time and camera…”. 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 4 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?
Regulation is possible if you want it closer. On many movements it's a quick adjustment by a watchmaker. Can you check whether the losing rate is consistent or getting worse? A stable -8 is a good candidate for simple regulation. A growing loss points to something else, such as falling amplitude, and regulation alone won't fix that.
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.
Case 28 — 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 16 — Crown operation: when a forum cannot diagnose the resistance
Method note for “Crown operation: when a forum cannot diagnose the resistance”: use “Describe whether resistance occurs during winding or setting 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 35 — Movement identification: the limits of a rotor photograph
Correction note for “Movement identification: the limits of a rotor photograph”: retain the wording beginning “Describe visible bridge shapes and markings separately…” 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 4 — 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.