Case 32 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?
Log the rate over several comparable days, identify the correct specification and state the conditions. Stable and changing patterns raise different questions; a watchmaker can assess whether regulation, inspection or no action is appropriate.
Method note for “Date window centring: compare the same date at the same angle”: use “Use the same numeral, camera axis…” 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.
Method note for “QC checklist: prioritise observable faults over pixel hunting”: use “Start with function, legibility, assembly 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.
Correction note for “Forum comparison archive: link the evidence and the correction”: retain the wording beginning “Preserve the reasoning trail instead of silently replacing an…” 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 66 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic? · source wording exercise
Reader check for “Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?”: distinguish the discussion point “Comparing against a phone clock once a day for a week,…” 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.
Case 251 — Service enquiry: information a watchmaker can use · indexing exercise
Method note for “Service enquiry: information a watchmaker can use”: use “Document when it stops, winding behaviour, recent impacts 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. Make the reasoning findable without reducing it to a trust score.
Case 37 — Service enquiry: information a watchmaker can use · source wording exercise
Correction note for “Service enquiry: information a watchmaker can use”: retain the wording beginning “Be honest about the watch and request an assessment…” 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. Retain the source wording beside any paraphrase.
Case 23 — Maintenance question: how do I tell if an automatic actually needs service?
A sudden rate change has several possible causes. Ask a watchmaker to test suspected magnetism rather than diagnosing it from a compass or attempting an adjustment based on forum replies.
Case 15 — Date window centring: compare the same date at the same angle
Method note for “Date window centring: compare the same date at the same angle”: use “Use the same numeral, camera axis…” 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.
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 2 — Seller review template: facts, dates and unresolved questions
Summary draft for “Seller review template: facts, dates and unresolved questions”: the answer addresses “Use fields for order date, promised terms, dated…”; the related point is “Leave unsupported fields blank and separate observations from opinions; this…”. 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 25 — 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 14 — Comparing versions without mixing case sizes
Summary draft for “Comparing versions without mixing case sizes”: the answer addresses “Match reference, dimensions and…”; the related point is “List confirmed differences separately from seller descriptions and date the comparison…”. 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.
State the lighting and white-balance limitations. Compare controlled images where available and avoid calling a colour defect from differently processed photographs.
Case 25 — Lug-to-lug and end-link overhang in wrist photographs
Method note for “Lug-to-lug and end-link overhang in wrist photographs”: use “Record lug-to-lug and the effective span…” 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.