Execute

Build the operating foundation first, then run complete optimizations for products or product groups.

Active workflowBrand + catalog foundation

Writes continuously toCatalog + Library / Artifacts

1.01 / Client / Brand

Client + Brand Context

Confirm the client, brand, marketplace, trust rules, and material the system cannot know.

input gate

Required inputs

Client identity
Brand assets
Transcripts and reference material

ProducesGoverned run context + client asset intake

Saved as a versioned artifact with source lineage and approval state.

Unlocks nextSource ingestion

The Catalog reflects the new operating state immediately after approval.

Current stage readinessReady to begin

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 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 show recommended actions, readiness, dependencies, mode, owner, priority, and live execution status by product and artifact.

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 Catalog Grid — Execution.

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

Guidance: Catalog Grid — Execution should show recommended actions, readiness, dependencies, mode, owner, priority, and live execution status by product and artifact.

execution cellsrecommended next step columnreadiness badgesdependency promptsmode selectorqueue controls

Architecture signals

Screen map: DIR-008Surface: DirectorTemplate: CatalogMatrixPageTemplateEntities: product, artifact, executionStates: Ready, Blocked, Recommended, Running, Waiting Review

Execute

Build the Foundation

Optimize Products

Client + Brand Context