Atlas HydrationUnited States
Structured shellADM-007
Page guide
Execution Definition Detail

Who can do what? Which definitions, policies, and integrations power the operating system?

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
definition form

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

2
schema validation

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

3
dependency graph

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

4
output contracts

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

5
recommendation rules

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

6
version diff

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

7
approve/deprecate

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/execution-definitions/{executionTypeId}
Primary entities
artifact, artifact_version, execution, recommendation, approval_request, publishing_job
Screen states
draftvalidation errorapproveddeprecated

Primary actions

Navigation and exits

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.