Prepare
Check and compile AWL locally, or build and package a Gleam project. Enable the server’s deploy surface and use a caller with deploy authority.
Deployment accepts documents, archives and directories. It prepares the entire local batch first. A local parse, compile, archive or duplicate-type error prevents all uploads.
Deploy `.awl` documents and `.aion` archives, singly or in batches (operator API).
aion deploy [OPTIONS] <PATH>... -
<PATH>... - `.awl` documents, `.aion` archives, or directories (walked recursively for both). At least one
-
--bind <BINDING.awlb> - Compose each AWL source with this venue binding before deployment. Archives cannot be bound; every local refusal precedes upload
-
--dry-run - Prepare everything locally, ask the server what it already holds, and report what the batch would change. Uploads nothing
-
--fail-fast - Stop at the first archive the server refuses; later entries are reported as not attempted. Without it every archive is attempted. An unreachable server always stops the batch
-
--max-inflated-bytes <BYTES> - Optional byte ceiling for each locally expanded archive, including archives built from AWL. An archive above the ceiling is refused before upload. Omitted means unbounded local expansion.
Uploads then proceed in path order. A server refusal can leave earlier entries deployed; read every entry in the batch report. Dry-run still reads the server’s current state, although it uploads nothing.
A worker document explicitly named as a deploy input is refused by family. Directory discovery reports worker documents as skipped instead, because they supply implementations rather than workflow entries.
Read versions
List every loaded workflow version with its routing flag (operator API)
aion versions [OPTIONS] -
--workflow-type <WORKFLOW_TYPE> - Show only versions of this workflow type
Persisted archives and routes survive restart. Boot restores versions required by routes and active runs. Before reopening a failed run, confirm its pinned archive is available.
Change routing
Re-point routing for a workflow type at an already-loaded version (rollback / roll-forward; operator API)
aion route [OPTIONS] <WORKFLOW_TYPE> <CONTENT_HASH> -
<WORKFLOW_TYPE> - Logical workflow type
-
<CONTENT_HASH> - Content hash of the already-loaded target version
Choose a loaded hash from the version reading. Routing back changes new starts. Existing runs retain their pinned code and history.
Unload
Unload a non-routed, unpinned workflow version (operator API)
aion unload [OPTIONS] <WORKFLOW_TYPE> <CONTENT_HASH> -
<WORKFLOW_TYPE> - Logical workflow type
-
<CONTENT_HASH> - Content hash of the version to unload
A routed or pinned version cannot be unloaded. Resolve the refusal instead of deleting its package record from storage.
Bound venues
A bound source creates a venue-distinct type and records both source and binding source record. Use the venue command to see which deployed venues lag the newest source deployment.
Which venues run each role-bound flow, and which are BEHIND the newest source deployed for it (operator API).
aion venues [OPTIONS] [FLOW] -
[FLOW] - Show only venues of this flow
Read package identity before using a content hash as evidence.