Limit of the answer in “Clasp photographs: what to request before judging alignment”: “Request open and closed views from both sides,…” 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.
Forum Replies Created
Case 34 — Movement identification: the limits of a rotor photograph
Clarification for “Movement identification: the limits of a rotor photograph”: the point beginning “Describe visible bridge shapes and markings separately…” 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 105 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic? · comparison exercise
My entry-level automatic loses about 8 seconds a day. The spec sheet lists a tolerance range, but I'm not sure how to read it or whether my measurement is reliable. Is this something to fix or something to live with?
Review focus: comparison. Make the basis of a comparison explicit before interpreting it. Use the original answer fragment “One 24-hour reading isn't, because rate depends on wrist time,…” as the discussion anchor; no new event or result is supplied.
Exercise RWF-28599/105: address this question within its stated limits.
Case 5 — QC photographs: perspective or a genuinely tilted index?
Method note for “QC photographs: perspective or a genuinely tilted index?”: use “Request a level straight-on image with the hands…” 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 “QC photographs: perspective or a genuinely tilted index?”: the answer addresses “Request a level straight-on image with the hands…”; the related point is “Compare two independently aligned images before drawing a conclusion; an overlay…”. 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.
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 36 — Seller review template: facts, dates and unresolved questions
Clarification for “Seller review template: facts, dates and unresolved questions”: the point beginning “Use fields for order date, promised terms, dated…” 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 11 — Lug-to-lug and end-link overhang in wrist photographs
A wide-angle wrist photo exaggerates the nearest edge of the case. How can two watches be compared fairly?
Exercise RWF-22474/11: address this question within its stated limits.
Case 16 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
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.
Exercise RWF-21408/16: address this question within its stated limits.
Case 25 — Beginner glossary Q&A: complication, caliber, jewel count, power reserve
One more term that will come up is 'hacking', meaning the seconds hand stops when you pull the crown so you can set the time to the second. It's minor, but beginners often assume every automatic has it, and not all do. That rounds out the glossary: caliber means what, complication means extra functions, jewels mean bearings, power reserve means how long it runs, hacking means precise setting.
Case 8 — 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.
Clarification for “Crown operation: when a forum cannot diagnose the resistance”: the point beginning “Describe whether resistance occurs during winding or setting 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.
Case 4 — Magnetism and rate: record evidence before naming a cause
Record the change and the circumstances without treating the suspected cause as established. A competent watchmaker can test and diagnose it; random adjustment is not a substitute for assessment.
Case 14 — Bracelet fit: measuring the usable clasp adjustment
Record wrist circumference, removable links and the clasp adjustment range in millimetres. Request the closed bracelet circumference rather than inferring it from marketing dimensions.
Batch variation on coloured dials does happen in general. Plating, lacquer thickness and supplier changes can all shift tone, so the claim isn't implausible. Plausible isn't the same as confirmed, though. The thread should keep 'possible' and 'shown' as separate statuses rather than letting repetition turn a hypothesis into accepted fact.