Atlas HydrationUnited States
Structured shellDIR-012
Page guide
Readiness & Data Gaps

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

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
readiness score

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

2
hard gates

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

3
missing inputs

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

4
question queue

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

5
owners

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

6
provisional override

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

7
recheck 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
Screen states
not readyminimumstrongidealoverride

Primary actions

Navigation and exits

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.