What an artifact is

A versioned, signed file the fleet can push to nodes — a fine-tuned model, an app bundle, a firmware image, or a config. On upload the mainframe fingerprints it (SHA-256) and signs it with the fleet's private ed25519 key. This is just the library; nothing is sent to a node until you queue a Job.

What you need

• The file to distribute.
• A Type (model · app · firmware · config) and a Version tag (e.g. 2026.07.03).
• Optionally a Format hint so the node's executor knows how to apply it — e.g. ollama-modelfile, gguf, app-bundle.
• Each node must have the fleet's public signing key pinned (provisioned at install). Without it a node refuses every artifact.

How to use it

1. Choose a Type, then fill in Version, Notes (changelog), and a Format hint.
2. Pick the File and click Upload & sign. It appears in the table below.
3. For a model, click Make production to mark it as the fleet's current model (PROD).
4. Go to Jobs to push it to a node, a ring, or the whole fleet.

Safety

Before applying anything, a node re-checks the SHA-256 checksum, verifies the ed25519 signature against its pinned key, and enforces a 1 GB size cap. Anything that doesn't verify is refused.

What a job is

A job pushes one signed artifact — or a command — to a target. Nodes never accept inbound connections: each node pulls its queued jobs on its next check-in (every ~15 s) and applies them locally, then reports the result back.

What you need

• At least one enrolled node (see Enroll a node).
• For model / app / firmware / config jobs: an uploaded, signed artifact (see Artifacts).
• For a command job: no artifact — just an action in Params.

How to use it

1. Pick a Type. For everything except command, choose the Artifact to send.
2. Choose a Target: a specific node, a ring (a group tag set when a node is enrolled — e.g. default), or the entire fleet.
3. For a command, add Params JSON — e.g. {"action":"ping"}.
4. Click Dispatch job, then watch its status in the list below.

Job status

queued waiting to be pulled · dispatched handed to the node on check-in · applied verified & ran · failed node refused / couldn't apply · cancelled · rolledback

A node only applies a type it has an executor for (and only if the signature verifies). The built-in command executor handles action: "ping" / "noop"; model/app/firmware executors run on nodes provisioned for them.