Examples

Complete, copy-pasteable deployments: the recipes, the plan, and the exact calls to get them onto a device over each control plane.

Everything here uses one fictional stack, built up across the pages: a time-series database, an HTTP API that depends on it, a telemetry agent, and a static web front end in a container. It is deliberately the shape of a real edge deployment rather than a hello-world.

• A service from a GitHub release

  One component, end to end: sign it, describe it, deploy it, verify it.

• A four-component stack

  Database, API, telemetry agent and a container front end, in the right order.

• Deploying over HTTP

  curl and keystonectl, including the recipe store and dry runs.

• Deploying over MQTT

  Exact topics and payloads, including shipping recipes and plan in one message.

• Updating over a metered link

  Ship a 34 MB release as a 1 MB patch: a delta server, a recipe, and what the agent does with them.

• Keeping an OT scanner's data fresh

  IEEE OUI vendor prefixes and a daily vulnerability feed, published signed and refreshed without restarting the scanner. {class=“children children-type-flat children-sort-”}

Conventions in these examples

• The agent runs with its working directory at /var/lib/keystone, so runtime/… paths below are relative to that.
• Recipes are named in reverse DNS (com.acme.api) and components get short names in the plan (api). The two are different things — see The four words.
• Where an artifact is downloaded, it is signed. Skipping that is a development shortcut, not a deployment pattern.