Models, assets and variables

Assets (Publish → Assets) are versioned files that ship beside the image without a rebuild: model weights, prompt files, rule sets. An asset item is an OCI artifact in any registry, public or private, or a Git repository; each version is a reference pinned to a digest, and the item has a latest pointer.

An app maps the items it needs to a directory and says what happens when one changes: nothing, restart the app, send it a signal (signal:HUP, USR1, USR2, TERM, INT, QUIT, WINCH) or run a command (exec:…, through /bin/sh, within two minutes). A release pins a version of each item, the latest at publish time unless you choose; an item marked optional may be left out.

The supervisor unpacks each version under <dir>/<item>/.versions/ and switches <dir>/<item>/current to it atomically, keeping the live version and two older ones. The app's apply order decides whether files land before or after the new image; a restart hook is skipped when the app is about to be restarted for the image anyway.

Variables come from two places: a channel (pinned with each promotion) and a fleet (applied live, winning by name). A fleet variable change restarts the app in place without a new release.