Case 26 — 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.
Limit of the answer in “Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?”: “Comparing against a phone clock once a day for a week,…” 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 48 — A maintenance log that remains useful after a sale · source wording exercise
Limit of the answer in “A maintenance log that remains useful after a sale”: “Redact addresses and payment information; do not invent service…” 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: source wording. Retain the source wording beside any paraphrase.
Case 123 — QC checklist: prioritise observable faults over pixel hunting · documentation exercise
Method note for “QC checklist: prioritise observable faults over pixel hunting”: use “Explain what the full-size image shows, what the crop adds 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. Distinguish an original record from a proposed record format.
Case 27 — Forum comparison archive: link the evidence and the correction
A comparison has been corrected after a new photograph arrived. How should the original thread remain useful?
Exercise RWF-27693/27: address this question within its stated limits.
Case 22 — 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.
Separate three properties: click count (60 or 120 positions), feel (how firm each click is, and whether there's back-play), and alignment (whether the pip lines up with the 12 o'clock marker at rest). Crisp vs mushy is mostly about feel and back-play. Alignment can be measured, so treat it separately.
Case 35 — Disputed observation: is this dial colour shift real or just lighting?
Suggested protocol. 1) Both dials in one frame. 2) Diffuse daylight, no direct sun, plus a second shot under neutral indoor light. 3) Grey card visible. 4) No filters, no editing. 5) State camera settings if known. If both shots show the same direction of difference, the claim is supported. If the difference flips between lighting conditions, it's most likely lighting.
Case 40 — 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.
Method note for “Comparing dial colour under different lighting”: use “State the lighting 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 32 — Lug-to-lug and end-link overhang in wrist photographs
Correction note for “Lug-to-lug and end-link overhang in wrist photographs”: retain the wording beginning “Record lug-to-lug and the effective span…” 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.
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.
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.
Case 28 — Service enquiry: information a watchmaker can use
Correction note for “Service enquiry: information a watchmaker can use”: retain the wording beginning “Document when it stops, winding behaviour, recent impacts and…” 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 38 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me? · source wording exercise
Summary draft for “Timegrapher reading context: what do rate, amplitude and beat error actually tell me?”: the answer addresses “Without those fields, the rate, amplitude and beat-error values lack…”; the related point is “Can the same settings and winding state be…”. 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.