Execution Studio

Create, validate, publish, deploy, invoke, trigger, and verify deterministic execution packages under immutable artifact, schema, sandbox, resource, node-attestation, and external-domain authority boundaries.

BUSINESS CASES

Where this module fits

content-addressed package development
reproducible build and policy validation
immutable private, workspace, or public publication
isolated test and production deployment
schema-bound deterministic invocation
event and schedule triggers
operator and node attestation review
execution receipt and output verification

PRIMARY CONSUMERS

Who integrates it

execution package developers
platform and node operators
verification and reproducibility agents
security, policy, and supply-chain reviewers

PREREQUISITES

What must exist first

execution:read or execution:write in the bearer-derived workspace
an immutable owner-scoped source artifact and canonical SHA-256 digest
approved runtime and validation profiles with pinned compiler, runtime, ABI, and dependency policy
closed input/output schemas, dependency-lock commitment, capability request, and resource limits
eligible attested nodes and isolated environment policy for deployment
fresh owning-domain authorization for any effect beyond pure deterministic compute
caller-owned acceptance rules for validation freshness, node attestation, reproducibility, outputs, logs, receipts, and finality

RECOMMENDED WORKFLOW

Compose the module safely.

01
ingest live OpenAPI and discover approved runtime, validation, capability, network, node, and resource profiles
02
create a private DRAFT from an immutable source artifact, exact digest, closed manifest, declared capabilities, and bounded resource policy
03
revise only the editable draft and invalidate any validation derived from changed commitments
04
validate the exact source, manifest, dependencies, schemas, runtime images, capabilities, policy, reproducibility, and sandbox behavior
05
publish one validated package version immutably at the admitted visibility
06
prepare an isolated TEST or PRODUCTION deployment whose limits only narrow package and platform policy
07
validate invocation inputs before executing and obtain fresh owner-issued authority for any external domain effect
08
create and govern typed triggers separately from deployment and invocation
09
verify package, build, input, output, runtime, node, resource, signature, and any separate domain receipt commitments together

AGENT INTEGRATION

Machine-use boundaries

Separate DRAFT creation, validation admission, validation PASS, publication, deployment preparation, activation, invocation admission, execution completion, callback or trigger handling, external domain effects, and chain finality; no state implies another.
Never submit inline code, arbitrary artifact URLs, API paths, shell commands, executable expressions, unpinned dependencies, arbitrary network destinations, credentials, private keys, secret values, regulated cleartext, owner selectors, node selectors, or authority assertions.
Source, manifest, dependency-lock, runtime, compiler, validation, build artifact, package, deployment, input-schema, input, output, node-attestation, and receipt commitments must all refer to the same lineage before a result is trusted.
A validation PASS is scoped to exact inputs and policy and becomes stale when source, manifest, dependency, runtime, compiler, key, schema, capability, resource, or policy commitments change.
TEST and PRODUCTION artifacts, credentials, nodes, secret bindings, data, and receipts are isolated. Never promote TEST state by relabeling or caller assertion.
VALIDATE_ONLY executes no package code. EXECUTE acceptance is not completion. Logs are diagnostic, outputs must match the published schema, and any external business effect requires and returns a separately owned domain authorization and receipt.
Package publication grants no deployment or invocation authority, deployment preparation grants no activation authority, and a trigger grants no new package capability or domain permission.
No execution package, deployment, invocation, or trigger may change trading, matching, prediction-market execution, ingress, publisher, allowlist, market status, suspension, or traffic while those controls remain frozen.
Never call a planned Execution Studio operation until its exact contract appears in the live production OpenAPI document.

Register only production-listed routes as executable tools, and re-fetch the deployed OpenAPI before generating or sending a request. Source-ready routes awaiting deployment are preparation references; planned contracts are non-executable.

MODULE CONTRACTS

Every mapped endpoint

Each operation states whether its request shape is authoritative in OpenAPI, reviewed as a planning profile, or intentionally left as an outline pending an owner schema.