⌕◔
Atlas HydrationUnited States
Structured shellWS-123
Page guide
Version Compare & Reconciliation

What exactly was produced? What source evidence supports it?

Home/Workspace/Version Compare & Reconciliation
WS-123 · StandardPageTemplate

Version Compare & Reconciliation

Compare versions, AI output versus director-edited content, internal versus live, or client feedback versus draft, and reconcile selected changes.

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
side-by-side diff

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

2
field/section/image diff

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

3
accept/reject changes

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

4
conflict resolution

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

5
version metadata

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

Governed component composition

PageHeaderSearchFieldTabsDataTablePaginationBulkActionBarVersionTimeline

Expected data

Primary endpoint
/v1/artifacts/{artifactId}
Primary entities
artifact, artifact_version
Screen states
no diffdifferencesconflictreconciled

Primary actions

Open Artifactid

Navigation and exits

WS-005
Artifact Workspace ShellConsistent shell for any artifact with context navigation, specialized editor, review controls, comments, lineage, versioning, and downstream impact.
->WS-126
Approval DetailReview evidence, comments, diffs, risks, and approval policy before approving, rejecting, or requesting revision.
->

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.