Operation profiles
Define the program, participant roles, inputs, permitted outputs, and execution limits.
An operation profile defines one kind of work: the approved Wasm workload, required roles and inputs, limits, and what may be released to whom. Code, data, or model inputs must fit that workload and the supported runtime limits. The profile declares the work; it grants no access to data, code, tools, or recipients. Each owner authorizes its own part separately.
The Conversation analytics profile shows each part highlighted. The example gallery also includes separate release, diagnostics and multi-owner profiles.
Function logic, profile boundaries and owner authority
The function contains the calculations, validations and decision rules. Its code defines the order of checks and the reports produced when checks pass or fail. The profile binds that accepted program to named inputs, resource limits and permitted outputs. Each required owner separately authorizes the use of its assets and result release.
Rule configuration supplied as input is part of the accepted input contract: bind the expected revision or digest alongside the program. Requests are checked against the accepted workload and scope. See Write a protected function.
The parts of a profile
| Part | What it defines |
|---|---|
| Program | The approved Wasm module the profile accepts, referenced by content hash. |
| Roles | The participant roles the work needs. Each role is filled by its own owner, and a profile can require that two roles are held by different principals. Declaring a role grants nothing. |
| Inputs | The slots each role contributes through. A participant contributes only through its own role’s slots; declaring a slot grants no access. |
| Steps | The program step that runs and which slot feeds each of its inputs. |
| Output contract | Each output that may be released, the recipient roles that may receive it and its size bound. Release still needs the owners’ authorization. |
| Limits | Memory, fuel, time and size bounds for the operation and each step. The runtime enforces them. |
Example: the input owner accepts conversation-categories, the batch-042 input selection, execution limits and category-count release to the Analytics integration. The Analytics agent requests that operation but cannot change the accepted scope.
When a function needs an independent owner, the same profile model names that owner's contribution and authority. Example: vendor diagnostics combines the vendor's approved program with the customer's telemetry window. The customer receives permitted findings and the vendor receives a narrower service summary.