Case 1 — 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.
Case 34 — A maintenance log that remains useful after a sale
Clarification for “A maintenance log that remains useful after a sale”: the point beginning “Keep the date, work performed, provider invoice reference…” 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 19 — Crystal types: sapphire, mineral and acrylic trade-offs for daily wear
The core trade-off is scratch resistance versus shatter resistance. Sapphire is very hard to scratch but can chip or crack from a sharp impact on an edge. Acrylic scratches easily but flexes, rarely shatters, and light scratches can be polished out at home. Mineral glass sits in between and is often the cheapest to replace.
Case 39 — 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-22861/39: address this question within its stated limits.
Case 10 — A maintenance log that remains useful after a sale
Limit of the answer in “A maintenance log that remains useful after a sale”: “Keep the date, work performed, provider invoice reference…” 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.
Clarifying question: how are you charging it? A few seconds under a warm indoor bulb gives a much weaker charge than daylight or a UV source. Many 'weak lume' reports turn out to be undercharging. Try a consistent charge, such as 30 seconds under a phone flashlight at a fixed distance, before judging.
Case 20 — Bracelet fit: measuring the usable clasp adjustment
Correction note for “Bracelet fit: measuring the usable clasp adjustment”: retain the wording beginning “Record wrist circumference, removable links and the clasp…” 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 2 — Disputed observation: is this dial colour shift real or just lighting?
Suggested protocol. 1) Both dials in one frame. 2) Diffuse daylight, no direct sun, plus a second shot under neutral indoor light. 3) Grey card visible. 4) No filters, no editing. 5) State camera settings if known. If both shots show the same direction of difference, the claim is supported. If the difference flips between lighting conditions, it's most likely lighting.
Clarification for “First QC request: the minimum useful information”: the point beginning “State the model configuration, the specific concern 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 2 — Clasp photographs: what to request before judging alignment
Summary draft for “Clasp photographs: what to request before judging alignment”: the answer addresses “Request open and closed views from both sides,…”; the related point is “Separate cosmetic alignment from whether the clasp engages reliably;…”. 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 22 — QC checklist: prioritise observable faults over pixel hunting
Start with function, legibility, assembly and clear visible damage. Explain what the full-size image shows, what the crop adds and what remains uncertain; do not turn an overlay into an automatic verdict.
A bright initial glow followed by a steep drop is normal for photoluminescent pigments. Afterglow fades fastest in the first minutes and then settles to a dim, long-lasting level that dark-adapted eyes can still read. The real question is whether it's readable after an hour in darkness, not how it looks right after charging.
Clarification for “Comparing versions without mixing case sizes”: the point beginning “Match reference, dimensions 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.
Summary draft for “Case finishing: distinguish a reflection from a surface mark”: the answer addresses “Ask for photographs with the light moved and…”; the related point is “A mark should be assessed across multiple views; aggressive polishing…”. 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.
A dated note in the frame can support a claim that photographs are recent, but it is not conclusive proof of ownership, authenticity or an honest transaction. Treat it as one limited check alongside independent verification.