Case 18 — Comparing dial colour under different lighting
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 32 — Forum comparison archive: link the evidence and the correction
A comparison has been corrected after a new photograph arrived. How should the original thread remain useful?
Exercise RWF-29092/32: address this question within its stated limits.
Case 105 — Reading a timegrapher recording without losing the context · comparison exercise
Reader check for “Reading a timegrapher recording without losing the context”: distinguish the discussion point “Keep the complete recording and ask for the…” 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: comparison. Make the basis of a comparison explicit before interpreting it.
Summary draft for “Seller review template: facts, dates and unresolved questions”: the answer addresses “Use fields for order date, promised terms, dated…”; the related point is “Leave unsupported fields blank and separate observations from opinions; this…”. 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 4 — Beginner glossary Q&A: complication, caliber, jewel count, power reserve
Jewel count describes bearings used in a movement design; it is not a quality ranking. Compare the documented movement architecture and service support rather than assuming a higher count makes one watch better.
Correction note for “Shipping timeline: separate dispatch, handover and scan events”: retain the wording beginning “Ask the sender or carrier for clarification; missing scans alone…” 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 “QC checklist: prioritise observable faults over pixel hunting”: the point beginning “Start with function, legibility, assembly 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 21 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?
Regulation is possible if you want it closer. On many movements it's a quick adjustment by a watchmaker. Can you check whether the losing rate is consistent or getting worse? A stable -8 is a good candidate for simple regulation. A growing loss points to something else, such as falling amplitude, and regulation alone won't fix that.
Case 22 — Strap compatibility: width is only the first measurement
Summary draft for “Strap compatibility: width is only the first measurement”: the answer addresses “Measure the lug opening and document bar diameter,…”; the related point is “Avoid forcing an assembly that does not fit and…”. 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.
One method that often helps without any service is using overnight resting position to cancel daily drift. Many watches gain in some positions and lose in others. If yours loses on the wrist, try leaving it crown up or dial up overnight and log the result for a few nights. Some people get close to zero this way.
Case 20 — Clasp photographs: what to request before judging alignment
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: scope. Keep the stated question separate from any broader claim.
Summary draft for “Disputed observation: is this dial colour shift real or just lighting?”: the answer addresses “The difficulty is that phone cameras adjust white balance automatically,…”; the related point is “Two photos of the same dial under different light can…”. 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 48 — Crystal reflections: why a dark patch is not a coating test · source wording exercise
A dark area appears at an oblique angle in a single photograph. Does that establish a coating difference?
Review focus: source wording. Retain the source wording beside any paraphrase. Use the original answer fragment “Compare multiple controlled angles and describe the visible observation without asserting…” as the discussion anchor; no new event or result is supplied.
Exercise RWF-16079/48: address this question within its stated limits.
Case 7 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
A useful table has columns for date, position, winding state, lift angle, rate, amplitude and beat error. Keep the full recording so settings and stability can be checked.
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.