Atlas HydrationUnited States
Structured shellPUB-003
Page guide
A+ Publishing Jobs

Which exact approved versions are ready to package? What did the marketplace accept, reject, override, or partially publish?

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
job table

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

2
content project

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

3
ASIN assignment

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

4
submission state

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

5
Amazon review

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

6
errors

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

Governed component composition

PageHeaderSearchFieldTabsDataTablePaginationBulkActionBarVersionTimelinePublishPackageCardPublishAttemptRowVerificationPanel

Expected data

Primary endpoint
/v1/publishing/jobs
Primary entities
product, review_request, publishing_job, live_verification
Screen states
readysubmittedunder reviewapprovedrejectedlive

Primary actions

Open JobidOpen Verification

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.