Case 123 — QC checklist: prioritise observable faults over pixel hunting · documentation exercise
Limit of the answer in “QC checklist: prioritise observable faults over pixel hunting”: “Explain what the full-size image shows, what the crop adds 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: documentation. Distinguish an original record from a proposed record format.
Case 27 — Forum comparison archive: link the evidence and the correction
Add a dated correction near the original conclusion and link the new evidence. Preserve the reasoning trail instead of silently replacing an uncertain claim with a confident one.
Case 22 — Forum comparison archive: link the evidence and the correction
Method note for “Forum comparison archive: link the evidence and the correction”: use “Add a dated correction near the original conclusion…” 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.
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.
Back-play is the most objective feel measurement. Set the bezel on a click and gently push it the other way without forcing it. Noticeable wobble before it engages means play. A little is common and within normal production, but if one model has visible movement and the other doesn't, that's a real difference you can describe.
Case 35 — Disputed observation: is this dial colour shift real or just lighting?
Something to keep apart: sunburst and gradient dials can look like different colours depending on viewing angle, even on the same piece. A shift that appears only at certain angles is a finish effect, not a batch difference. Include a straight-on shot and one tilted shot so readers can tell the two apart.
Case 40 — Case finishing: distinguish a reflection from a surface mark · source wording exercise
Summary draft for “Case finishing: distinguish a reflection from a surface mark”: the answer addresses “A mark should be assessed across multiple views; aggressive polishing…”; the related point is “Ask for photographs with the light moved and…”. 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.
Limit of the answer in “Comparing dial colour under different lighting”: “State the lighting 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.
Case 32 — Lug-to-lug and end-link overhang in wrist photographs
Summary draft for “Lug-to-lug and end-link overhang in wrist photographs”: the answer addresses “Record lug-to-lug and the effective span…”; the related point is “Use a similar camera distance and neutral wrist position; photographs support…”. 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.
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 28 — Service enquiry: information a watchmaker can use
Summary draft for “Service enquiry: information a watchmaker can use”: the answer addresses “Document when it stops, winding behaviour, recent impacts and…”; the related point is “Be honest about the watch and request an assessment…”. 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 38 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me? · source wording exercise
Reader check for “Timegrapher reading context: what do rate, amplitude and beat error actually tell me?”: distinguish the discussion point “Without those fields, the rate, amplitude and beat-error values lack…” 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.
Case 23 — First QC request: the minimum useful information
Correction note for “First QC request: the minimum useful information”: retain the wording beginning “State the model configuration, the specific concern 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.
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 7 — Magnetism and rate: record evidence before naming a cause
A sudden rate change is being attributed to magnetism without a measurement. How should the discussion be structured?
Exercise RWF-10501/7: address this question within its stated limits.