Execution Registry
Browse, filter, create, version, approve, deprecate, and validate execution definitions.
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
Review whether this region belongs on the page, where it should appear, and what decisions it must support.
Review whether this region belongs on the page, where it should appear, and what decisions it must support.
Review whether this region belongs on the page, where it should appear, and what decisions it must support.
Review whether this region belongs on the page, where it should appear, and what decisions it must support.
Review whether this region belongs on the page, where it should appear, and what decisions it must support.
Review whether this region belongs on the page, where it should appear, and what decisions it must support.
Review whether this region belongs on the page, where it should appear, and what decisions it must support.
Governed component composition
Expected data
- Primary endpoint
/v1/admin/health- Primary entities
- artifact, artifact_version, execution, approval_request
- Screen states
- approveddraftdeprecatedinvalid
Primary actions
Navigation and exits
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.