Case 35 — 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.
Clarification for “Crown operation: when a forum cannot diagnose the resistance”: the point beginning “Describe whether resistance occurs during winding or setting and…” 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 11 — Bracelet fit: measuring the usable clasp adjustment
Clarification for “Bracelet fit: measuring the usable clasp adjustment”: the point beginning “Record wrist circumference, removable links and the clasp…” 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 “Seller review template: facts, dates and unresolved questions”: the point beginning “Use fields for order date, promised terms, 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.
Before the table goes live, a question: are you comparing current production only, or older references too? Dial printing, lume colour and crown signing often changed between batches. If older pieces are in scope, add a production-period column, or every disagreement will look like an error when it's really a running change.
Match reference, dimensions and configuration first. List confirmed differences separately from seller descriptions and date the comparison so later readers understand its scope.
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.
Method note for “Bracelet fit: measuring the usable clasp adjustment”: use “Record wrist circumference, removable links and the clasp…” 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 9 — QC checklist: prioritise observable faults over pixel hunting
A large crop makes tiny differences look dramatic. How can a checklist remain proportionate?
Exercise RWF-19101/9: address this question within its stated limits.
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.
Clarification for “What a water-resistance claim does and does not establish”: the point beginning “Ask a qualified watchmaker about a suitable test for that individual…” 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 35 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
I ran a watch on a basic timegrapher and got +6 s/d, 245 degrees amplitude and 0.8 ms beat error, dial up, about an hour after winding. Is this good, bad or normal? I don't want to send it for service on a single reading.
Exercise RWF-15341/35: address this question within its stated limits.
Case 44 — Reading a timegrapher recording without losing the context · source wording exercise
Reader check for “Reading a timegrapher recording without losing the context”: distinguish the discussion point “A single number cannot establish service condition, movement identity…” 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: source wording. Retain the source wording beside any paraphrase.
Caliber is the movement's model designation, like a part number. Two watches from different brands can share the same caliber family with different finishing or regulation. On a spec sheet it tells you what's inside and roughly what service parts are available. It doesn't tell you how well that particular example was adjusted.
Case 39 — Forum comparison archive: link the evidence and the correction · source wording exercise
Summary draft for “Forum comparison archive: link the evidence and the correction”: the answer addresses “Preserve the reasoning trail instead of silently replacing an…”; the related point is “Add a dated correction near the original conclusion…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: source wording. Retain the source wording beside any paraphrase.