Product lifecycle / 2m 15.24s

Build privately. Publish deliberately. Retire without erasing.

One product moves from private Catalog work into customer discovery, then leaves the assortment while retaining its governed record.

Silent film with burned-in narrationOpen WebM directly

What You Will See

  1. Build privatelyThe product URL remains unavailable while commercial and descriptive facts are prepared.
  2. Review readinessCatalog exposes the facts and lifecycle decision to the manager.
  3. Publish into discoveryThe same identity becomes a sellable customer product page.
  4. Archive cleanlyCustomer visibility ends while staff retain identity, reason and lifecycle history.

Why It Matters

Incomplete work should remain private, and retirement should not destroy the history that explains the product.

Catalog owns identity and lifecycle. Search and storefront visibility follow those decisions asynchronously.

The System Underneath

Product aggregateIdentity, content, price, variants and lifecycle
Publication decisionReadiness and explicit transition
Outbox + projectionsSearch and downstream facts
Customer visibilityPublished enters · archived leaves
Archive is a governed withdrawal, not deletion. Product identity and history remain inside Catalog.

What This Story Proves

Visible proof

Draft remains private, publication exposes the product and archive withdraws it.

Known gap

The current pending-price approval path bypasses the full eleven-check application selling gate; the complete showcase states that explicitly.

Read the current publication decision paths.

AI engineering connectionExecutable feedback constrains autonomous change