Connect software requirements to a live system parent

What the check observes

The check inspects active software and integration requirements. It requires a satisfies relationship and resolves its targets, accepting the record when at least one target is an active system requirement. A missing ID, a terminal parent, or a target at the wrong layer cannot be its sole parent. Additional historical links may remain when a valid live system target is also present.

Example: a software child still points to a superseded parent

# After reviewing the actual refinement relationship
proof req link add SW-REQ-042 satisfies SYS-REQ-073

# Inspect the complete lineage before removing any historical link
proof req show SW-REQ-042 --with lineage,traces

Resolve the finding

1. Read the reported target defects: nonexistent, terminal, wrong layer, or no usable satisfies entry.
2. Compare the software behavior with the proposed live parent. Update the child if the new parent's promise differs, rather than changing the link alone.
3. Add the legitimate system relationship and handle obsolete links through the reviewed migration. Then inspect the parent's downward coverage as a separate question.

Run and interpret

proof audit --check l2_software_complete --verbose

This is a specification-stage error check. Retired, superseded, and rejected child records are excluded. It checks the configured software/integration layers and respects an explicit L2 skip.

At least one valid live parent satisfies this structural predicate. It does not prove logical refinement, allocation of every parent obligation, or that the child is implemented and verified. A syntactically correct parent can still govern unrelated behavior.

Continue from here

Check downward system realization. Follow individual obligations into children.

Bring a software requirement affected by a system-level change or supersession. Bring a change to Proof.