Listing OS — Catalog Workspace

Atlas HydrationUnited States

Foundation currentCatalog synced

Product

H2Go Portable Hydrogen Water BottleB0H2GO1001

→Product

H2Glass Countertop Hydrogen GeneratorB0H2GL2002

→Product

Molecular Hydrogen Tablets — 30 CountB0HTAB3003

→Product

Vitamin C Radiance SerumB0NVCS4004

→Artifact

H2Go Product BriefProduct Brief · v4

→Artifact

H2Go Keyword ResearchKeyword Research · v3

→

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 search across brands, products, ASINs, executions, artifacts, versions, comments, and live states.

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 Universal Search Results.

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

Guidance: Universal Search Results should search across brands, products, ASINs, executions, artifacts, versions, comments, and live states.

global query barfacetssaved searchesresult previewsrecent searches

Architecture signals

Screen map: GLB-004Surface: GlobalTemplate: StandardPageTemplateEntities: brand, product, artifact, artifact_version, execution, review_requestStates: No Results, Partial Results, Permission Filtered