Case 6 — 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.
Forum Replies Created
Correction note for “QC checklist: prioritise observable faults over pixel hunting”: retain the wording beginning “Explain what the full-size image shows, what the crop adds 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 31 — A maintenance log that remains useful after a sale
Method note for “A maintenance log that remains useful after a sale”: use “Keep the date, work performed, provider invoice reference…” 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 8 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log
Before the table goes live, a question: are you comparing current production only, or older references too? Dial printing, lume colour and crown signing often changed between batches. If older pieces are in scope, add a production-period column, or every disagreement will look like an error when it's really a running change.
Method note for “A maintenance log that remains useful after a sale”: use “Keep the date, work performed, provider invoice reference…” 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.
Add lug-to-lug, thickness and lug width as separate rows. Diameter alone tells you little about wearability. Two cases 2mm apart in diameter can be within 1mm of each other lug to lug, and that number decides whether the watch overhangs a small wrist. Also give the source for each figure: manufacturer sheet, caliper measurement, or catalogue listing.
Case 27 — 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.
Method note for “Crystal reflections: why a dark patch is not a coating test”: use “Compare multiple controlled angles and describe the visible observation without asserting…” 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 “Lug-to-lug and end-link overhang in wrist photographs”: distinguish the discussion point “Record lug-to-lug and the effective span…” 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.
Distinguish label creation from physical acceptance and retain dated event text with personal details removed. Ask the sender or carrier for clarification; missing scans alone do not establish loss or seizure.
Reader check for “A maintenance log that remains useful after a sale”: distinguish the discussion point “Keep the date, work performed, provider invoice reference…” 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 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-10331/41: address this question within its stated limits.
Case 2 — Reading a timegrapher recording without losing the context
Clarification for “Reading a timegrapher recording without losing the context”: the point beginning “Keep the complete recording and ask for the…” 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.
Summary draft for “Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?”: the answer addresses “Start with how you…”; the related point is “Comparing against a phone clock once a day for a week,…”. 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.
Micro-adjust spacing varies by clasp. Measure the actual change at each setting rather than assuming a standard number of millimetres; compare the usable range with the link length.