# Execution Run

Canonical URL: https://babadook.tech/sub-modules/maxacor-execution-run
Entity: sub-modules
Content hash: 2edd3f856366819347d25b41604c76358e64647f98285e7229e76a149249ba2b

Follow one physical run from admission through work, interruption, completion and evidence closure.

A run pauses after partial production and resumes without losing the units already transformed. Run status reflects physical evidence rather than a workflow terminal.

## What changes

A run pauses after partial production and resumes without losing the units already transformed. Run status reflects physical evidence rather than a workflow terminal.

### data Viz

### data View

section: operating-scene

## Operational boundary

- **What it does:** Follow one physical run from admission through work, interruption, completion and evidence closure.
- **What the team gains:** Run status reflects physical evidence rather than a workflow terminal.
- **What it does not own:** MAXACOR does not replace MES business ownership.
- **section:** operational-boundary

## Execution Run

action: Follow one physical run from admission through work, interruption, completion and evidence closure.

mechanism: A run pauses after partial production and resumes without losing the units already transformed.

workflow role: A run pauses after partial production and resumes without losing the units already transformed.

operational outcome: Run status reflects physical evidence rather than a workflow terminal.

maturity: specified

evidence: MAXACOR Part 9, §§12–19.

### Section 1

Operations team

### Section 2

Engineering team

### Section 1

Qualified physical state

### Section 2

Current work context

### Section 1

Evidence-bearing operational disposition

### Section 1

MAXACOR does not replace MES business ownership.

## Relationships

### products

- MAXACOR — https://babadook.tech/products/maxacor

### modules

- Recipe, Run and Process Execution — https://babadook.tech/modules/maxacor-recipe-run-execution