Listing OS — Catalog Workspace

Atlas HydrationUnited States

Foundation currentCatalog synced

Validated sources

Needs review

Rows ingested

2,865

Freshness SLA

98%

Source intake

Every source remains versioned, attributable, and linked to the research outputs it supports

4 records / 5 columns

File	Validation	Rows	Freshness
SmartScout_Category_Hydrogen_Water.csvSmartScout	Validated	1843	Today
Keepa_Hydrogen_Water_Export.xlsxKeepa	Validated	922	Today
US_Top_Search_Terms_Q1_2026.csvBrand Analytics	Validated	100	Yesterday
Clinical_Evidence_Packet.pdfEvidence	Needs Review	0	3 days

What this page is supposed to answer

What should we do next across the catalog?
Which work is already complete, running, blocked, or recommended?
Which execution should be added, reordered, deferred, or launched?
What should a Research Analyst, Listing Director, Account Manager, Brand Director, Compliance Reviewer decide or understand here?

Why it exists

Director is the command center: it decides what should happen, in what order, at what scope, and whether work should be manual, assisted, or machine-run. This specific page exists to upload, classify, process, and govern source materials for the selected brand or scope.

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

The roadmap is the center of Director because AI recommendations should be advisory, while the listing director controls sequence and priority.
The catalog grid has three lenses over the same products: current assets, audit and quality, and execution readiness.
AI guidance belongs where action decisions happen, not as a disconnected chatbot.
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 Source Intake Center.

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

Guidance: Source Intake Center should upload, classify, process, and govern source materials for the selected brand or scope.

upload zonesource registerprocessing statusauthority markerduplicate detectionevidence links

Architecture signals

Screen map: DIR-017Surface: DirectorTemplate: StandardPageTemplateEntities: brand, source_materialStates: Uploading, Processing, Parsed, Failed, Conflict