Listing OS — Catalog Workspace

Atlas HydrationUnited States

Foundation currentCatalog synced

Step 1: Choose products

The plan remains a draft until every required dependency and owner is resolved.

H2Go Portable Hydrogen Water BottleB0H2GO1001

Readiness74%

H2Glass Countertop Hydrogen GeneratorB0H2GL2002

Readiness82%

Molecular Hydrogen Tablets — 30 CountB0HTAB3003

Readiness66%

Vitamin C Radiance SerumB0NVCS4004

Readiness91%

Plan readiness

Complete20%

✓ Product scope selected✓ Objective defined✓ Executions selected✓ Dependencies resolved✓ Governance reviewed

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, Account Manager 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 build a multi-step plan, choose scope and mode, insert prerequisites, estimate timing, assign owners, and add the plan to the roadmap.

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.
This screen follows a governed template so similar workflows remain consistent.
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 Execution Plan Builder.

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

Guidance: Execution Plan Builder should build a multi-step plan, choose scope and mode, insert prerequisites, estimate timing, assign owners, and add the plan to the roadmap.

selected executionsscope pickerdependency expansionsequence editorowner assignmentestimate summary

Architecture signals

Screen map: DIR-010Surface: DirectorTemplate: PlanBuilderPageTemplateEntities: artifact, roadmap, executionStates: Draft Plan, Invalid Chain, Ready To Queue, Queued