Check reference

Review the obligations activated by requirement tags

Requirement tags can activate a baseline of catalog obligations. obligation_baseline reports the classes that have not yet received an explicit disposition.

What the check observes

The baseline match is deterministic: a class applies when its required tag set is contained in the requirement's tags, after project profile filtering. Description similarity does not participate in this predicate. The check runs across active stakeholder, system, software, and integration requirements. A class is resolved by a checklist entry, a suppression, or a valid delegation to a requirement whose checklist carries it. Contradictory acceptance and suppression are findings.

Example: an implementation tag activates a new obligation

Illustrative case. Adding a concurrency-related tag to a software requirement may activate a matching catalog class. That does not mean the code is now verified for concurrency; it means the requirement must account for that concern.

proof catalog show concurrent
proof audit --check obligation_baseline --verbose

# Accept only after reviewing applicability
proof req edit SW-REQ-042 --add-obligation concurrent

Resolve the finding

Read the matched class, its tag predicate, and evidence expectations. Check the accuracy of the requirement tags.
Accept an applicable obligation and plan its decomposition and evidence. Delegate only when another requirement genuinely owns the same obligation.
Suppress only a non-applicable obligation with a concrete rationale. Keep applicable but unfinished work visible as debt; draft a project class if the catalog lacks the needed concern.

Run and interpret

proof audit --check obligation_baseline --verbose

The default finding severity is warning. Catalog baseline configuration can disable classes or raise effective severity, including through framework overrides. Audit defaults to a warning failure threshold unless configured otherwise.

A tag match is an applicability rule, not a complete hazard analysis. Missing or inaccurate tags can hide relevant obligations, and an accepted checklist item is not verified behavior. Review the product's risks and operating conditions beyond the catalog matches.

Continue from here

Check class definitions and references. Inspect evidence for accepted obligations.

Bring a tagged requirement and one obligation whose applicability is disputed. Bring a change to Proof.