Allocate each stakeholder obligation to the system

What the check observes

For each eligible stakeholder guarantee, the check looks for active system requirements that satisfy it and carry its declared checklist classes. Each uncovered requirement/class pair is a finding. Terminal parents and children are excluded, and assumptions and constraints do not owe downward guarantee decomposition. A link without the relevant class cannot silently stand in for every behavior family the parent promises.

Example: the error case has no system owner

STK-REQ-042 checklist: nominal, boundary, malformed_input
  SYS-REQ-051 satisfies STK-REQ-042
  SYS-REQ-051 checklist: nominal

Unallocated: boundary, malformed_input

Resolve the finding

1. Inspect each uncovered class and the actual behavior it means for this stakeholder promise.
2. If an existing system child already governs that behavior, make its class declaration accurate. Otherwise author the missing system requirement and link it to the parent.
3. For applicable work that is intentionally unfinished, record a tracked deferral under project policy. Do not narrow the parent's promise just because its children are incomplete.

Run and interpret

proof audit --check obligation_completeness --verbose

Missing undeferred coverage is a specification-stage error. Explicit deferrals remain counted warnings, including under strict evidence policy. Audit defaults to failing on warnings unless configured otherwise.

This is structural class allocation. It does not establish that the system requirement is a sufficient refinement, that the behavior is implemented, or that a test exists. Accepted known-issue debt and other dispositions must be read as debt, not as delivered behavior. Review the actual conditions, results, and boundary cases behind each class.

Continue from here

Check for any system satisfier. Follow obligations through lower layers.

Bring one stakeholder requirement whose child requirements cover only part of its promise. Bring a change to Proof.