Summary draft for “Reading a timegrapher recording without losing the context”: the answer addresses “Keep the complete recording and ask for the…”; the related point is “A single number cannot establish service condition, movement identity…”. 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.
Forum Replies Created
Clarification for “Case finishing: distinguish a reflection from a surface mark”: the point beginning “Ask for photographs with the light moved 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.
Method note for “First QC request: the minimum useful information”: use “Include complete instrument settings where relevant and say…” 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 24 — Shipping timeline: separate dispatch, handover and scan events
Method note for “Shipping timeline: separate dispatch, handover and scan events”: use “Distinguish label creation from physical acceptance and retain dated…” 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 “Lume comparison: keep exposure and charging conditions consistent”: the point beginning “Repeat with equal light source, charging duration, elapsed time and camera…” 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 11 — Crown operation: when a forum cannot diagnose the resistance
Correction note for “Crown operation: when a forum cannot diagnose the resistance”: retain the wording beginning “Describe whether resistance occurs during winding or setting 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.
Case 29 — Magnetism and rate: record evidence before naming a cause
Clarification for “Magnetism and rate: record evidence before naming a cause”: the point beginning “Record the change and the circumstances without treating…” 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 23 — A maintenance log that remains useful after a sale
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.
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.
Case 26 — Comparing versions without mixing case sizes
Clarification for “Comparing versions without mixing case sizes”: the point beginning “Match reference, dimensions 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.
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 14 — Crown operation: when a forum cannot diagnose the resistance
Describe whether resistance occurs during winding or setting and whether the crown engages consistently. Stop forcing it and arrange inspection rather than trying an unverified repair from a thread.
Clarification for “Shipping timeline: separate dispatch, handover and scan events”: the point beginning “Distinguish label creation from physical acceptance and retain dated…” 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 92 — Lume comparison: keep exposure and charging conditions consistent · comparison exercise
Limit of the answer in “Lume comparison: keep exposure and charging conditions consistent”: “Treat the comparison…” 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: comparison. Make the basis of a comparison explicit before interpreting it.
Clarification for “Movement identification: the limits of a rotor photograph”: the point beginning “Ask a qualified watchmaker to inspect it if identification matters for…” 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.