STV Sphinx Traceability View

Getting started

  • Getting started
  • Licensing

Explore this project's traces

  • Explore this project’s traces

Scope management

  • Change Requests
  • 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
      • Pane boundary acceptance follow-up
    • STV_PR_016: SVG export omits visible graph overflow
  • Project Metrics

Requirements

  • Stakeholder requirements
  • System requirements
  • Software requirements

Architecture

  • Architecture Design Decisions
  • Architecture View for System
  • System elements
  • Architecture View for Software
  • Software elements
  • Behavioral state machines
  • Technology stack and dependency decisions
  • Traceability

Verification and Validation

  • Implementation verification plan
  • CI validation and candidate provenance
  • Test-case specification
  • Executable test scripts
  • Executable requirement coverage
  • Release test executions

Miscellaneous

  • Internal interfaces and model contract
  • Implementation concept and handover
  • Review and scope decisions
  • Project maturity
  • Sources and evidence

Utilities

  • Methods
  • Minimal requirements and allocation model
STV Sphinx Traceability View
  • Problem Tickets
  • STV_PR_015: Correct detail readability, metadata controls and artifact-ID links

STV_PR_015: Correct detail readability, metadata controls and artifact-ID links

Problem report: Correct detail readability, metadata controls and artifact-ID links STV_PR_015
status: fixed
tags: usability, persistent_details
basis: owner
evidence: docs/problem-tickets/STV_PR_015_detail-presentation.rst
priority: unassigned
verification_state: passed

Reporter/date: Project owner, 2026-10-24, acceptance findings in this conversation. Language corrected without changing meaning.

Reported/expected: Make the detail views twice as wide. Secondary attributes such as status and tags must start folded. The existing arrow must fold/unfold them; it currently does nothing. The artifact-ID link in copied details must lead to the actual artifact, rather than this same view. Other working links must keep working.

Input: Commit 740c35ce234ec26b16c76a0b77463b273f84863c plus the current uncommitted CR014 implementation and the owner’s acceptance findings.

Diagnosis: RENDER fixes the dock at 360 px. The lazy copied content misses Sphinx-Needs’ document-ready metadata handler, so its show-state and inert spans survive extraction. INSPECT rebases the header self-link to the copied Need ID, turning original navigation into an in-box jump. The real Firefox file/HTTP baseline reproduces these findings.

Resolution: Target a 720 px dock; place it below graph containers at or below 1120 px, bounded by available width. INSPECT initializes only copied metadata controls with folded defaults, per-table state and pointer/Enter/ Space activation, unique IDs and ARIA state. Reuse preserves local state. Keep canonical header-ID URLs and open them in a new tab; ordinary local body fragments remain namespaced. Existing sanitization stays in force.

Affected V-cycle: Keep explicitly opened arti... (STV_SHR_057), Present and focus persisten... (STV_SWR_064), Open canonical object links (STV_SWR_016), Use portable output URLs (STV_SWR_018); owners Hover, persistent details a... (STV_SWE_INSPECT) and Accessible view and viewport (STV_SWE_RENDER). New regression Readable details, metadata ... (STV_TC_SY_065). Design review: Round 13: Detail acceptance corrections. State transitions: Behavioral state machines (Copied metadata disclosure).

Actual result: Both baseline variants fail; all 127 distinct selected checks pass after the correction, including file/HTTP acceptance, existing persistence/races, adjacent rich-content/hover/security/nested-path checks, frontend units and clean wheel/source-package checks. Full capacity and release qualification were not repeated. Evidence and phase identity: PR015 detail acceptance corrections: development verification.

Disposition: Fixed and development-verified. Owner acceptance retest is pending; no commit, release or external publication is implied.

Pane boundary acceptance follow-up

The owner supplied an annotated screenshot showing the unmarked side-pane edge, the graph disappearing behind it and a shadowed gap at the first card. Requested resolution: a thin grey outline around the pane whenever it is open. The frame now marks all four edges, aligns with the graph’s top/full height and retains padding around shadow-free cards. This is a state-neutral CSS refinement of Present and focus persisten... (STV_SWR_064); verification extends Readable details, metadata ... (STV_TC_SY_065) and reruns the existing viewport-boundary and persistent browser procedures. See the follow-up results in PR015 detail acceptance corrections: development verification.

Previous Next

© Copyright .

Built with Sphinx using a theme provided by Read the Docs.