# Deployment

The Passenger application remains isolated at `control.aijoost.com`. Deploy
and verification use only:

```text
sudo /usr/local/sbin/aijoost-ops check
sudo /usr/local/sbin/aijoost-ops deploy
```

The dashboard consumes a sanitized qualification evidence file. It cannot
start, resume, cancel, or enqueue a worker.

## Optional persistent worker activation

`scripts/worker-daemon.mjs` and `scripts/activate-worker.sh` are reviewed,
fixed-path, non-root activation artifacts. The daemon uses the private
workspace spool, restores unfinished metadata, and refuses any UID except
1005. Activation was not performed because it is not part of the exact
restricted wrapper and no durable user service is currently available.

If the owner chooses qualification-only daemon activation, the exact command
is:

```text
sudo -u aijoostops /home/aijoostops/workspaces/aijoost/scripts/activate-worker.sh
```

This does not authenticate root, edit sudoers, or grant new authority. It is
not a reboot-persistent service; a future owner-approved user service should
replace it.
