⌕◔
Atlas HydrationUnited States
Structured shellLIB-013
Page guide
Internal vs Live Comparison

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

Home/Library/Internal vs Live Comparison
LIB-013 · StandardPageTemplate

Internal vs Live Comparison

Compare approved internal artifact versions with the version currently live on Amazon or advertising platforms.

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
side-by-side content

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

2
field/image/module differences

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

3
live timestamp

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

4
verification status

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

5
link/update actions

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/{artifactId}
Primary entities
artifact, artifact_version, live_verification
Screen states
matcheddriftedunknown live state

Primary actions

Open VerificationOpen Artifactid

Navigation and exits

PUB-006
Live Verification CenterVerify that submitted listing, A+, and Store content is live, correct, complete, and linked to the approved internal version.
->WS-123
Version Compare & ReconciliationCompare versions, AI output versus director-edited content, internal versus live, or client feedback versus draft, and reconcile selected changes.
->

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.