Listing Platform Product Review Sandbox

Atlas HydrationUnited States

Deep implementationGLB-005

Approval requested

H2Go Graphic Strategy v6 is ready for review.

5m ago

Publishing completed

H2Go listing copy was accepted by Amazon and is awaiting verification.

2h ago

Execution blocked

Hydrogen Tablet claims review needs clinical evidence.

4h ago

Measurement complete

H2Glass hero-image impact window is complete.

1d ago

What this page is supposed to answer

What context am I operating in?
What work or notification needs my attention?
Where can I jump without losing scope?
What should a Listing Director, Brand Director, Creative Director, Research Analyst, Listing Specialist, Creative Producer, Advertising Strategist, Compliance Reviewer, Account Manager, Client Approver, Platform Admin decide or understand here?

Why it exists

Global screens preserve access, context, search, notifications, and personal work so the user never loses the operating frame for the brand, marketplace, or assignment. This specific page exists to centralize execution, review, approval, publishing, blocker, and performance notifications.

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

Global context is not decorative. It controls which products, artifacts, permissions, and marketplace states are visible.
Search and notifications should deep-link into the exact product, artifact, execution, approval, or publishing state.
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 Notifications Center.

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

Guidance: Notifications Center should centralize execution, review, approval, publishing, blocker, and performance notifications.

notification feedseverity filtersmark readsnoozenotification settings

Architecture signals

Screen map: GLB-005Surface: GlobalTemplate: StandardPageTemplateEntities: execution, review_request, approval_request, publishing_job, metric_observationStates: Empty, Unread, Critical