[Demo notebook] Reference notebook: corrections and recurring beginner questions · RWI-21408

Case 12 — 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.

Case 12 — Forum comparison archive: link the evidence and the correction

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.

Case 12 — Forum comparison archive: link the evidence and the correction

Limit of the answer in “Forum comparison archive: link the evidence and the correction”: “Add a dated correction near the original conclusion…” 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 12 — Forum comparison archive: link the evidence and the correction

Correction note for “Forum comparison archive: link the evidence and the correction”: retain the wording beginning “Add a dated correction near the original conclusion…” 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 12 — Forum comparison archive: link the evidence and the correction

Summary draft for “Forum comparison archive: link the evidence and the correction”: the answer addresses “Add a dated correction near the original conclusion…”; the related point is “Preserve the reasoning trail instead of silently replacing an…”. 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 13 — First QC request: the minimum useful information

What should an initial QC request include so replies can address the actual question?

Exercise RWI-21408/13: address this question within its stated limits.

Case 13 — First QC request: the minimum useful information

Clarification for “First QC request: the minimum useful information”: the point beginning “State the model configuration, the specific concern 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.

Case 13 — 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 13 — First QC request: the minimum useful information

Method note for “First QC request: the minimum useful information”: use “State the model configuration, the specific concern and…” 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 13 — First QC request: the minimum useful information

Limit of the answer in “First QC request: the minimum useful information”: “State the model configuration, the specific concern 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 13 — First QC request: the minimum useful information

Correction note for “First QC request: the minimum useful information”: retain the wording beginning “State the model configuration, the specific concern 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 13 — First QC request: the minimum useful information

Summary draft for “First QC request: the minimum useful information”: the answer addresses “State the model configuration, the specific concern and…”; the related point is “Include complete instrument settings where relevant and say…”. 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 14 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log

Add lug-to-lug, thickness and lug width as separate rows. Diameter alone tells you little about wearability. Two cases 2mm apart in diameter can be within 1mm of each other lug to lug, and that number decides whether the watch overhangs a small wrist. Also give the source for each figure: manufacturer sheet, caliper measurement, or catalogue listing.

Case 14 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log

I'm putting together a side-by-side of the 38mm and 40mm versions of a common three-hand field watch design. The aim is a reference post we can fix over time instead of repeating the same arguments. Corrections go in a dated log at the bottom. What should the table include besides case diameter, and which specs are usually misreported?

Exercise RWI-21408/14: address this question within its stated limits.

Case 14 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log

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 14 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log

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.

Case 14 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log

State whether thickness includes the highest point of a domed crystal. Different measurement methods can produce different figures, so keep both the source and method beside each dimension.

Case 14 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log

Summary so far. Rows: diameter, lug-to-lug, thickness (method stated), lug width, crystal type, water resistance (as specified), movement family, production period. Each row has a source tag. Corrections go in the dated log with old and new values. If nobody objects, that's the template, and later posts should give evidence rather than restate opinions.

Case 14 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log

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 15 — Beginner glossary Q&A: complication, caliber, jewel count, power reserve

Caliber is the movement's model designation, like a part number. Two watches from different brands can share the same caliber family with different finishing or regulation. On a spec sheet it tells you what's inside and roughly what service parts are available. It doesn't tell you how well that particular example was adjusted.