Case 23 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?
A correction to a common belief: an automatic doesn't need to match a quartz watch to be healthy. Consistency matters more than the absolute figure. A watch that's reliably -8 every day is easy to live with, since you correct it once a week. One that swings from +10 to -15 is the real concern.
Case 15 — Magnetism and rate: record evidence before naming a cause
Method note for “Magnetism and rate: record evidence before naming a cause”: use “Record the change and the circumstances without treating…” 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 “QC checklist: prioritise observable faults over pixel hunting”: use “Start with function, legibility, assembly 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 31 — Seller review template: facts, dates and unresolved questions
What belongs in a useful review template when no actual purchase experience is being asserted?
Exercise RWF-24834/31: address this question within its stated limits.
Case 21 — QC checklist: prioritise observable faults over pixel hunting
Clarification for “QC checklist: prioritise observable faults over pixel hunting”: the point beginning “Start with function, legibility, assembly 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 — 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.
Reader check for “Movement identification: the limits of a rotor photograph”: distinguish the discussion point “Describe visible bridge shapes and markings separately…” 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 8 — First QC request: the minimum useful information
What should an initial QC request include so replies can address the actual question?
Exercise RWF-19829/8: address this question within its stated limits.
Limit of the answer in “QC checklist: prioritise observable faults over pixel hunting”: “Start with function, legibility, assembly 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.
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.
Case 33 — Bracelet fit: half-links, micro-adjust holes and the 'between sizes' problem
Check whether a compatible half-link exists for the exact bracelet reference. Compatibility involves the connection and hardware, not just width. Ask a watchmaker if the correct part is uncertain.
Case 44 — Lug-to-lug and end-link overhang in wrist photographs · source wording exercise
Method note for “Lug-to-lug and end-link overhang in wrist photographs”: use “Use a similar camera distance and neutral wrist position; photographs support…” 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. Retain the source wording beside any paraphrase.
Case 4 — 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.
Summary draft for “Date window centring: compare the same date at the same angle”: the answer addresses “Use the same numeral, camera axis…”; the related point is “Keep the uncropped originals alongside the detail crops and distinguish…”. 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 19 — QC checklist: prioritise observable faults over pixel hunting
Limit of the answer in “QC checklist: prioritise observable faults over pixel hunting”: “Start with function, legibility, assembly 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.