Case 5 — Lume questions: why does my lume fade so quickly, and how should I compare it?
Lume photos are close to useless for comparison unless exposure is fixed. Phones raise exposure automatically in the dark, so a dim watch can look as bright as a strong one. For a fair photo comparison: same charge method, same delay after charging, manual exposure, and both watches in the same frame.
Case 4 — Date window centring: compare the same date at the same angle
Summary draft for “Date window centring: compare the same date at the same angle”: the answer addresses “Use the same numeral, camera axis…”; the related point is “Keep the uncropped originals alongside the detail crops and distinguish…”. 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.
Thickness matters more than people expect. Straps around 4 to 5mm at the lugs can hit the case or stop the strap folding down on watches with short lugs or tight lug-to-case clearance. Do you know whether your watch has drilled lugs or a tight gap between strap and case? That tells you how much thickness is safe.
Case 7 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
The lift angle must match the movement specification for the amplitude reading to be meaningful. If it is unknown, label amplitude as provisional instead of accepting the instrument default.
Ask a qualified watchmaker about a suitable test for that individual case and record the test date and method. A photograph or a caseback engraving is not proof of water resistance.
Case 42 — QC checklist: prioritise observable faults over pixel hunting · source wording exercise
Correction note for “QC checklist: prioritise observable faults over pixel hunting”: retain the wording beginning “Explain what the full-size image shows, what the crop adds 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. Retain the source wording beside any paraphrase.
Case 22 — Reading a timegrapher recording without losing the context
Method note for “Reading a timegrapher recording without losing the context”: use “Keep the complete recording and ask for the…” 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 “Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?”: the answer addresses “Start with how you…”; the related point is “Comparing against a phone clock once a day for a week,…”. 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 47 — QC photographs: perspective or a genuinely tilted index? · source wording exercise
Clarification for “QC photographs: perspective or a genuinely tilted index?”: the point beginning “Compare two independently aligned images before drawing a conclusion; an overlay…” 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: source wording. Retain the source wording beside any paraphrase.
Case 21 — Model comparison: dive bezel action and alignment, how to compare fairly
Correction to earlier posts in similar threads: 120-click bezels aren't automatically worse. More positions means smaller steps, which can feel less pronounced. Comparing a 60-click and a 120-click bezel on crispness alone is apples to oranges. Compare same-click-count designs, or note the difference clearly.
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 5 — 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.
Case 19 — Crystal reflections: why a dark patch is not a coating test
No single lighting setup settles that question. Compare multiple controlled angles and describe the visible observation without asserting material specifications that have not been verified.
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.
Clarification for “Packing photographs: document condition without exposing an address”: the point beginning “Photograph the item and protective packing…” 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.