Documentation menu

Documentation

Build protected functions for your calculations and business checks. Configure who may run them, which inputs they may use, and what results may leave.

Start hereOverviewStart with one approved function: what Standard manages, what owners control, and how the receiving integration verifies the permitted result.
Conversation analyticsThe conversation-categories example: protected input, duplicate-ID validation, permitted counts, recipient verification and publication policy.Write a protected functionTurn required calculations and business checks into an accepted Wasm function, test its behavior, and verify its permitted result.Sources and customer vaultsConnect supported data sources, keep control of keys and API secrets, and authorize protected retrieval and processing.How Standard worksHow customer-defined functions, operation profiles and owner permissions work together, from protected inputs and execution to results with Standard Proof.Run your first taskFollow Conversation analytics from an approved function and conversation batch to verified counts and a separately authorized report update.Join a SpaceReview the proposed work, authorize your contribution, and choose what may be released, without joining another organization’s account.ExamplesExplore Conversation analytics and separate examples for release verification, diagnostics, supplier assessment, model scoring and joint analytics.Software release verificationA separate example: validate a candidate artifact with approved checks, verify the findings and enforce deployment policy.Operation profilesDefine the program, participant roles, inputs, permitted outputs, and execution limits.Inputs and permissionsHow encrypted inputs and key access work, how each required owner authorizes independently, and how each operation is approved when it is requested.Results and lifecycleAutomatic verification and result delivery, approval requests, failures, retries and cleanup status.Integration referenceReference for Standard’s Control transaction, CLI, MCP transport, application bindings, participant custody, and execution evidence.Threat model and AI risk mappingHow Standard’s execution controls and approved customer functions address specific threat scenarios using MIT’s risk and mitigation taxonomies.Security modelHow scoped authority, confidential ingress, protected execution and Standard Proof govern sensitive work.