Case 11 — Bracelet fit: measuring the usable clasp adjustment
Summary draft for “Bracelet fit: measuring the usable clasp adjustment”: the answer addresses “Record wrist circumference, removable links and the clasp…”; the related point is “Request the closed bracelet circumference rather than inferring…”. 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.
Summary draft for “First QC request: the minimum useful information”: the answer addresses “State the model configuration, the specific concern and…”; the related point is “Include complete instrument settings where relevant and say…”. 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.
Clarifying question: does anyone in the thread have access to both versions at once? Without simultaneous comparison, every claim either way is weak evidence. If not, the next best option is photos with a grey card in frame and white balance locked or set manually, which at least makes separate photos roughly comparable.
Case 22 — Bracelet fit: half-links, micro-adjust holes and the 'between sizes' problem
Resolution checklist. 1) Rebalance links around the clasp. 2) Test every micro-adjust hole with each link count. 3) Check fit morning and afternoon. 4) Look for half-links by bracelet reference. 5) Accept slightly loose if the head is light. If none of that works, a strap with finer hole spacing is a reasonable conclusion, not a failure.
Correction note for “Strap dimensions: lug width, taper, thickness and spring bar diameter explained”: retain the wording beginning “Measure with a ruler marked in millimetres, ideally…” 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 12 — First QC request: the minimum useful information
Method note for “First QC request: the minimum useful information”: use “State the model configuration, the specific concern 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. Keep the stated question separate from any broader claim.
Case 14 — Maintenance question: how do I tell if an automatic actually needs service?
If the manufacturer provides a suitable procedure, a running-time log can support a service enquiry. State the winding method and stop time. A shortened run does not identify the cause by itself.
Case 40 — What a water-resistance claim does and does not establish · source wording exercise
A listing describes a water-resistance rating but provides no test record for the individual watch. What evidence would address the gap?
Review focus: source wording. Retain the source wording beside any paraphrase. Use the original answer fragment “A photograph or a caseback engraving is not…” as the discussion anchor; no new event or result is supplied.
Exercise RWF-19490/40: address this question within its stated limits.
Case 2 — 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 30 — Reading a timegrapher recording without losing the context
Limit of the answer in “Reading a timegrapher recording without losing the context”: “Keep the complete recording and ask for the…” 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.
Method note for “Seller review template: facts, dates and unresolved questions”: use “Use fields for order date, promised terms, dated…” 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 41 — Packing photographs: document condition without exposing an address · source wording exercise
A condition record is useful but a shipping label contains personal information. How can the record be shared safely?
Review focus: source wording. Retain the source wording beside any paraphrase. Use the original answer fragment “Remove names, addresses, barcodes and tracking tokens from public…” as the discussion anchor; no new event or result is supplied.
Exercise RWF-14789/41: address this question within its stated limits.
Case 14 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log
Summary so far. Rows: diameter, lug-to-lug, thickness (method stated), lug width, crystal type, water resistance (as specified), movement family, production period. Each row has a source tag. Corrections go in the dated log with old and new values. If nobody objects, that's the template, and later posts should give evidence rather than restate opinions.
Clarification for “Date window centring: compare the same date at the same angle”: the point beginning “Use the same numeral, camera axis…” 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.