Connect a change record to requirement review

What the check observes

For a change or defect record's affected requirements, the check resolves each requirement and looks for a citation of the record in its current review motivation or append-only motivation history. Matching is case-insensitive. This preserves a legitimate older change citation after a later approval replaces the current motivation. The reverse question, whether a current approval has an appropriate motivation, belongs to another check.

Example: the record names an untouched review

# Illustrative approval after substantive review and policy authorization
proof approve SYS-REQ-042 --role reviewer \
  --motivation-kind chg --motivation-ref CHG-17

Resolve the finding

1. Compare the record's affected requirements with the actual intent and implementation delta. Resolve any unknown requirement IDs.
2. Review each affected requirement and its evidence. If it truly belongs to the change, record the correct motivation through the authorized approval workflow.
3. Correct an erroneous affected list with an explanation. Preserve valid historical links when later approvals occur instead of rewriting the past to match the newest record.

Run and interpret

proof audit --check change_record_lands --verbose

The check reports warnings when the required return link is absent. A change record may exist before the corresponding review is complete; that intermediate state should remain visible. Audit defaults to a warning failure threshold unless configured otherwise.

A citation shows that the record reached the review trail. It does not establish implementation, successful tests, defect closure, or approval authority by itself. The configured approval policy determines who can make the decision, including any explicit agent delegation.

Continue from here

Check declared change backing. Review requirement evidence.

Bring a change record whose requirement impact is difficult to reconstruct. Bring a change to Proof.