Case 7 — Lume comparison: keep exposure and charging conditions consistent
Method note for “Lume comparison: keep exposure and charging conditions consistent”: use “Treat the comparison…” 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.
A bright initial glow followed by a steep drop is normal for photoluminescent pigments. Afterglow fades fastest in the first minutes and then settles to a dim, long-lasting level that dark-adapted eyes can still read. The real question is whether it's readable after an hour in darkness, not how it looks right after charging.
Describe whether resistance occurs during winding or setting and whether the crown engages consistently. Stop forcing it and arrange inspection rather than trying an unverified repair from a thread.
Method note for “Case finishing: distinguish a reflection from a surface mark”: use “Ask for photographs with the light moved 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 “Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?”: use “Start with how you…” 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 “Reading a timegrapher recording without losing the context”: distinguish the discussion point “Keep the complete recording and ask for the…” 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.
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.
Method note for “Strap compatibility: width is only the first measurement”: use “Measure the lug opening and document bar diameter,…” 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 “Comparing dial colour under different lighting”: the point beginning “State the lighting 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 24 — 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-19240/24: address this question within its stated limits.
Case 41 — Strap dimensions: lug width, taper, thickness and spring bar diameter explained · source wording exercise
Correction note for “Strap dimensions: lug width, taper, thickness and spring bar diameter explained”: retain the wording beginning “Measure with a ruler marked in millimetres, ideally…” 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.
Method note for “Service enquiry: information a watchmaker can use”: use “Document when it stops, winding behaviour, recent impacts 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 28 — Lume comparison: keep exposure and charging conditions consistent
Method note for “Lume comparison: keep exposure and charging conditions consistent”: use “Treat the comparison…” 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 38 — QC photography: what photos actually help verify a pre-owned listing? · source wording exercise
Correction note for “QC photography: what photos actually help verify a pre-owned listing?”: retain the wording beginning “Flash flattens printing and hides…” 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 26 — Beginner glossary Q&A: complication, caliber, jewel count, power reserve
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.