Overview
Start with one approved function: what Standard manages, what owners control, and how the receiving integration verifies the permitted result.
Standard is a managed confidential execution service: approved Wasm workloads start just in time inside an attested trusted execution environment, scoped authority and release rules stay outside the caller, and each permitted result includes Standard Proof.
Keep planning and orchestration in your existing applications, services and agents. Move selected calculations, validations and business rules into approved functions in Standard. The caller requests the work; the accepted function performs the processing, while owner permissions and release rules govern access and disclosure.
Four protections
- Authority outside the agent. Owners control which functions may run, which inputs they may use and which results may be released. Standard enforces those permissions independently of the requesting agent.
- Restricted Wasm execution. Functions use declared input and output interfaces with enforced resource limits. They receive no general shell, filesystem, subprocess or network interface.
- Confidential execution and key custody. Functions run inside an attested TEE that protects code and inputs during execution. For supported vault and KMS connections, your non-exportable master encryption keys remain in your store. Authorized confidential components may use temporary data keys and connector credentials for permitted processing.
- Proof before the next step. The receiving integration verifies Standard Proof against the expected operation before it accepts the result. The workflow then evaluates the outcome and enforces permission for the next action.
Start with Conversation analytics to see the complete explanation, then Run your first task for the setup sequence. The separate function authoring guide explains the Wasm interface using a sales calculation.
The single-organization case
Start with one organization and one approved function: Conversation analytics.
- The Analytics agent requests category counts for the approved
batch-042selection. - The input owner authorizes
conversation-categories, that batch and permitted-result release to the Analytics integration. - The approved classifier processes the conversations inside the protected runtime.
- The Analytics integration verifies Standard Proof before making the permitted counts available to the agent.
- The reporting workflow applies its own publication policy.
The illustrative counts are Coding 420, Writing 310, Research 190 and Other 80. The requesting agent does not receive the raw conversations or source credentials. Changing the input, function or recipient needs applicable owner authority.