Atlas HydrationUnited States
Structured shellWS-106
Page guide
VOC & Review Research Editor

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
themes

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

2
praise/complaints

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

3
objections

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

4
customer language

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

5
use cases

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

6
evidence snippets

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

7
handoffs

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

Governed component composition

WorkspaceShellTabsInspectorPanelStickyActionBarStateBadgeArtifactHeaderArtifactSectionEvidencePanel

Expected data

Primary endpoint
/v1/artifacts/{artifactId}
Primary entities
artifact, review_request
Screen states
drafteditingreviewrevision requestedapprovedlocked

Primary actions

Open ArtifactidOpen ArtifactidOpen Artifactid

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.