Listing Platform Product Review Sandbox

Atlas HydrationUnited States

Structured shellDIR-015

Structured review shell

This route is intentionally visible before detailed implementation.

Review the intended hierarchy, information regions, actions, states, and navigation. Use Review Mode to identify what must be added or changed before this screen is promoted to deep implementation.

Intended screen regions

Derived from the page implementation registry

1

blocker table

Review whether this region belongs on the page, where it should appear, and what decisions it must support.

2

type/severity

Review whether this region belongs on the page, where it should appear, and what decisions it must support.

3

owner

Review whether this region belongs on the page, where it should appear, and what decisions it must support.

4

age

Review whether this region belongs on the page, where it should appear, and what decisions it must support.

5

affected downstream work

Review whether this region belongs on the page, where it should appear, and what decisions it must support.

6

resolve/request/override actions

Review whether this region belongs on the page, where it should appear, and what decisions it must support.

Governed component composition

PageHeaderDataTableStateBadgeBulkActionBar

Expected data

Primary endpoint: /v1/director/summary
Primary entities: approval_request, publishing_job, source_material
Screen states: openwaiting externalresolvedoverridden

Primary actions

Open ReadinessOpen ApprovalidOpen Exceptions

Navigation and exits

Readiness & Data GapsEvaluate minimum, strong, and ideal readiness; manage exact missing-input questions and provisional execution decisions.

Publishing ExceptionsResolve validation failures, Amazon rejections, partial updates, drift, missing live content, and connector errors.

Approval DetailReview evidence, comments, diffs, risks, and approval policy before approving, rejecting, or requesting revision.

Acceptance criteria

Renders only after required context and permissions resolve.
Supports declared loading, empty, blocked, error, and stale-data states without layout shift.
All governed actions expose reason, target object, resulting state, and undo/recovery path where allowed.
Keyboard focus order follows visual reading order and all overlays restore focus to their invoker.
Route is deep-linkable and browser back returns to the prior scoped view without losing safe local filters.

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 Listing Director, Account Manager, Brand Director, Creative Director, Research Analyst, 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 manage work blocked by missing sources, client decisions, approvals, claims, dependencies, publishing errors, or capacity.

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 when the core job is finding, filtering, comparing, and acting on many records.
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 Blockers & Waiting.

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

Guidance: Blockers & Waiting should manage work blocked by missing sources, client decisions, approvals, claims, dependencies, publishing errors, or capacity.

blocker tabletype/severityownerageaffected downstream workresolve/request/override actions

Architecture signals

Screen map: DIR-015Surface: DirectorTemplate: CollectionPageTemplateEntities: approval_request, publishing_job, source_materialStates: Open, Waiting External, Resolved, Overridden