Listing Platform Product Review Sandbox

Atlas HydrationUnited States

Deep implementationPUB-001

Sandbox v1.3 · Stateful vertical slice

Move concentration proof into Image 2H2Go Portable Hydrogen Water Bottle · B0H2GO1001

Current: Recommendation

1Recommend 2Roadmap 3Execute 4Create 5Review 6Approve 7Publish 8Verify 9Measure 10Learn

Ready packages

Processing

Live unverified

Exceptions

Journey publishing package

Not Created

H2Go Image 2 proof hierarchy

Graphic Strategy v6 → Core Image Brief v3 → ASIN B0H2GO1001 · US

Versionv6

ContentAi Draft

ApprovalNot Submitted

PublishingNot Created

VerificationNot Started

Open package

Publishing operations

3 records / 5 columns

Package / job	Marketplace	Status	Approved lineage
H2Go Image 2	US	Not Created	Strategy v6
Vitamin C A+ v3	US	Processing	A+ v3
Hydrogen Tablets copy	US	Failed	Copy v2

What this page is supposed to answer

Which exact approved versions are ready to package?
What did the marketplace accept, reject, override, or partially publish?
Does the live page match the intended approved state?
What should a Listing Director, Listing Specialist, Brand Director, Creative Director, Account Manager decide or understand here?

Why it exists

Publishing controls how approved work becomes marketplace-visible work and proves whether Amazon actually rendered the intended version. This specific page exists to overview of ready-to-publish work, active submissions, verification status, exceptions, and live-state drift.

How to use it

Start with the page header to confirm the screen, scope, and review status.
Read the primary cards or table as the operating surface for the current decision.
Use the element info buttons to inspect why a region, component, action, or state exists.
If the page feels wrong, add a Review Mode call-out and then save an explanation update describing what changed and why.

Important nuance

Approval is not publishing authorization. Submitted is not live. Live is not verified.
Publishing must preserve field-level lineage so partial failures and Amazon overrides can be diagnosed without guessing.
Rollback and retry are recovery workflows, not ordinary one-click catalog actions.
This screen follows a governed template so similar workflows remain consistent.
Old and new explanations should both remain available because product decisions are part of the system history.

Current explanation version

Architecture baseline2026-07-16 / Architecture conversation

What: Initial product guidance for Publishing Dashboard.

Why: Generated from the Listing Division architecture, screen map, navigation spec, execution ontology, component system, and sandbox implementation.

Guidance: Publishing Dashboard should overview of ready-to-publish work, active submissions, verification status, exceptions, and live-state drift.

summary KPIsready queueactive jobsverification queueexception alertslive drift

Architecture signals

Screen map: PUB-001Surface: PublishingTemplate: DashboardPageTemplateEntities: publishing_job, live_verificationStates: Empty, Active, Critical Errors