A dependency relationship means that Item B cannot be fully implemented — or its impact is substantially diminished — until Item A is complete. Triage that ignores dependencies risks selecting items that look high-priority in isolation but are blocked by upstream work that hasn't been scheduled.
Dependency chains — hover items for detail, filter by category
Sequencing logic — three clusters for triage
Foundation items — complete first
These items are preconditions for multiple downstream items. Delaying them delays everything that depends on them. Triage should treat these as high-priority regardless of their individual complexity.
Mid-stream items — need foundation
These items are ready to move once foundation items are in place. Many are the most visible and politically significant items in the HAP — they benefit from having upstream work done first.
Downstream items — complex chains
These items have multiple upstream dependencies or require significant institutional capacity before implementation is meaningful. Scheduling them too early creates delays and dilutes effort.
For triage: The July 2026 Council deadline creates pressure to show early progress. Foundation items are the right answer to that pressure — they're the ones that unlock the rest of the plan. Selecting only visible mid-stream items without clearing upstream dependencies risks delivering activity without impact.