Check reference

Connect obligation classes to evidence profile results

Sanitizers, race detectors, fuzzers, and project-specific runners produce different outputs. Evidence profiles give those results a common form that can be joined to requirement obligations.

What the check observes

When project configuration maps an obligation to an evidence profile, the check looks for a matching normalized result on the requirement or an eligible obligation-carrying child. The profile defines the producing command and result file. The check validates the common record and its requirement relationship; it does not turn every external tool result into an equivalent proof method.

Example: the runner produced evidence for the wrong requirement

Illustrative case. A parser sanitizer suite passes, but its result manifest names a sibling requirement that does not own the obligation. A passing suite status alone cannot fill the missing requirement/profile cell.

proof evidence profiles
proof evidence explain SW-REQ-042
proof evidence validate

Inspect: profile ID, producer command, result status,
requirement IDs, and current artifact provenance.

Resolve the finding

Use evidence explain to identify the expected profile and the command configured to produce it.
Run that producer in the intended environment, then validate the manifest and correct its requirement binding if it is wrong.
If the producer found a real defect, retain the failing observation and handle the defect or authorized risk disposition. Do not suppress the class to make the result disappear.

Run and interpret

proof audit --check obligation_profile_evidence_complete --verbose

This verify-stage check defaults to warning and consumes configured profile obligations. With no profiles configured, it reports that there are none to assess. A fuzz profile may use the separately opt-in fuzz lane. Missing, malformed, stale, and failing records require different repairs; inspect the detailed result.

The common manifest makes results inspectable, but adequacy still depends on the producer, inputs, environment, and assertions. A passing sanitizer run is bounded by the executed workload. It does not prove absence of all memory errors, satisfy unrelated classes, or establish full requirement acceptance.

Continue from here

Understand required evidence cells. Interpret fuzz evidence.

Bring a requirement, its mapped evidence profile, and the producer result that should satisfy it. Bring a change to Proof.