Standard
  • Docs
  • Examples
  • Pricing
  • About

Get started

  • Overview
  • Conversation analytics
  • How Standard works
  • Run your first task
  • Connect
  • Join a Space

Build

  • Authoring · Sales calculation
  • Examples
  • Software release verification
  • Operation profiles
  • Integration reference

Concepts

  • Sources and customer vaults
  • Inputs and permissions
  • Accounts and billing
  • Results and lifecycle
  • Verification checks
  • Follow-on tasks
  • Cleanup

Security

  • Security model
  • Threat model and AI risk mapping
Documentation menu

Get started

  • Overview
  • Conversation analytics
  • How Standard works
  • Run your first task
  • Connect
  • Join a Space

Build

  • Authoring · Sales calculation
  • Examples
  • Software release verification
  • Operation profiles
  • Integration reference

Concepts

  • Sources and customer vaults
  • Inputs and permissions
  • Accounts and billing
  • Results and lifecycle
  • Verification checks
  • Follow-on tasks
  • Cleanup

Security

  • Security model
  • Threat model and AI risk mapping
Standard

Managed confidential execution for approved functions.

© 2026 Standard Runtime, Inc. All rights reserved.

  • Security
  • Docs
  • Examples
  • Pricing
  • FAQ
  • About
  • Contact
  • Terms
  • Privacy
  • Cookies
  • Docs
  • Examples
  • Pricing
  • About
  • Get started

    • Overview
    • Conversation analytics
    • How Standard works
    • Run your first task
    • Connect
    • Join a Space

    Build

    • Authoring · Sales calculation
    • Examples
    • Software release verification
    • Operation profiles
    • Integration reference

    Concepts

    • Sources and customer vaults
    • Inputs and permissions
    • Accounts and billing
    • Results and lifecycle
    • Verification checks
    • Follow-on tasks
    • Cleanup

    Security

    • Security model
    • Threat model and AI risk mapping

    Get started

    • Overview
    • Conversation analytics
    • How Standard works
    • Run your first task
    • Connect
    • Join a Space

    Build

    • Authoring · Sales calculation
    • Examples
    • Software release verification
    • Operation profiles
    • Integration reference

    Concepts

    • Sources and customer vaults
    • Inputs and permissions
    • Accounts and billing
    • Results and lifecycle
    • Verification checks
    • Follow-on tasks
    • Cleanup

    Security

    • Security model
    • Threat model and AI risk mapping

    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

    PartWhat it defines
    ProgramThe approved Wasm module the profile accepts, referenced by content hash.
    RolesThe 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.
    InputsThe slots each role contributes through. A participant contributes only through its own role’s slots; declaring a slot grants no access.
    StepsThe program step that runs and which slot feeds each of its inputs.
    Output contractEach output that may be released, the recipient roles that may receive it and its size bound. Release still needs the owners’ authorization.
    LimitsMemory, 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.

    PreviousSoftware release verificationNextIntegration reference

    On this page

    • Function logic, profile boundaries and owner authority
    • The parts of a profile
    • Definition and configuration
    • Versions
    • From profile to operation
    • Related pages

    Definition and configuration

    A profile definition declares reusable work. A Space governance revision accepts an exact profile and binds the required owners, roles, and policies. An operation request supplies concrete participants and assets under those accepted rules. One owner cannot bind another owner’s role or assets.

    Versions

    Each accepted profile revision has exact provenance and a digest. Older revisions stay resolvable so a past result can be verified against the version it used. Changing the program, a role, an input, or an output requires a new revision and the affected owners’ authorization before use.

    From profile to operation

    A Space accepts an exact profile revision. An operation request proposes one instance: the program and input references, requested result, recipients, and resources. Standard checks it against the accepted profile, owner authority, supported formats, and account limits before admitting the operation. See Operation requests and Formats and limits.

    Related pages

    • Run your first task
    • Join a Space
    • Inputs and permissions