Library / Artifacts

The saved system of record for every brand, catalog, client, and product output.

Artifact lifecycle

Current approved and in useUpdated newer, not publishedPast previous versions

Brand + catalog wide

Foundation library

Shared intelligence and client-owned assets available to the entire catalog.

Product level

Catalog artifact library

The same catalog you execute from, organized around everything already produced and saved.

H2Go Portable Hydrogen Water BottleB0H2GO1001 · H2GO-01-BLKfamily-hydration

H2Glass Countertop Hydrogen GeneratorB0H2GL2002 · H2GLASS-01family-hydration

Molecular Hydrogen Tablets — 30 CountB0HTAB3003 · HTAB-30family-tablets

Vitamin C Radiance SerumB0NVCS4004 · NVC-30MLfamily-serums

What this page is supposed to answer

What exists for this brand, family, product, ASIN, or artifact type?
Which version is current, approved, live, superseded, or retired?
Where is this artifact used and what downstream work depends on it?
What should a Listing Director, Brand Director, Creative Director, Research Analyst, Listing Specialist, Creative Producer, Advertising Strategist, Account Manager decide or understand here?

Why it exists

Library is the permanent system of record for all research, strategy, copy, creative, approvals, source evidence, versions, live states, and performance records. This specific page exists to system-of-record landing page with artifact categories, recent items, saved views, live assets, and maintenance alerts.

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 grid and Workspace are operating surfaces; the Library is the versioned archive behind them.
Performance should be attached to the artifact that produced it, not trapped in a separate analytics silo.
Reusable assets should show where they are used before rollout or retirement.
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 Library Home.

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

Guidance: Library Home should system-of-record landing page with artifact categories, recent items, saved views, live assets, and maintenance alerts.

category cardsrecent artifactsfavoritesoutdated alertslive/internal countssearch

Architecture signals

Screen map: LIB-001Surface: LibraryTemplate: DashboardPageTemplateEntities: artifactStates: Empty, Active, Maintenance Due