---
_version: '1'
uuid: 45541828-5887-4ba8-9679-d353908dfa85
created: 2025-10-26T16:55:20.079234662Z
parents:
- uuid: b871f9b8-ae8f-405b-8727-11e2409f20c3
fingerprint: 7f9c8e5d4b3a2f1e0d9c8b7a6f5e4d3c2b1a0f9e8d7c6b5a4f3e2d1c0b9a8f7e
hrid: USR-007
---
# SYS-019 Relationship Navigation Views
## Statement
The `req list` command shall expose relationship-focused views that make it easy to inspect parents, children, ancestors, and descendants of selected requirements.
## Rationale
Impact analysis and review prep require seeing the neighborhood around a requirement: upstream drivers, downstream implementations, and gaps such as missing children. Navigating that context inside the CLI keeps engineers in their workflow and avoids context switching.
## Scope
Relationship views shall help engineers understand impact, traceability gaps, and neighbourhood context without switching tools. The command should feel exploratory: easy to enter and exit a view, with clear signposting for depth and traversal.
Traversal behaviours, presentation conventions, and illustrative examples are provided in [SPC-002](./SPC-002.md).
## Verification
- Operators can pivot from a requirement to its parents or children with one flag.
- Depth controls constrain traversal so outputs stay legible.
- Views integrate with filters, ensuring the resulting set reflects both traversal and selection logic.