Capability surfaces

Bring your own connector. Bring your own language.

The AuthoredComponent implementation source is language-agnostic by design. WIT (WebAssembly Interface Types) under wit/worlds/connector/ is the single source of truth for contracts. Any language that compiles to the Wasm Component Model can author a connector — Rust, C, AssemblyScript, Go, Python (via py2wasm), anything else. Built-in native, declarative bundles, and authored Wasm components are indistinguishable at the router.

Three peer implementation sources

BuiltInNative · DeclarativeBundle · AuthoredComponent. All canonical.

BuiltInNative

First-party CLR class. Database providers, distribution connectors, runtime fabric — everything Vadyl ships natively. Implements the canonical capability declaration directly.

DeclarativeBundle

JSON manifest interpreted by the canonical declarative engine. The language-free path — for connector authors who don't need code execution. Validated against WIT contracts at build time.

AuthoredComponent

Wasm Component Model artifact compiled from project source. Multi-language: Rust, C, AssemblyScript, Go, Python via py2wasm. Indistinguishable from built-in at the router — same descriptor, same router, same registry.

The build pipeline

Hermetic. Deterministic. Signed.

Hermetic build

Vadyl.Connectors.Build runs DeclarativeBundleBuildAdapter — no network, no ambient env, deterministic re-build. Same inputs always produce the same artifact.

WIT validator

Every connector contract is validated against the canonical WIT world. Method shape mismatches, missing host imports, type incompatibilities — all caught before the artifact is signed.

Manifest validator

Capability declarations are validated against the WIT world they target. A connector cannot claim a capability the world doesn't expose. Schema-first, fail-closed.

Canonical conformance suite

Built-in test battery every authored connector runs against — round-trip semantics, error contracts, edge cases. Pass to publish. Never optional.

IKeyRing-signed artifacts

KeyRingBackedArtifactSigner produces a signed wasm-component-v1 artifact. The runtime verifies the signature before execution. Tampered artifacts cannot run.

WasmConnectorKernel

Wasmtime 34.0.2. Epoch deadlines per invocation. Per-invocation Stores so memory cannot leak across calls. The same kernel runs every authored connector regardless of source language.

19 host-import kinds

Bounded surface. Six families.

CapabilityHostImportKind enumerates exactly what an authored connector can import from the host: 9 memory operations, 2 observability operations, 5 secret operations, 1 egress-plan operation, 1 time operation, 1 capability operation. Six families, 19 kinds, closed by construction. A new host import requires a canonical addition — there is no escape hatch.

3
Implementation sources

BuiltInNative · Declarative · Authored Wasm

5+
Authoring languages

Rust · C · AssemblyScript · Go · Python

19
Host imports

6 families, closed by construction

Indistinguishable
At the router

Authored = Built-in to consumers

Author the connector in the language you already use.

WIT contracts. Hermetic build. Canonical conformance. IKeyRing-signed artifacts. Wasmtime kernel with epoch deadlines. Capability-bounded by construction.