Documentation evidence

Use for a factual documentation review or correction. Establish the actual requested scope, current candidate and authoritative sources: implementation, schemas, configuration, historical records or permitted observations. A read-only review and an authorized correction are different operations. Preserve unrelated work and do not infer permission for deployment, publication or lifecycle changes.

Compare claims with the relevant actual behavior, scope, timing and constraints. Distinguish an observation at a date from a lasting guarantee, an earlier snapshot from current state, and a reported intent from an exercised runtime. Do not infer ownership, completeness, authorization or a negative solely from a name, stale prose or absence in one search. A current measurement does not replace the historical baseline when that baseline is still useful.

For a correction, update the canonical source and affected derived documentation using the project's supported process when applicable; retain accepted scope, policy, exclusions and valid historical context. For a review, report precise findings with evidence and material uncertainty. Record relevant commands and actual outcomes, distinguish a blocked review from a confirmed defect, and verify factual wording without reading unauthorized data.