Method note for “Crystal reflections: why a dark patch is not a coating test”: use “No single lighting setup settles…” 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.
Forum Replies Created
Micro-adjust spacing varies by clasp. Measure the actual change at each setting rather than assuming a standard number of millimetres; compare the usable range with the link length.
Case 31 — QC checklist: prioritise observable faults over pixel hunting
Correction note for “QC checklist: prioritise observable faults over pixel hunting”: retain the wording beginning “Start with function, legibility, assembly 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.
Method note for “Forum comparison archive: link the evidence and the correction”: use “Add a dated correction near the original conclusion…” 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 7 — 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.
A useful table has columns for date, position, winding state, lift angle, rate, amplitude and beat error. Keep the full recording so settings and stability can be checked.
Case 22 — 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 31 — Strap compatibility: width is only the first measurement
Measure the lug opening and document bar diameter, shoulder position and strap thickness. Avoid forcing an assembly that does not fit and let a watchmaker check uncertain clearances.
First identify the caliber, lift-angle setting, winding state and measurement position. Without those fields, the rate, amplitude and beat-error values lack enough context for a useful comparison.
Case 9 — Service enquiry: information a watchmaker can use
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. Keep the stated question separate from any broader claim.
Case 41 — Shipping timeline: separate dispatch, handover and scan events · source wording exercise
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. Retain the source wording beside any paraphrase.
Case 1 — Forum comparison archive: link the evidence and the correction
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.
Case 1 — 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 6 — Forum comparison archive: link the evidence and the correction
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.
Case 11 — Magnetism and rate: record evidence before naming a cause
Correction note for “Magnetism and rate: record evidence before naming a cause”: retain the wording beginning “Record the change and the circumstances without treating…” 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.