Case 39 — QC photographs: perspective or a genuinely tilted index? · source wording exercise
Method note for “QC photographs: perspective or a genuinely tilted index?”: use “Compare two independently aligned images before drawing a conclusion; an overlay…” 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.
Limit of the answer in “Date window centring: compare the same date at the same angle”: “Keep the uncropped originals alongside the detail crops and distinguish…” 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 21 — First QC request: the minimum useful information
State the model configuration, the specific concern and links to clear redacted images. Include complete instrument settings where relevant and say explicitly what evidence is missing.
Case 17 — Seller review template: facts, dates and unresolved questions
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.
Reader check for “QC checklist: prioritise observable faults over pixel hunting”: distinguish the discussion point “Start with function, legibility, assembly and…” 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.
Case 41 — Crystal types: sapphire, mineral and acrylic trade-offs for daily wear · source wording exercise
Correction note for “Crystal types: sapphire, mineral and acrylic trade-offs for daily wear”: retain the wording beginning “Sapphire is very hard to scratch but can chip or crack…” 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 29 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
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 49 — A maintenance log that remains useful after a sale · source wording exercise
Which information should a transferable maintenance log retain while protecting the owner’s identity?
Review focus: source wording. Retain the source wording beside any paraphrase. Use the original answer fragment “Redact addresses and payment information; do not invent service…” as the discussion anchor; no new event or result is supplied.
Exercise RWF-15212/49: address this question within its stated limits.
Case 18 — Lume comparison: keep exposure and charging conditions consistent
Treat the comparison as inconclusive. Repeat with equal light source, charging duration, elapsed time and camera settings; disclose conditions rather than assigning an unsupported quality score.
On anti-reflective coatings: inner-surface AR cuts glare without wear concerns. Outer-surface AR improves legibility further but can scuff over time, and the scuffs show up as hazy patches in certain light. When comparing two watches, check which surfaces are coated. Spec sheets often just say 'AR coated' without saying where.
Case 10 — 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.
State the model configuration, the specific concern and links to clear redacted images. Include complete instrument settings where relevant and say explicitly what evidence is missing.
Case 16 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
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.
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.
Case 19 — 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.