⌕◔
Atlas HydrationUnited States
Structured shellWS-122
Page guide
QA Review Editor

What exactly was produced? What source evidence supports it?

Home/Workspace/QA Review Editor
WS-122 · WorkspaceEditorPageTemplate

QA Review Editor

Edit, review, and approve qa review editor content inside the unified Workspace shell.

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
checklist

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

2
automated findings

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

3
evidence

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

4
pass/fail

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

5
revision request

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

6
partial approval

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

Governed component composition

WorkspaceShellTabsInspectorPanelStickyActionBarStateBadgeArtifactHeaderArtifactSectionEvidencePanel

Expected data

Primary endpoint
/v1/artifacts/{artifactId}
Primary entities
artifact, review_request, approval_request
Screen states
drafteditingreviewrevision requestedapprovedlocked

Primary actions

Open ArtifactidOpen ArtifactidOpen Artifactid

Navigation and exits

LIB-006
Artifact DetailPermanent artifact record with metadata, current version, preview, status, source, approvals, lineage, use, performance, and actions.
->WS-123
Version Compare & ReconciliationCompare versions, AI output versus director-edited content, internal versus live, or client feedback versus draft, and reconcile selected changes.
->WS-124
Change Impact ReviewShow downstream artifacts, executions, live assets, and performance analyses affected by a proposed or approved change.
->

Acceptance criteria

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