Components and languages

Typed Wasm Component execution

The reference sandbox compiles and admits a Rust WebAssembly Component against pliego:build/transformer@0.1.0. The host instantiates it without ambient WASI, invokes the typed export, and emits a schema-valid build transform receipt over framed input and output digests.

cargo run -p pliego-cli --locked -- sdk test \
  fixtures/opensdk/rust-component/pliego-extension.json \
  --input fixtures/opensdk/transform-input.json \
  --format json

One contract, independent implementations

The conformance fixture implements the same bounded build transform in Rust, TypeScript, and Python process bridges plus the Rust Wasm Component. The gate runs each implementation twice and requires exact canonical result bytes across all four.

npm run check:opensdk:multilang

Rust Component

Reference sandboxed Component Model implementation

TypeScript

Conformance process bridge transpiled with esbuild and run on Node.js 20

Python

Independent conformance process bridge

Prove resource failures

The component gate also proves finite fuel exhaustion, wall-time interruption, memory rejection, output rejection, and receipt validation. Instantiation and invocation share one deadline, and each execution receives an isolated Wasmtime engine.

Know what the evidence means

This fixture proves protocol equivalence for one build transform. The TypeScript and Python bridges are native-trusted conformance implementations, not sandboxed Component Model SDKs. A third stable Component SDK still requires hosted cross-platform Component Model evidence.