Glossary

broker

The Momotor Engine service that coordinates processing. It receives jobs, manages their state, and arranges for the required work to be performed.

recipe

The plan for a processing job. It defines which checklets should run, in what order, and which data they should receive. See the Recipe structure section for more details.

step

One named action in a recipe. A step runs one checklet with the options and dependencies configured for that action.

dependency

A relationship between steps that tells Momotor Engine that one step should use, wait for, or react to the result of another step.

option

A named setting passed to Momotor Engine, the scheduler, a tool, or a checklet through the recipe or config bundle.

configuration

Assignment-specific data used by a recipe, such as expected answers, limits, options, or supporting files.

config bundle

The bundle that carries assignment-specific configuration for a recipe. Its options generally override matching options from the recipe.

product

The material to process. In education this is usually a student’s submission.

result

The output produced by Momotor Engine, often including HTML feedback and other data that a user interface can display later in a separate application, like the Momotor LTI tool provider.

bundle

A structured package of Momotor data. Recipes, configurations, products, and results are all represented as bundles.

checklet

A usually small Python package that performs one concrete part of a recipe, such as checking files, running tests, rendering feedback, or calling an external tool.

client

A system that sends work to Momotor Engine. The Momotor LTI tool provider is one example of a client.

worker

An environment that runs the work requested by the broker. Different workers may have different tools available.

tool registry

A registry that helps checklets find external tools and helps the broker schedule work on workers that have the required tools.