Reader check for “First QC request: the minimum useful information”: distinguish the discussion point “State the model configuration, the specific concern and…” 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.
Forum Replies Created
Case 35 — A maintenance log that remains useful after a sale
Keep the date, work performed, provider invoice reference and test results where available. Redact addresses and payment information; do not invent service events to fill an empty history.
Case 41 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me? · source wording exercise
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.
Review focus: source wording. Retain the source wording beside any paraphrase. Use the original answer fragment “Without those fields, the rate, amplitude and beat-error values lack…” as the discussion anchor; no new event or result is supplied.
Exercise RWF-26999/41: address this question within its stated limits.
Case 82 — Clasp photographs: what to request before judging alignment · comparison exercise
Correction note for “Clasp photographs: what to request before judging alignment”: retain the wording beginning “Request open and closed views from both sides,…” 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. Make the basis of a comparison explicit before interpreting it.
Case 5 — QC photographs: perspective or a genuinely tilted index?
Limit of the answer in “QC photographs: perspective or a genuinely tilted index?”: “Request a level straight-on image with the hands…” 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.
Correction note for “Crown operation: when a forum cannot diagnose the resistance”: retain the wording beginning “Describe whether resistance occurs during winding or setting 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 13 — Disputed observation: is this dial colour shift real or just lighting?
Status for now: unresolved. The claim is plausible, but no controlled comparison has been posted. Until one appears, describe it as 'reported, not verified'. When someone posts a same-frame, grey-card comparison under two lighting conditions, the thread can update the status with a date and a link to that post.
Case 10 — Magnetism and rate: record evidence before naming a cause
Correction note for “Magnetism and rate: record evidence before naming a cause”: retain the wording beginning “Record the change and the circumstances without treating…” 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 “Date window centring: compare the same date at the same angle”: the point beginning “Keep the uncropped originals alongside the detail crops and distinguish…” 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.
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. Retain the source wording beside any paraphrase.
Case 1 — 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.
Method note for “Service enquiry: information a watchmaker can use”: use “Be honest about the watch and request an assessment…” 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.
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.
Case 44 — Service enquiry: information a watchmaker can use · source wording exercise
Clarification for “Service enquiry: information a watchmaker can use”: the point beginning “Be honest about the watch and request an assessment…” 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: source wording. Retain the source wording beside any paraphrase.