Westwind interfaces

Westwind is four repositories that agree on the files and protocols below.

westwind-pipelines

Python package and westwind CLI. Owns the pipeline schema, the board, element and model catalogs, the code generator, the MCP server, the offload server and the GitHub Actions workflow that builds firmware.

westwind-zephyr

Zephyr module. mpipe elements (ww_executorch, ww_preprocess, ww_postprocess, ww_offload, sources and sinks), the ww_result C API, samples and tests.

westwind

Web application deployed on Vercel. Flow editor, Blockly and code editors, builds through GitHub Actions, browser flashing, dataset and model browsers, downloads of the VS Code extension.

westwind-vscode

VS Code extension. Registers the Zephyr documentation MCP server and the Westwind MCP server, runs the CLI, and writes OpenCode configuration.

The catalogs in catalog/ and the schema in schema/ are the source of truth. The other repositories copy them at build time; they do not edit them.

These pages show doc/interfaces.rst and doc/deploy.rst from westwind-pipelines, copied into this application at build time.

• Pipeline file
  westwind.yaml, its sections and the schema.
• Placement
  Device, edge, cloud and split placement, and federated training.
• Compute
  Where the host-side work runs: local, compose, hybrid or Kubernetes.
• Running in containers
  Images, Docker Compose profiles, Kubernetes on Amazon EKS, hybrid sites and measured results.
• CLI
  The westwind command and its stages.
• MCP and editors
  The Westwind MCP server, the Zephyr documentation server, OpenCode and VS Code configuration.
• Firmware builds
  The GitHub Actions workflow, its inputs and the artifact manifest.
• Offload protocol
  HTTP and serial protocol of westwind serve, and result objects.
• C API
  ww_result and ww_on_result() for application code on the device.