# Recipe and Execution Context

Canonical URL: https://babadook.tech/sub-modules/maxacor-recipe-context
Entity: sub-modules
Content hash: 5f6610190bf7b3de04031f915b2eec0aee69ba672beee33e5477f9d062560d3f

Connect recipe, parameters, materials, tooling and approved configuration to the physical run.

A batch starts only after the current recipe, equipment and material context agree. Teams can prove which instructions governed each output.

## What changes

A batch starts only after the current recipe, equipment and material context agree. Teams can prove which instructions governed each output.

### data Viz

### data View

section: operating-scene

## Operational boundary

- **What it does:** Connect recipe, parameters, materials, tooling and approved configuration to the physical run.
- **What the team gains:** Teams can prove which instructions governed each output.
- **What it does not own:** Recipe approval does not directly command equipment.
- **section:** operational-boundary

## Recipe and Execution Context

action: Connect recipe, parameters, materials, tooling and approved configuration to the physical run.

mechanism: A batch starts only after the current recipe, equipment and material context agree.

workflow role: A batch starts only after the current recipe, equipment and material context agree.

operational outcome: Teams can prove which instructions governed each output.

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

Recipe approval does not directly command equipment.

## Relationships

### products

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

### modules

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