How can a reference thread stay useful when product information changes?
Reply scope: address the opening question, explain the supporting record or reasoning, and state the limit of the answer.
Link to the issuing organisation, note the document version and access date, and record later corrections. Do not present an archived extract as current advice for an individual.
Clarification for “Official information: save the version and access date”: the point beginning “Link to the issuing organisation, note the document version 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.
Limit of the answer in “Official information: save the version and access date”: “Link to the issuing organisation, note the document version 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.
Method note for “Official information: save the version and access date”: use “Link to the issuing organisation, note the document version 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.
Correction note for “Official information: save the version and access date”: retain the wording beginning “Link to the issuing organisation, note the document version 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.