Case 7 — 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.
Case 10 — What a water-resistance claim does and does not establish
Limit of the answer in “What a water-resistance claim does and does not establish”: “Ask a qualified watchmaker about a suitable test for that individual…” 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 21 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log
Use a correction row with date, old value, revised value and evidence. A worked example could change a lug-width entry from 20 to 22 mm; do not present that example as a correction to a real model.
Keep the complete recording and ask for the settings, winding state and position. A single number cannot establish service condition, movement identity or performance on a wrist.
Match reference, dimensions and configuration first. List confirmed differences separately from seller descriptions and date the comparison so later readers understand its scope.
Case 24 — Lume comparison: keep exposure and charging conditions consistent
Two glowing dials are shown with different camera exposure and unknown charging time. What can the images establish?
Exercise RWF-21599/24: address this question within its stated limits.
Case 6 — 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.
Method note for “Case finishing: distinguish a reflection from a surface mark”: use “Ask for photographs with the light moved and…” 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. Retain the source wording beside any paraphrase.
Case 3 — 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 27 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?
Compare the observed rate with the exact caliber and cased-watch specification, if available. An example such as -8 seconds per day cannot be declared acceptable solely from its price category.
Case 7 — Comparing versions without mixing case sizes
Two purported versions differ in case diameter and bracelet. How can the comparison avoid attributing every difference to a revision?
Exercise RWF-15754/7: address this question within its stated limits.
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.
Case 39 — Model comparison: dive bezel action and alignment, how to compare fairly · source wording exercise
Reader check for “Model comparison: dive bezel action and alignment, how to compare fairly”: distinguish the discussion point “Crisp vs mushy is mostly about…” 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.
A correction to a common assumption: a slightly loose fit isn't automatically wrong. Heavier heads tend to slide on loose bracelets, but a lighter watch often wears comfortably with a finger's width of space. Try 'loose' for a full day before deciding it doesn't work. Comfort over hours tells you more than the first minute.