Listing Platform Product Review Sandbox

Atlas HydrationUnited States

Structured shellADM-009

Structured review shell

This route is intentionally visible before detailed implementation.

Review the intended hierarchy, information regions, actions, states, and navigation. Use Review Mode to identify what must be added or changed before this screen is promoted to deep implementation.

Intended screen regions

Derived from the page implementation registry

1

content editor

Review whether this region belongs on the page, where it should appear, and what decisions it must support.

2

metadata

Review whether this region belongs on the page, where it should appear, and what decisions it must support.

3

version history

Review whether this region belongs on the page, where it should appear, and what decisions it must support.

4

compatibility

Review whether this region belongs on the page, where it should appear, and what decisions it must support.

5

test preview

Review whether this region belongs on the page, where it should appear, and what decisions it must support.

6

approval

Review whether this region belongs on the page, where it should appear, and what decisions it must support.

7

usage impact

Review whether this region belongs on the page, where it should appear, and what decisions it must support.

Governed component composition

PageHeaderTabsFormFieldDataTableStickyActionBarDependencyGraph

Expected data

Primary endpoint: /v1/admin/health
Primary entities: artifact, artifact_version, review_request, approval_request, impact_analysis
Screen states: draftreviewapproveddeprecated

Primary actions

Open TemplatesOpen Audit

Navigation and exits

Audit LogSearch immutable records of user, AI, execution, approval, publishing, registry, permission, and artifact changes.

Artifact TemplatesBrowse reusable artifact and creative templates available to execution and Workspace editors.

Acceptance criteria

Renders only after required context and permissions resolve.
Supports declared loading, empty, blocked, error, and stale-data states without layout shift.
All governed actions expose reason, target object, resulting state, and undo/recovery path where allowed.
Keyboard focus order follows visual reading order and all overlays restore focus to their invoker.
Route is deep-linkable and browser back returns to the prior scoped view without losing safe local filters.

What this page is supposed to answer

Who can do what?
Which definitions, policies, and integrations power the operating system?
What changed, who changed it, and what downstream behavior did it affect?
What should a Platform Admin, Brand Director, Creative Director, Listing Director, Compliance Reviewer decide or understand here?

Why it exists

Administration governs the registries, policies, integrations, permissions, taxonomies, and audit history that keep the platform coherent as it grows. This specific page exists to edit, version, validate, approve, and deprecate a reusable template, policy, rule set, or knowledge base.

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

Execution definitions should be governed data, not scattered hard-coded workflows.
Policy changes affect downstream approval, publishing, automation, and permission behavior.
Administrative edits should leave an audit trail because they change how the platform reasons.
Used for broad operating surfaces with a page header, primary content, actions, and optional supporting 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 Template / Knowledge Base Detail.

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

Guidance: Template / Knowledge Base Detail should edit, version, validate, approve, and deprecate a reusable template, policy, rule set, or knowledge base.

content editormetadataversion historycompatibilitytest previewapproval

Architecture signals

Screen map: ADM-009Surface: AdministrationTemplate: StandardPageTemplateEntities: artifact, artifact_version, review_request, approval_request, impact_analysisStates: Draft, Review, Approved, Deprecated