Claim-level evidence attaches support to an individual assertion rather than to a document as a whole. A consequential assertion has an identifiable subject, a stated property or relationship, a value, and a scope within which it applies. Its evidence record explains how that assertion was obtained and reviewed.
A source list at the end of an assessment helps locate background material. It does not by itself reveal which passage supports a support date, compatibility claim, cost estimate, or recommendation. Those connections need to be recoverable when the decision is challenged.
Separate observation from inference
A vendor can state that a product supports a feature. A local test can demonstrate that feature under a particular configuration. An assessment can infer that the feature makes a migration path worth investigating. These are different assertions with different evidence requirements.
Attribution establishes who made a claim. It does not turn a performance promise into a measured deployment outcome. A case report likewise describes its own population, conditions, and measurement period rather than establishing a universal result.
Hypothetical examples should identify themselves as constructed. Their purpose is to explain a mechanism or calculation, not to borrow credibility from an event that never occurred.
Make the assertion addressable
An evidence record can give each consequential assertion an identifier and attach its source, inspected passage, product version, environment, and applicable dates. This is an editorial design for inspectable decisions, not a requirement to use a particular database.
W3C PROV-O supplies concepts for entities, activities, agents, attribution, and derivation. Those concepts can represent how a claim was produced or revised. A provenance graph records that history without certifying the truth of the underlying sources.
The useful test is whether a reviewer can move from a recommendation to the claims it depends on and then to the actual supporting material. A graph that stores only document titles leaves much of that work unresolved.
Different dates answer different questions
An event date states when something happened. An effective date states when a condition applies. A publication or update date describes the source, while retrieval records access and substantive verification records review.
Retrieving an old lifecycle page today does not make its product scope current. A page can also change without its most relevant claim changing. The record should preserve these distinctions instead of replacing every date with the latest access time.
Version-specific claims need version-specific scope. A statement about one connector release or operating-system architecture should not become a category-wide compatibility rule when summarized elsewhere.
Preserve disagreement and correction
Conflicting evidence should remain visible until resolved. Deleting an earlier assertion without its correction history can make a decision appear to have used knowledge that became available only later.
A superseding claim should identify what changed and which recommendations depended on the earlier version. Corrections then have an actionable scope: affected articles, assessments, exports, or planned migration paths can be reviewed.
Confidence should explain its basis. Agreement between copied secondary accounts is different from independent testing, even when both produce several apparently consistent references.
Review follows volatility and consequence
Lifecycle claims, commercial terms, and platform limits can need different review schedules from stable definitions. W3C’s data-publication guidance supports making update frequency explicit; the actual schedule remains a decision for the corpus and its users.
A working link establishes availability, not unchanged meaning. Review requires rereading material passages and recording substantive corrections. Evidence maintenance succeeds when stale, disputed, or superseded claims produce visible work before dependent decisions continue to treat them as current.