Change Requests

Records use stable project-prefixed sequence numbers in original request order, not retrospective file creation time. The initial request is reconstructed from available evidence; see its provenance. Canonical requirement IDs and historical acceptance records remain unchanged.

Each request is a change_request Need with Draft / Accepted / Implemented status. Implementation status describes completed agreed scope; requirement acceptance, verification and release approval remain separate.

ID

Title

Status

STV_CR_001

Initial project request: traceability exploration

implemented

STV_CR_002

Starting-node requirement amendment

implemented

STV_CR_003

Draft usability problem resolution

implemented

STV_CR_004

Problem-report model and folder handover

implemented

STV_CR_005

Draft relationship-control ordering

implemented

STV_CR_006

Centered parents and interactive seed selection

implemented

STV_CR_007

STV_CR_007: Record folder layout

implemented

STV_CR_008

STV_CR_008: Trace software elements to component code and tests

implemented

STV_CR_009

STV_CR_009: Requirement filenames and verification levels

implemented

STV_CR_010

STV_CR_010: Consolidate system and software test specifications

implemented

STV_CR_011

STV_CR_011: MIT license and author attribution

implemented

STV_CR_012

STV_CR_012: Cancel release and close preparation findings

implemented

STV_CR_013

STV_CR_013: Vertical target levels for artifacts and test records

implemented

STV_CR_014

STV_CR_014: Persistent artifact details on the right side

implemented

STV_CR_015

Collapse all graph relationships

implemented

STV_CR_016

Save the visible view as SVG

implemented

STV_CR_017

Smaller configurable detail text

implemented

STV_CR_018

Page-wide Need attribute controls

implemented

STV_CR_019

Remember current view across page reloads

implemented