---
_version: '1'
uuid: 46cb949e-6e51-4014-a1ef-418a7ffa83cb
created: 2025-07-23T06:53:50.368620174Z
parents:
- uuid: 12fcd31d-7b7a-41d1-a072-66248ad6f86f
fingerprint: d7a6df07168a0b5e39ef8dea0fd0b33821f6e44630d20ea2d532f1520175baee
hrid: USR-004
- uuid: 2540b2c1-ea21-4732-aafb-ee1c836ca19b
fingerprint: 3ef22648c9e35771efb43c520376391d3bcecc21d4e0cb03a9bfdf946d04d7b9
hrid: USR-003
---
# SYS-005 Suspect Link Detection
## Statement
The tool shall track "suspect links" by comparing the fingerprint stored in a child requirement against the current content fingerprint of its parent requirement.
## Rationale
When parent requirements change, child requirements may need updates to maintain consistency with the new parent specification. Suspect link detection automatically identifies which requirements need review after parent changes, preventing drift between parent and child requirements. This maintains traceability integrity without requiring manual tracking of all changes. The fingerprint-based approach scales efficiently to large requirement repositories.
## Implementation Notes
- A link is "suspect" when stored fingerprint ≠ current parent fingerprint
- Indicates parent has been modified since link was created/reviewed
- Child requirements with suspect links need manual review
- Fingerprints use SHA256 hash of parent content
- Tool computes current fingerprint on-demand for comparison
## Verification
- Tool correctly identifies suspect links after parent modifications
- Tool does not flag links when parent content unchanged
- Tool handles multiple parents (checks each independently)
- Fingerprint comparison is accurate and reliable
- Suspect links are clearly reported with child and parent HRIDs