SLEEVECAST
The Fleet and lifecycle
The Fleet page lists every sleeve of your organization on every Dock, from what each Dock last reported. It refreshes every few seconds.
Statuses
| Status | Meaning |
|---|---|
| Idle | Running and waiting for work. |
| Working | In the middle of a task; the task id is shown. |
| Guarded | Its last task stopped on a guard (iterations, tokens or time). Clears with its next task. |
| Needlecasting | Starting: pulling, verifying or booting the runtime. |
| Resleeving | Moving to a new version or a fresh container. |
| Unresponsive | The container runs but the sleeve has not reported while working. |
| Degraded | A new version failed to start; the previous one keeps running. |
| Flatlined | The container failed to start or keeps crashing; the error is shown. |
| Dormant | Stopped on purpose. |
When a Dock goes offline, its sleeves show their last known status with a note.
Actions
Operators and above can act on a sleeve from the Fleet or its page:
| Action | What happens |
|---|---|
| Halt | Stops the current task now. The sleeve stays running and takes the next one. |
| Resleeve | Replaces the container with a fresh one from the same spec. Memory stays; a task in flight is lost. |
| Stop / Start | Stops the sleeve until you start it again. Memory stays on the Dock. |
Architects and Owners also manage specs:
- Apply moves a placed sleeve to another saved version (newer or older).
- Place puts a stack on a Dock; Unplace removes it from that Dock.
- Delete removes a stack that is not placed anywhere.
Every action is recorded in the organization's audit log.
Roles
| Role | Can |
|---|---|
| Viewer | See the Fleet, specs, events, traces, memory and cost. |
| Operator | Also halt, resleeve, stop, start and message sleeves. |
| Architect | Also write specs, place and apply them, and enroll Docks. |
| Owner | Also manage members, the plan and API keys. |