Interoperable
Workflows do not belong to one model, agent, vendor, or runtime.

A standard, three native SDKs, and Praxis—the AIWS workflow engine—for building governed, observable AI workflows across agents, tools, humans, and systems.

The complete stack
Shared semantics connect what you define, what developers build, and what the runtime executes.
Interoperable contracts, workflow semantics, governance rules, and an evidence model.
Read the Standard ↗02Native TypeScript, Python, and Rust APIs built from the same closed wire records.
Explore the SDKs ↗03The AIWS workflow engine: durable orchestration, recovery, scheduling, handoffs, controls, and operator evidence.
Understand Praxis ↗Governed execution
Every stage has a defined shape, authority boundary, and durable record.
Human authority
Approval gates, permissions, intervention, recovery, and uncertainty handling are part of the workflow—not exceptions bolted on afterward.
Explore authorization and controlNative SDKs
Three independent libraries implement the same finite-v1 profile and share exact conformance scenarios.
# Install the native TypeScript SDK
npm install ./aiws-sdk-0.3.0.tgz
# Run the verified first workflow
node examples/guide/typescript/first-run.ts# Install the native Python SDK
python -m pip install ./aiws_sdk-0.3.0-py3-none-any.whl
# Run the verified first workflow
python examples/guide/python/first-run.py# Build the native Rust SDK
cargo build --locked
# Run the verified first workflow
cargo run --manifest-path examples/guide/rust/Cargo.toml --bin first-runWhy a standard?
Agents, orchestrators, tools, and runtimes describe work differently. That makes governance, portability, recovery, and trustworthy evidence harder than they need to be.
AIWS defines shared semantics for how AI-powered work is described, executed, controlled, resumed, verified, and recorded.
Workflows do not belong to one model, agent, vendor, or runtime.
Execution survives pauses, retries, failures, and long-running work.
People can inspect, approve, intervene, and retain authority.
Every run produces structured state, events, evidence, and history.
Permissions and policies constrain what agents are allowed to do.
Acceptance conditions and evidence—not a completion claim—close the work.
Start building
Start with the standard, choose an SDK, and run your first governed workflow.