Case 4 — 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.
Case 29 — Disputed observation: is this dial colour shift real or just lighting?
Status for now: unresolved. The claim is plausible, but no controlled comparison has been posted. Until one appears, describe it as 'reported, not verified'. When someone posts a same-frame, grey-card comparison under two lighting conditions, the thread can update the status with a date and a link to that post.
Case 22 — Crystal reflections: why a dark patch is not a coating test
Correction note for “Crystal reflections: why a dark patch is not a coating test”: retain the wording beginning “No single lighting setup settles…” 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.
A stated water-resistance rating does not establish the present condition of an individual watch. Separate the manufacturer specification from a dated inspection or test of the particular example.
Case 6 — QC photography: what photos actually help verify a pre-owned listing?
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.
Reader check for “A maintenance log that remains useful after a sale”: distinguish the discussion point “Redact addresses and payment information; do not invent service…” 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: scope. Keep the stated question separate from any broader claim.
Keep the date, work performed, provider invoice reference and test results where available. Redact addresses and payment information; do not invent service events to fill an empty history.
Document spring-bar diameter, end-tip fit and the strap’s clearance using appropriate measuring tools. If dimensions or compatibility are uncertain, ask a watchmaker rather than forcing a bar or substituting an unsuitable part.
Case 9 — QC checklist: prioritise observable faults over pixel hunting
Limit of the answer in “QC checklist: prioritise observable faults over pixel hunting”: “Start with function, legibility, assembly and…” 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.
First, a clarifying question: how many links are on each side of the clasp right now? Fit often improves by moving one link from the 6 o'clock side to the 12 o'clock side, or the reverse. That doesn't change length, but it shifts where the clasp sits under the wrist, and a centred clasp feels less tight.
Summary draft for “Shipping timeline: separate dispatch, handover and scan events”: the answer addresses “Distinguish label creation from physical acceptance and retain dated…”; the related point is “Ask the sender or carrier for clarification; missing scans alone…”. 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 22 — Comparing versions without mixing case sizes
Match reference, dimensions and configuration first. List confirmed differences separately from seller descriptions and date the comparison so later readers understand its scope.
Case 23 — Disputed observation: is this dial colour shift real or just lighting?
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 15 — Service enquiry: information a watchmaker can use
Limit of the answer in “Service enquiry: information a watchmaker can use”: “Document when it stops, winding behaviour, recent impacts and…” 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 135 — QC checklist: prioritise observable faults over pixel hunting · documentation exercise
Limit of the answer in “QC checklist: prioritise observable faults over pixel hunting”: “Explain what the full-size image shows, what the crop adds and…” 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: documentation. Distinguish an original record from a proposed record format.