STV Sphinx Traceability View
STV version: 1.2.0
STV (Sphinx Traceability View) adds interactive traceability graphs to Sphinx-Needs documentation. Explore how requirements, architecture elements and tests connect, then inspect their published details without losing your place in the graph.
Views are part of the generated HTML and work offline from disk or on static HTTP hosting. STV uses your existing Need types and relationships; no separate application server is needed.
New to STV? Start with Getting Started for a live demonstration, installation and a minimal integration example.
Getting started
Explore this project's traces
Scope management
- Change Requests
- Initial project request: traceability exploration
- Starting-node requirement amendment
- Draft usability problem resolution
- Problem-report model and folder handover
- Draft relationship-control ordering
- Centered parents and interactive seed selection
- STV_CR_007: Record folder layout
- STV_CR_008: Trace software elements to component code and tests
- STV_CR_009: Requirement filenames and verification levels
- STV_CR_010: Consolidate system and software test specifications
- STV_CR_011: MIT license and author attribution
- STV_CR_012: Cancel release and close preparation findings
- STV_CR_013: Vertical target levels for artifacts and test records
- STV_CR_014: Persistent artifact details on the right side
- STV_CR_015: Collapse all graph relationships
- STV_CR_016: Save the visible view as SVG
- STV_CR_017: Smaller configurable detail text
- STV_CR_018: Page-wide Need attribute controls
- STV_CR_019: Remember current view across page reloads
- Problem Tickets
- STV_PR_001: Facing edge ports
- STV_PR_002: Direct readable routes
- STV_PR_003: Increase view height
- STV_PR_004: Delay hover details
- STV_PR_005: Order relationship controls by vertical direction
- STV_PR_006: Detail tooltips fail on long Windows paths
- STV_PR_007: Authored detail transport attributes bypass resource policy
- STV_PR_008: Historical distributions omit complete license materials
- STV_PR_009: Build and test environments contain advisory-matched dependencies
- STV_PR_010: Source archives include execution logs despite exclusion
- STV_PR_011: Incremental output retains obsolete published data
- STV_PR_012: Limited automated validation and artifact provenance
- STV_PR_013: Keep node positions stable during relationship expansion
- STV_PR_014: Mark the visible graph boundary with a grey line
- STV_PR_015: Correct detail readability, metadata controls and artifact-ID links
- STV_PR_016: SVG export omits visible graph overflow
- Project Metrics
Architecture
- Architecture Design Decisions
- STV_ADR_001: Static build integration and browser runtime
- STV_ADR_002: Portable graph and rendered-detail bundle
- STV_ADR_003: Transactional exploration and semantic rank layout
- STV_ADR_004: Concrete dependency and delivery stack
- STV_ADR_005: Optional seed sets and paged project entry
- STV_ADR_006: Centered layout and interactive overview
- STV_ADR_007: Architecture-owned component directories
- STV_ADR_008: Stable navigation after fresh placement
- STV_ADR_009: Resolve evidence rows before exploration
- STV_ADR_010: Separate persistent details from hover inspection
- STV_ADR_011: Separate exploration, page metadata and SVG capture
- STV_ADR_012: Browser-local opt-in view snapshots
- Architecture View for System
- System elements
- Architecture View for Software
- Software elements
- Behavioral state machines
- Technology stack and dependency decisions
- Browser runtime
- Python build-time dependencies
- Maintainer and verification tools
- Packaging and reproducibility
- Feasibility evidence and limits
- Reproduce the dependency check
- Compiled ELK dependency notices
- Patched maintainer tooling
- Source distribution boundary
- Navigation projection policy
- Classified placement compatibility
- Persistent and hover inspection placement
- CR015-018 browser presentation and export
- Browser view storage
- Traceability
Verification and Validation
- Implementation verification plan
- Canonical test and execution records
- Execution environments
- Host failure ownership
- Capacity measurements
- Release exit criteria
- Concept review additions
- Remote-media fallback fixtures
- Starting-node amendment checks
- Centered-layout and picker MVP checks
- Historical draft smoke scope
- Stable navigation increment
- CR_013 classified-row checks
- PR014 viewport boundary regression
- CR014 persistent details verification
- PR015 acceptance correction
- CR015-018 verification increment
- Remembered view verification
- CI validation and candidate provenance
- Test-case specification
- Executable test scripts
- Executable requirement coverage
- Release test executions
- Method migration qualification handover
- 0.1.0-candidate-1 execution
- 0.1.0-candidate-2 execution
- 0.1.0-candidate-3 execution
- 0.1.0-candidate-4 execution
- Initial MVP consolidated verification
- 0.2.0-candidate-1 execution
- 0.2.0-candidate-2 execution
- 0.2.0-candidate-3 execution
- 0.2.0-candidate-4 execution
- 0.2.0-candidate-5 execution
- v0.2.0 final release validation
- 0.2.0-method-1 execution
- 0.2.0-method-2 execution
- 1.0.0-candidate-1 execution
- Canceled release preparation
- Maintenance regression evidence
- PRSA-002 development fix verification
- Historical licensing and toolchain remediation
- PRSA-004 source archive boundary verification
- PRSA-005 clean documentation publication verification
- PRSA-006 CI and provenance preparation
- PR013 position-stability proof of concept
- PR013 final development verification
- CR_013 classified evidence rows: development verification
- PR014 viewport boundary: development verification
- CR014 persistent details: development verification
- PR015 detail acceptance corrections: development verification
- 1.0.0-candidate-2 execution
- 1.1.0-candidate-1 execution
- 1.1.0-candidate-2 execution
- 1.1.0-candidate-3 execution
- 1.1.0-candidate-4 execution
- Post-release build cleanup, 2026-10-26
- CR019 development verification
- 1.2.0-candidate-1 execution
Miscellaneous
- Internal interfaces and model contract
- Author interface
- Build-to-browser contract
- State interface
- Capacity and performance
- Remote embedded resource contract
- Layout and inspection contract
- Detail asset path contract
- Detail transport marker ownership
- Local documentation publication
- Committed geometry and navigation layout
- Classified test evidence placement
- Viewport clipping marker
- Persistent detail collection contract
- Copied Need metadata controls
- Detail pane boundary
- CR015-018 command and presentation contracts
- Visible-area capture and resource contract
- Remembered view protocol
- Implementation concept and handover
- Product boundary and source layout
- Component interfaces
- Sphinx lifecycle contract
- Final rendered details and offline loading
- Graph and state contracts
- Layout algorithm and library boundary
- Rendering, viewport and inspection
- Implementation sequence and completion gates
- Remote embedded resources
- Project-root pages and multiple roots
- Navigation geometry delivery
- Classified-row implementation slice
- Viewport boundary presentation
- Persistent-details slice
- CR015-018 delivery sequence
- Remembered view increment
- Review and scope decisions
- Resolved stakeholder questions
- Agreed MVP scope
- Deferred features - scope resolved
- Owner design clarification queue
- Remaining refinement - not blockers for design
- Working assumptions - not confirmed obligations
- Revision history
- PR013 approved PoC baseline refinement
- CR_013 nine-category evidence rows
- PR014 boundary marker
- CR014 persistent details decisions
- PR015 acceptance findings
- v1.0.0 release acceptance
- CR015-018 concept increment, 2026-10-25
- Project maturity
- 1.2.0 release qualification, 2026-11-01
- CR019 implemented development increment, 2026-10-28
- CR019 owner acceptance and delivery authorization, 2026-10-28
- CR019 stakeholder amendment awaiting owner review, 2026-10-28
- 1.1.0 release qualification, 2026-10-25
- CR015-018 development implementation, 2026-10-25
- CR015-018 accepted concept, 2026-10-25
- Creation history: CR015-018, 2026-10-25
- v1.0.0 released
- PR014 visible viewport boundary fixed
- CR_013 classified evidence rows implemented
- PR013 stable navigation finalized
- PRSA-006 local preparation; hosted hardening pending
- PRSA-005 clean publication remediation
- PRSA-004 source archive remediation
- PRSA-001 and PRSA-003 remediation
- PRSA-002 security fix awaiting owner review
- Release canceled; maintenance fixes accepted
- 1.0.0 release preparation, 2026-10-24
- Component source organization, 2026-10-24
- Requirement filenames and test levels, 2026-10-24
- MIT licensing decision, 2026-10-24
- Current release increment
- Previous baseline
- Review and lifecycle records
- Maintenance rule
- Implementation verification dashboard
- CR014 persistent details
- PR015 detail acceptance corrections
- Independent method tooling, 2026-10-25
- Additional browser smoke check, 2026-10-25
- Sources and evidence
- Stakeholder baseline v1 acceptance
- Internal specification source baseline
- Concrete technology selection and design checks
- Concept review delegation and round 1
- Concept review round 2 - remote media and diagram readability
- v0.2.0 stakeholder release and delegated review
- Centered-layout and interactive-seed MVP clarification
- Centered-layout amendment approval and concept acceptance delegation
- PR013 owner and design evidence
- CR_013 input and fallback decision
- PR014 owner evidence
- CR014 owner decisions
- PR015 owner acceptance findings, 2026-10-24
- v1.0.0 release instruction, 2026-10-24
- CR015-018 acceptance and Save As clarification, 2026-10-25
- Round 15 acceptance delegation, 2026-10-25
Utilities
- Methods
- Minimal requirements and allocation model
- Purpose and limits
- Workflow phases and documentation continuity
- Central maturity and review records
- Portable documentation and repository location
- Nine types
- Five canonical relations
- Channeling stakeholder requirements directly to software
- Problem-report intake and handover
- Attributes
- Test cases and execution history
- Architecture design decisions
- Recovery and quality review
- Sphinx reuse
- Publish the method
- Documentation presentation
- Reproducing owner prompts
- Shared project layout
- Change-request lifecycle and metrics
- Default page metadata controls