Listing OS — Catalog Workspace

Atlas HydrationUnited States

Foundation current○ NO BACKENDCatalog synced

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

Approved intended state

Graphic Strategy v6 · immutable approval target

APPROVED IMAGE 2

H₂

Up to 5.0 PPM molecular hydrogen in 10 minutes

Independent dissolved-hydrogen test result with method and date

Marketplace live snapshot

Capture required

◫No live snapshot yet

Capture the rendered marketplace state before asserting that the submission is live correctly.

Field comparison

3 records / 4 columns

Comparison	Approved	Live	Result
Image asset	Image 2 v3	—	Pending
Primary message	Up to 5.0 PPM molecular hydrogen in 10 minutes	—	Pending
Scope	US · B0H2GO1001	—	Pending

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 verify that submitted listing, A+, and Store content is live, correct, complete, and linked to the approved internal version.

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.
Used for broad operating surfaces with a page header, primary content, actions, and optional supporting context.
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 Live Verification Center.

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

Guidance: Live Verification Center should verify that submitted listing, A+, and Store content is live, correct, complete, and linked to the approved internal version.

verification queueinternal/live comparechecksevidencepass/faillink version

Architecture signals

Screen map: PUB-006Surface: PublishingTemplate: StandardPageTemplateEntities: artifact_version, publishing_job, live_verificationStates: Pending, Matched, Mismatch, Not Found, Verified