Atlas HydrationUnited States
Structured shellWS-003
Page guide
Product Family Workspace

What exactly was produced? What source evidence supports it?

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
family header

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

2
child comparison

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

3
shared artifact chain

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

4
reuse matrix

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

5
open executions

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

6
performance summary

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/artifacts
Primary entities
product_family, product, artifact, artifact_version, execution, metric_observation
Screen states
complete familypartial familyconflicting variants

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.