Documentation

DOC / 17 / OPENSDK

OpenSDK preview

Install the public OpenSDK preview and understand admission, capabilities, effects, conformance, and its pending governance.

In this guideOpenSDK preview
Getting startedProject structureCLI referenceDeveloper loopIncremental buildsRouting and pagesRust viewsEvents and foldsSchemas and snapshotsHyphae verified syncTyped contentBrowser runtimeDOM ownershipNative runtime previewPortable deploymentFull-stack betaOpenSDK previewComponents and languagesBrowser framework conformanceTooling protocolCompatibility and deprecationAdaptive assetsArtifact trustRelease trustPerformance evidenceErrors and diagnosticsVoluntary telemetryBuild and deployCrates and APILicensing and policy

Install the OpenSDK public beta

pliego-sdk 0.4.0-beta.1 is public on crates.io inside the coordinated framework graph. Its conformance suites remain in the repository, and RFC-006/RFC-007 plus ADR-006 remain pending before stabilization.

toml
[dependencies]
pliego-sdk = "=0.4.0-beta.1"

Admit exact bytes before execution

An extension manifest declares its identity, exact entry points, OpenSDK API, compatible host range, required features, requested capabilities, and resource budgets. Admission verifies the component digest and policy before returning a ValidatedExtension typestate that a runtime can execute.

rust
use pliego_sdk::{CapabilityPolicy, ExtensionManifest, HostContract};
use semver::Version;

let manifest: ExtensionManifest = serde_json::from_slice(manifest_bytes)?;
let host = HostContract::preview(
    Version::parse("0.4.0-beta.1")?,
    CapabilityPolicy::deny_all(),
);
let validated = host.admit(manifest, component_bytes)?;

Broker effects and retain evidence

Non-deterministic work crosses EffectBroker only after both the broker and specific effect capabilities pass policy. Calls that reach the executor produce ordered SHA-256 receipts for success or error. Denials happen before execution and do not claim that an effect occurred.

Fuel and deadline
Bound computation and interrupt an expired invocation
Memory and output
Reject growth or results beyond the declared budgets
Effect receipts
Bind ordered operation, request, outcome, and response evidence
Ambient WASI
Not linked by the reference component host

Implemented does not mean stable

RFC-006 and RFC-007 remain Draft, and ADR-006 remains Proposed. The implementation is executable evidence for governance and external evaluation; incompatible changes may arrive in another preview protocol. None of this surface is labeled stable.