ADR 028 Project Dependency Navigation - joeroberts/release-radar GitHub Wiki

  • ID: ADR-028
  • Status: Accepted
  • Date: 2026-09-08
  • Date meaning: Original dated decision/source section; extraction recorded 2026-10-02.
  • Implementation: No implementation information was recorded in the source status; tickets own progress.
  • Approval qualification: Recorded accepted decision; dated delivery conditions are historical, not new execution authorization.

Context

Project-wide dependencies and session navigation preserve selected entity identity without changing active execution context.

Decision

The owner selected project-wide dependency relationships focused on the selected ticket, with phase labels. A ticket opened from a nonactive phase retains its identity and displays its cross-phase prerequisites and dependents within that project. The graph never substitutes an active-phase ticket. Stored dependency validation, five lanes, task completion and acceptance semantics are unchanged.

One typed navigation history captures project identity, explicit viewed scope, filters, selection and focus/restoration context across existing surfaces. Back/Forward restores context without creating entries; a new navigation after Back clears Forward history. Local filter adjustments update the current entry. Browsing never dispatches active-phase selection or other delivery mutations. Missing targets retain a valid parent scope with an explanation; restoration never silently substitutes a ticket/phase, broadens a filter or resolves a removed registration to a re-added project by path/name. Existing archive/removal views remain read-only and use their exact identities. Focus returns to the originating valid control/entity, or to an informative heading/recovery message.

The owner selected Projects with empty Back/Forward history on application relaunch, preserving existing startup behavior. Phase 4 navigation is session-only; it adds no navigation persistence, saved-view storage, external URL registration, store migration or portable navigation state. Future planning/search/saved-view surfaces consume this navigation boundary only when separately implemented. This decision does not approve the other proposed D4–D6 planning contracts.