Listing Platform Product Review Sandbox

Atlas HydrationUnited States

Deep implementationLIB-006

Artifact record

Artifact: H2Go Graphic Strategy
Type: Graphic Strategy
Current version: v6
Content state: In Review
Approval: Pending
Live state: Not Live
Owner: Creative Strategy

Lineage

Product Brief v4

→

Keyword Research v3

→

Graphic Strategy v6

→

Core Images v2

Version history

Current review version35m ago

In review

Version 52 days ago

Approved

Version 43 days ago

Superseded

Version 34 days ago

Superseded

Where used

ExecutionH2Go Core Image Production

ApprovalApproval request approval-001

RoadmapRebuild H2Go core image set

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, Compliance Reviewer, 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 permanent artifact record with metadata, current version, preview, status, source, approvals, lineage, use, performance, and actions.

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.
Used when one object needs lineage, state, actions, related records, and an inspector-like context.
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 Artifact Detail.

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

Guidance: Artifact Detail should permanent artifact record with metadata, current version, preview, status, source, approvals, lineage, use, performance, and actions.

header metadatapreviewtabs: overview/content/versions/lineage/approvals/performance/activityactions

Architecture signals

Screen map: LIB-006Surface: LibraryTemplate: DetailPageTemplateEntities: artifact, artifact_version, review_request, approval_request, metric_observation, source_materialStates: Draft, Approved, Live, Retired, Outdated