Definitions

A definition is the document that describes a business process. It names the records the work keeps, the operations that can be performed on them, the presentations — the screens the people involved use — and the integrations the work connects to. Everything Perstack runs comes from a definition.

In Studio, create the Definition identity with its kind, slug, and name, then author source revisions from the Definition detail page. Source and exact Agent/revision attachments are validated before an immutable revision is stored. You can use a plain-language description as an authoring aid, but a revision is still a structured source document: review it the way you would review a written procedure, checking its records, operations, and rules.

What it declares

A definition has four parts.

• Records — the things the process keeps track of, such as an invoice, a purchase order, or a support ticket, along with the fields each one carries.
• Operations — the actions that can be taken on those records, such as matching an invoice to an order or posting a payment.
• Rules — for each operation, whether it completes automatically, waits for a person, or is refused, and under what conditions.
• Presentations — the screens people use to see records, review what is waiting on them, and act on it.

An operation that is not in the definition does not exist as far as an agent is concerned. There is no fallback path and no way for an agent to invent one. See Operations and rules for how the platform enforces this.

Deployments

A definition is authored as immutable revisions. A Release selects exact Agent and Definition revision pins; a Deployment then pairs that Release with an existing Environment configuration revision. The sequence of Releases, Deployments, and Activations is the history of what each Environment ran.

To return to a known-good state, select its recorded revision pins in a new Release and promote that Release through a new Deployment. Releases, Deployments, and Activations are history; none is rewritten to make a rollback look like the original promotion.

To change a definition, see Revising a definition.

From definition to an active Environment

A definition revision on its own does not execute. Select it in a Release, submit a Deployment for a Project Environment, wait for the Deployment to become ready, and activate it. Only then do Agents start carrying out its operations and runs start landing on the record.

Deploying again does not rewrite an existing Release or alter a running revision. Create a new Release with new pins and promote it through the Environment lifecycle. What happens to work already in progress is covered in Revising a definition.

To see how a definition comes together for the first time, see Describing your work. To see what a deployed definition looks like in operation, see Agents and runs.