Case 16 — Lume questions: why does my lume fade so quickly, and how should I compare it?
A bright initial glow followed by a steep drop is normal for photoluminescent pigments. Afterglow fades fastest in the first minutes and then settles to a dim, long-lasting level that dark-adapted eyes can still read. The real question is whether it's readable after an hour in darkness, not how it looks right after charging.
Use a correction row with date, old value, revised value and evidence. A worked example could change a lug-width entry from 20 to 22 mm; do not present that example as a correction to a real model.
Before the table goes live, a question: are you comparing current production only, or older references too? Dial printing, lume colour and crown signing often changed between batches. If older pieces are in scope, add a production-period column, or every disagreement will look like an error when it's really a running change.
Case 48 — Crown operation: when a forum cannot diagnose the resistance · source wording exercise
Correction note for “Crown operation: when a forum cannot diagnose the resistance”: retain the wording beginning “Stop forcing it and arrange inspection rather than trying…” 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 48 — Magnetism and rate: record evidence before naming a cause · source wording exercise
Summary draft for “Magnetism and rate: record evidence before naming a cause”: the answer addresses “A competent watchmaker can test and diagnose it; random adjustment…”; the related point is “Record the change and the circumstances without treating…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: source wording. Retain the source wording beside any paraphrase.
Case 22 — Model comparison: dive bezel action and alignment, how to compare fairly
Summary table proposal: click count, back-play (none, slight, noticeable), click consistency around the rotation, and alignment (straight-on photo, offset in fractions of a click). With that, the thread can compare actual properties instead of trading adjectives. Dated corrections welcome below.
Clarification for “Date window centring: compare the same date at the same angle”: the point beginning “Use the same numeral, camera axis…” 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 44 — First QC request: the minimum useful information · source wording exercise
Limit of the answer in “First QC request: the minimum useful information”: “Include complete instrument settings where relevant and say…” 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: source wording. Retain the source wording beside any paraphrase.
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.
Method note for “Lume comparison: keep exposure and charging conditions consistent”: use “Treat the comparison…” 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 “Timegrapher reading context: what do rate, amplitude and beat error actually tell me?”: use “Without those fields, the rate, amplitude and beat-error values lack…” 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.
Record the change and the circumstances without treating the suspected cause as established. A competent watchmaker can test and diagnose it; random adjustment is not a substitute for assessment.
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.
Reader check for “Lume comparison: keep exposure and charging conditions consistent”: distinguish the discussion point “Treat the comparison…” 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.
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.