⌕◔
Atlas HydrationUnited States
Structured shellDIR-011
Page guide
Dependency Graph

What should we do next across the catalog? Which work is already complete, running, blocked, or recommended?

Home/Director/Dependency Graph
DIR-011 · GraphPageTemplate

Dependency Graph

Visualize upstream requirements, downstream unlocks, approval gates, iterative loops, and blocked execution paths.

Structured review shell
This route is intentionally visible before detailed implementation.

Review the intended hierarchy, information regions, actions, states, and navigation. Use Review Mode to identify what must be added or changed before this screen is promoted to deep implementation.

Intended screen regions

Derived from the page implementation registry

1
interactive graph

Review whether this region belongs on the page, where it should appear, and what decisions it must support.

2
hard/soft dependency legend

Review whether this region belongs on the page, where it should appear, and what decisions it must support.

3
blocked nodes

Review whether this region belongs on the page, where it should appear, and what decisions it must support.

4
critical path

Review whether this region belongs on the page, where it should appear, and what decisions it must support.

5
what-if controls

Review whether this region belongs on the page, where it should appear, and what decisions it must support.

Governed component composition

PageHeaderSearchFieldTabsDataTablePaginationBulkActionBarVersionTimeline

Expected data

Primary endpoint
/v1/director/summary
Primary entities
execution, approval_request
Screen states
completeblockedprovisionalcycle detected

Primary actions

Open ReadinessOpen Artifactid

Navigation and exits

DIR-002
Roadmap Priority ListOrdered execution roadmap combining completed, active, upcoming, recommended, blocked, deferred, and canceled work.
->DIR-012
Readiness & Data GapsEvaluate minimum, strong, and ideal readiness; manage exact missing-input questions and provisional execution decisions.
->WS-005
Artifact Workspace ShellConsistent shell for any artifact with context navigation, specialized editor, review controls, comments, lineage, versioning, and downstream impact.
->

Acceptance criteria

  1. Renders only after required context and permissions resolve.
  2. Supports declared loading, empty, blocked, error, and stale-data states without layout shift.
  3. All governed actions expose reason, target object, resulting state, and undo/recovery path where allowed.
  4. Keyboard focus order follows visual reading order and all overlays restore focus to their invoker.
  5. Route is deep-linkable and browser back returns to the prior scoped view without losing safe local filters.