# Computer lifecycle

Provision, run, stop, retire and release a computer with clear state transitions.

Status: Management job foundation implemented · Physical controller pending

## Keep the operations separate
| Operation | Intended effect | Storage effect |
|---|---|---|
| End agent run | Stops that task's actions | Does not delete files or browser state |
| Disconnect viewer | Ends the human connection | Desktop may keep running |
| Shut down guest | Stops processes and normal RAM state | Persistent disk stays |
| Reset workspace | Rebuilds a clean workspace | Deletes the selected tenant state under the agreed policy |
| End rental | Revokes access and starts retirement | Cleanup and any approved retention follow |
| Release machine | Returns verified clean capacity | Only after cleanup verification |

## Provisioning
The reservation is transactional. A lifecycle job requests provisioning and waits for a controller acknowledgement. Retrying must reuse a stable operation ID. A timeout means the state is uncertain; it is not proof that the operation never happened.

## Suspension and revocation
An expired or suspended account loses API access immediately in the management service. The desktop worker must additionally revoke guest/streaming credentials and terminate established sessions. Until that is confirmed, the platform must show pending revocation and keep the host out of available inventory.

## Restart and reset
A restart must not be sold as a secure erase. Reset is a separate destructive operation requiring the owner’s explicit intent and a verified cleanup procedure. Reset cannot ignore snapshots, backups, temporary exports, logs or a valid preservation hold.