Reference
Glossary
The words this manual uses, each with the page that explains it.
| Term | Meaning |
|---|---|
| Aggregation | A structural link: an object consists of parts. |
| Agent link | A person object taken by a human process: that person carries it out. |
| Attribute | A named field of an object, with a definition agents follow. |
| Board | The canvas a flow is drawn on; a flow process has one of its own. |
| Branch | A run's git branch, which its agents and scripts work on. |
| Change request | A reviewer's instructions and the reviewed work, given to the process that revises it. |
| Condition | A link from a state: run only if the object is in it, and be skipped otherwise. |
| Consumption | A link that uses the object up: once taken, it is gone. |
| Copy | An object that follows a struct or a procedure's object, changing only with its source. |
| Cursor | A stored object a flow carries from run to run, such as when it last fetched. |
| Decision | An agent or a person setting the state of an object. |
| Duplicate | A step that generated a unique value another run already stored; its run ends terminated. |
| Effect | A process that takes and yields the same object, changing it. |
| End | The node marking what a flow leaves; a procedure's outcomes. |
| Entry | A human process that has a person fill an object in. |
| Event | A link from a state: the object entering it triggers the process. |
| Exhibition | A structural link: an object exhibits an attribute. |
| Flow | Something your team does, drawn so it can be run. |
| Flow process | A process made of a board of processes of its own. |
| Follow-up | A message sent to a finished agent step, continuing its session. |
| Generalization | A structural link: an object is a kind of another. |
| Instrument | A link to an object the process needs but does not change. |
| List | An object holding several items, as a JSON array. |
| MCP server | A server of tools an agent may use, connected per person. |
| Object | Something that exists, holding JSON; drawn with square corners. |
| OPL | The Object-Process Language: the board written as sentences. |
| OPM | The Object-Process Methodology, ISO 19450: the language flows are drawn in. |
| Pass | A sweep of a run in which each process runs at most once. |
| Person | An object standing for who carries out human processes; its name is a role. |
| Procedure | A flow other flows run as a step, as a run of its own. |
| Process | Something that happens: a step, drawn rounded. |
| Quorum | Needs: run once this many inputs exist, rather than all of them. |
| Query | An input link that takes the records earlier runs stored of an object, not the object in this run. |
| Recording | A flow process whose every run, per item, is a run of its own. |
| Records | What a stored or shared object keeps from runs that ended done; a shared struct keeps one set for every flow. |
| Re-run | A new run from one process of an ended run, with what came before copied. |
| Review | A process that takes an object and decides its state, leaving its content. |
| Role | Permission to decide the reviews a person object of that name handles. |
| Rounds | How often an agent reviewer may send work back before that fails it. |
| Rule | A condition on an object's fields saying when it is in a state. |
| Run | One execution of a flow. |
| Schedule | A cron expression and time zone that start runs on their own. |
| Shared | A struct whose copies, in every flow, read and write the same records. |
| Start | The node a run begins at, pointing at the first process. |
| State | A situation an object can be in; states route the flow. |
| Step | One process carried out once in a run. |
| Struct | A single object defined once for many flows to use. |
| Subflow | A procedure process: a step that runs a procedure. |
| Unique | An attribute no two stored instances may share, used to skip work already done. |
| Version | A saved snapshot of a flow's whole board. |
| Workspace | A run's checkouts of the flow's repositories, on its own branch. |