Atlas HydrationUnited States
Structured shellPUB-008
Page guide
Publishing Recovery & Rollback

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
recovery options

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

2
prior live version

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

3
impact preview

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

4
approval gate

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

5
execute

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

6
verification follow-up

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/{jobId}
Primary entities
artifact_version, review_request, approval_request, publishing_job, live_verification, impact_analysis
Screen states
planningapproval requiredexecutingrecoveredfailed

Primary actions

Open 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.