Atlas HydrationUnited States
Structured shellLIB-009
Page guide
Artifact Performance Record

What exists for this brand, family, product, ASIN, or artifact type? Which version is current, approved, live, superseded, or retired?

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
KPI cards

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

2
time series

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

3
placement breakdown

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

4
before/after

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

5
confidence

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

6
recommendation

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

Governed component composition

PageHeaderBreadcrumbsCardTabsActivityFeedInspectorPanelVersionTimelineTrendStatChartFramePerformanceAttributionCard

Expected data

Primary endpoint
/v1/artifacts/{artifactId}
Primary entities
artifact, recommendation, metric_observation
Screen states
insufficient datameasuringstabledecliningwinning

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.