Listing Platform Product Review Sandbox

Atlas HydrationUnited States

Deep implementationDIR-016

Review ready

Awaiting approval

Blocked by findings

Approved / downstream ready

Completion and approval control

Execution completion, output readiness, approval state, and the next permitted action stay separate

3 records / 6 columns

Execution	Output readiness	Approval state	Blocking condition	Next permitted action
H2Go Graphic StrategyGraphic Strategy v7	96%	Pending	None	Brand Director decision	Inspect
Zoya Keyword RefreshBackend Keywords v5	82%	Revision Requested	Search-term duplication	Owner revision	Inspect
Koblenz Core ImagesCore Images v4	100%	Approved	None	Publishing package	Inspect

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, Brand Director, Creative Director, Compliance Reviewer, Client Approver 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 review completed or review-ready executions, preview outputs, approve, request revision, or launch downstream work.

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 Completion & Approval Queue.

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

Guidance: Completion & Approval Queue should review completed or review-ready executions, preview outputs, approve, request revision, or launch downstream work.

completion cardsartifact previewapproval requirementcompare linkapprove and continuerevision action

Architecture signals

Screen map: DIR-016Surface: DirectorTemplate: CollectionPageTemplateEntities: artifact, artifact_version, execution, review_request, approval_requestStates: Ready For Review, Partially Approved, Approved, Revision Requested