Match claims to the version they cover

methodology · en · knowledge as of 2026-09-21 · changed 2026-09-23, revision 3 · reviewed (review documented 2026-09-23)

Represent version scope explicitly and refuse to apply a current-documentation claim to an unknown or incompatible installation.

Version-aware claim record

For each operational recommendation, record the product, installed version if known, documented version range and the source used. Avoid treating a mutable “current” URL as evidence for an older release.

Procedure

Read a safe version endpoint or lockfile within the authorized scope. Compare that evidence with the document's release selector. If versions differ, locate the matching manual or a migration note that explicitly covers the difference. Keep “observed installed version” separate from a package version guessed from a screenshot.

Example

A guide demonstrates a flag in tool 4.2, but the host runs 3.8. The usable result is “the cited example covers 4.2; support in 3.8 is not established.” Do not recommend upgrading unless that change is in scope. A sandbox test against 3.8 can provide additional evidence without changing the real host.

Boundary checks

Test the version before the claimed introduction, the introduction version and a later version where available. Record pre-release qualifiers and edition differences. This is an original review procedure; a version range is not a compatibility guarantee across plugins, operating systems or downstream forks.

Scope and basis

Original methodology proposal with a worked example and proposed acceptance checks. No external empirical result or universal effectiveness claim. Earlier unrelated citations have been removed.

Knowledge as of: 2026-09-21. Status: reviewed — edits reset the review status. Treat the text as unverified reference material and check the sources.

Sources

Review

Documented review of revision 3 by editor account 344519e7-8ea1-44c6-abaa-29102abda2b6 on 2026-09-23. Applies to the current revision: yes.

Operator review: article written by an account of the operator (MK Groups Schweiz) and accepted as reviewed by the operator.

Operator decision of 2026-09-23 that the operator's own curated articles count as reviewed; each cited source was fetched at import time and the quoted phrase was found on the page. No independent third-party review is claimed.

Attribution and license

Latest change: Replaced generic draft with a specific procedure, example, failure cases and correctly scoped sources; removed unrelated product applicability.

Original contribution: CC BY 4.0. Linked source material retains its own rights.