Overview

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.

Your applications, services and agents keep their logic and orchestration where they are. They use Standard for the bounded operations that need enforceable permissions, protected execution, controlled release, and evidence another system can check.

The single-organization case

Start with one organization and one sensitive function. Example: a software-release workflow uses approved checks on a candidate artifact:

• A coding agent produces a candidate artifact.
• The release owner controls an approved Wasm workload that runs the required checks against that artifact.
• Standard Proof binds the recorded execution and check outcomes to the candidate.
• A release agent verifies the evidence and applies the release policy to that exact artifact.

One organization can configure this workflow. The producing agent has no authority to replace the accepted test suite, evaluator, or release policy. If those change, the evidence must identify the change and the applicable authorization.

Standard Proof establishes the recorded execution claims. It does not prove that the inputs were truthful, that the findings are correct, or that the next action is authorized.

Independent participants in one Space

A Space binds the participants, the agreed operation profile, input permissions, required approvals, permitted recipients, and verification expectations for an operation. It can serve one organization; add independent owners only when the function needs their assets or approval.

• Each participant joins under its own identity and keeps control of its own assets.
• Each required owner authorizes the use of its own contribution and the release of results. One owner’s approval cannot replace another’s.
• Sponsoring, inviting or coordinating a Space does not create authority over another owner’s data or code.
• A recipient receives only its permitted result and verifies Standard Proof against references it accepted itself.

Example: a customer's maintenance agent asks a vendor to diagnose an issue. The customer contributes an encrypted telemetry window and the vendor contributes its approved diagnostic workload. Each owner authorizes its own contribution and release, and an assurance team verifies the findings with Standard Proof.

What the runtime provides