Case 28 — Seller review template: facts, dates and unresolved questions
Use fields for order date, promised terms, dated communications, delivery evidence and resolution. Leave unsupported fields blank and separate observations from opinions; this reference is not a seller endorsement.
Case 44 — Bracelet fit: half-links, micro-adjust holes and the 'between sizes' problem · source wording exercise
Reader check for “Bracelet fit: half-links, micro-adjust holes and the 'between sizes' problem”: distinguish the discussion point “Fit often improves by moving one link from the 6 o'clock…” 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.
Ask for profile shots of both case sides and a lug-top shot at an angle. Polishing shows as rounded edges, softened bevels or lug holes that look shallower than they should. Compare against a known-good reference image of the same model, not memory. A side-by-side tells you far more than a description.
Case 22 — 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-24807/22: address this question within its stated limits.
Method note for “Movement identification: the limits of a rotor photograph”: use “Describe visible bridge shapes and markings separately…” 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.
Method note for “Model comparison: dive bezel action and alignment, how to compare fairly”: use “Separate three properties: click count (60 or 120 positions), feel (how…” 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.
Summary draft for “Forum comparison archive: link the evidence and the correction”: the answer addresses “Add a dated correction near the original conclusion…”; the related point is “Preserve the reasoning trail instead of silently replacing an…”. 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.
Method note for “Movement identification: the limits of a rotor photograph”: use “Describe visible bridge shapes and markings separately…” 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 19 — 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.
Case 24 — Crown operation: when a forum cannot diagnose the resistance
Summary draft for “Crown operation: when a forum cannot diagnose the resistance”: the answer addresses “Describe whether resistance occurs during winding or setting and…”; the related point is “Stop forcing it and arrange inspection rather than trying…”. 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.
Use fields for order date, promised terms, dated communications, delivery evidence and resolution. Leave unsupported fields blank and separate observations from opinions; this reference is not a seller endorsement.
Case 40 — Strap compatibility: width is only the first measurement · source wording exercise
Method note for “Strap compatibility: width is only the first measurement”: use “Avoid forcing an assembly that does not fit 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 12 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?
Start with how you measured it. Comparing against a phone clock once a day for a week, at the same time, and noting the offset is reliable enough. One 24-hour reading isn't, because rate depends on wrist time, position overnight and state of wind. Average across several days before deciding anything.
Clarification for “Lume comparison: keep exposure and charging conditions consistent”: the point beginning “Treat the comparison…” 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.
Correction note for “Crown operation: when a forum cannot diagnose the resistance”: retain the wording beginning “Describe whether resistance occurs during winding or setting and…” 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.