Check stakeholder requirements have system coverage

What the check observes

Despite its broad name, the current check asks a specific question: does each eligible stakeholder requirement have at least one active system requirement that names it in traces.satisfies? Retired, superseded, and rejected parents are excluded. Assumptions and constraints are also excluded from this downward guarantee check. A terminal system requirement cannot provide coverage for an active stakeholder promise.

Example: the only child was superseded

# Replacement system requirement excerpt
id: SYS-REQ-073
description: "An interrupted import resumes without duplicating accepted records."
traces:
  satisfies: [STK-REQ-042]

Resolve the finding

1. Read each listed stakeholder requirement and decide which active system behavior realizes its promise.
2. Review the replacement requirement's actual semantics before adding or correcting its satisfies link. Preserve the superseded record and its history.
3. If the stakeholder promise itself changed, follow its lifecycle and approval process instead of treating retirement of a child as permission to erase the parent.

Run and interpret

proof audit --check cross_level_complete --verbose

This is a document-stage warning check. If there are no eligible stakeholder requirements, the result reports that there is nothing to check. Audit defaults to failing on warnings unless the project overrides the threshold.

One satisfying system link is enough for this predicate. It does not establish that all acceptance criteria are covered, that every obligation has a child, that software is implemented, or that documentation and tests are current. A displayed coverage percentage refers to this stakeholder-to-system relationship only.

Continue from here

Check each stakeholder obligation. Review completeness beyond graph links.

Bring one stakeholder promise whose path into the system is uncertain. Bring a change to Proof.