Clarification for “A maintenance log that remains useful after a sale”: the point beginning “Redact addresses and payment information; do not invent service…” 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.
Forum Replies Created
Case 12 — Packing photographs: document condition without exposing an address
Clarification for “Packing photographs: document condition without exposing an address”: the point beginning “Photograph the item and protective packing…” 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 16 — QC photography: what photos actually help verify a pre-owned listing?
When asking a seller for extra photos of a pre-owned watch, what shots are actually useful as evidence? Listings tend to have glossy angled photos that hide more than they show. I'd like a standard request list the forum can reuse.
Exercise RWF-29941/16: address this question within its stated limits.
Limit of the answer in “Lume comparison: keep exposure and charging conditions consistent”: “Repeat with equal light source, charging duration, elapsed time and camera…” 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 4 — Comparing versions without mixing case sizes
Summary draft for “Comparing versions without mixing case sizes”: the answer addresses “Match reference, dimensions and…”; the related point is “List confirmed differences separately from seller descriptions and date the comparison…”. 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.
Wrist size changes during the day and with temperature, sometimes by several millimetres. A fit that feels tight in the afternoon may be right in the morning. Before buying parts, check the fit at different times. You may find the 'too tight' setting is only a problem a few hours a day.
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 10 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
The lift angle must match the movement specification for the amplitude reading to be meaningful. If it is unknown, label amplitude as provisional instead of accepting the instrument default.
Case 4 — Reading a timegrapher recording without losing the context
Method note for “Reading a timegrapher recording without losing the context”: use “Keep the complete recording and ask for the…” 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.
Summary draft for “Comparing dial colour under different lighting”: the answer addresses “State the lighting and…”; the related point is “Compare controlled images where available and avoid calling a…”. 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 27 — Model comparison: dive bezel action and alignment, how to compare fairly
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.
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.
Case 13 — Lume comparison: keep exposure and charging conditions consistent
Treat the comparison as inconclusive. Repeat with equal light source, charging duration, elapsed time and camera settings; disclose conditions rather than assigning an unsupported quality score.
Case 23 — Forum comparison archive: link the evidence and the correction
Summary draft for “Forum comparison archive: link the evidence and the correction”: the answer addresses “Add a dated correction near the original conclusion…”; the related point is “Preserve the reasoning trail instead of silently replacing an…”. 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 51 — Magnetism and rate: record evidence before naming a cause · source wording exercise
Limit of the answer in “Magnetism and rate: record evidence before naming a cause”: “A competent watchmaker can test and diagnose it; random adjustment…” 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.