Check reference

Keep derived trace links current

autolink_clean reports problems while deriving trace links from source annotations. A clean scan gives later checks a usable graph of the claims present in the repository.

What the check observes

Proof scans recognized annotations and derives effective source-backed trace state without rewriting the authored requirement YAML. Malformed references, invalid scan configuration, or an unavailable source analysis tool can prevent that refresh. The result matters because downstream checks may otherwise inspect incomplete or old links. The scan records what source claims to implement or verify; it does not infer a complete specification from arbitrary code.

Example: the scanner cannot inspect a language

Illustrative case. A CI image lacks the managed Probe tool and disables downloads. The scan cannot enumerate the configured source population. Treat this as missing analysis capability, not as evidence that the project has no trace gaps.

# Refresh source-backed trace state
proof trace autolink

# Inspect the focused audit result
proof audit --check autolink_clean --verbose

Resolve the finding

Read the first scan error and identify whether it is a malformed annotation, a path configuration problem, or a missing tool.
Correct the annotation or scan scope. If a managed tool is unavailable, provision the pinned tool in the execution environment or follow the project's permitted download policy.
Refresh the trace state again, then rerun the downstream checks that relied on it. Retain the original failure if the source population still cannot be inspected.

Run and interpret

proof audit --check autolink_clean --verbose

This implementation-stage check defaults to warning severity. Run from the configured project root. Tool acquisition can be disabled by project settings, the no-download option, or environment policy. A focused audit is diagnostic; it is not the full project gate.

Successful autolinking means the scan completed under its configured scope. It does not show that every function is traced, that the requirement IDs describe the right behavior, or that linked tests passed. Those questions require annotation, orphan, review, and execution checks.

Continue from here

Validate annotation claims. Inspect code without requirement ownership.

Bring one broken source-to-requirement link and the environment that fails to resolve it. Bring a change to Proof.