Case 15 — Forum comparison archive: link the evidence and the correction
Add a dated correction near the original conclusion and link the new evidence. Preserve the reasoning trail instead of silently replacing an uncertain claim with a confident one.
Case 12 — Seller review template: facts, dates and unresolved questions
What belongs in a useful review template when no actual purchase experience is being asserted?
Exercise RWF-29065/12: address this question within its stated limits.
Case 15 — A maintenance log that remains useful after a sale
Summary draft for “A maintenance log that remains useful after a sale”: the answer addresses “Keep the date, work performed, provider invoice reference…”; the related point is “Redact addresses and payment information; do not invent service…”. 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 — Lume comparison: keep exposure and charging conditions consistent
Summary draft for “Lume comparison: keep exposure and charging conditions consistent”: the answer addresses “Treat the comparison…”; the related point is “Repeat with equal light source, charging duration, elapsed time and camera…”. 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 195 — Forum comparison archive: link the evidence and the correction · correction exercise
A comparison has been corrected after a new photograph arrived. How should the original thread remain useful?
Review focus: correction. Preserve the old wording if a later source changes the interpretation. Use the original answer fragment “Preserve the reasoning trail instead of silently replacing an…” as the discussion anchor; no new event or result is supplied.
Exercise RWF-25905/195: address this question within its stated limits.
Method note for “Shipping timeline: separate dispatch, handover and scan events”: use “Ask the sender or carrier for clarification; missing scans alone…” 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 — Forum comparison archive: link the evidence and the correction
Correction note for “Forum comparison archive: link the evidence and the correction”: retain the wording beginning “Add a dated correction near the original conclusion…” 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 12 — Maintenance question: how do I tell if an automatic actually needs service?
Common advice says service every five years, but service is expensive and some people run watches much longer. What observable signs actually indicate a mechanical watch needs attention, as opposed to just being due on a calendar?
Exercise RWF-21954/12: address this question within its stated limits.
Case 30 — 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.
Case 16 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
The reported numbers alone do not establish damage or the need for service. Confirm the setup, collect comparable readings and ask a watchmaker to assess a concerning or changing pattern.
Case 45 — Lug-to-lug and end-link overhang in wrist photographs · source wording exercise
Reader check for “Lug-to-lug and end-link overhang in wrist photographs”: distinguish the discussion point “Use a similar camera distance and neutral wrist position; photographs support…” 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: source wording. Retain the source wording beside any paraphrase.
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.
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.
Case 18 — 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.
Case 4 — 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.