Terms with one clear meaning.

Business processes written in plain language, versioned, approved and executed directly by the platform.

The approved object that carries flow, data, rules, interfaces and version control for a running process.

The execution-time control layer that checks the actor, process state, data state and rule version before an action updates a system, sends a notification or advances a case.

A packaged executable business capability, not a template. It contains the process definition, rules, interfaces and integration shape needed to run.

The controlled movement of a process version from design or test into production according to the organisation's approval rules.

The evidence attached to a process run: definition version, rule version, actor, data state, attempted action and outcome.

The customer's choice of hosted or self-hosted provider options configured for the customer environment. Automation may assist, but rules bind execution.

The existing enterprise system that remains authoritative for a data object. FlowMaster reads it in place and writes back when the process permits.

The translation and annotation layer that maps raw database schemas to plain-business-language terms, allowing AI agents and rules to query databases without hardcoding API endpoints or schema keys.