> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rotastellar.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Operator Agent

> The execution layer for orbital compute — a pull-based agent protocol for running workloads on satellites

# Operator Agent

The RotaStellar Operator Agent is a lightweight runtime that executes compute workloads on satellites. It uses a **pull-based protocol** designed for intermittent connectivity — agents operate autonomously and sync with Mission Control during contact windows.

<Info>
  The Operator Agent is open source. See the [GitHub repository](https://github.com/rotastellar/rotastellar-agent) for the Rust SDK.
</Info>

## Architecture

```mermaid theme={null}
sequenceDiagram
    participant Agent as Satellite Agent
    participant API as Console API

    Agent->>API: POST /api/agent/register
    API-->>Agent: agent_id confirmed

    loop Every contact window
        Agent->>API: GET /api/agent/workloads
        API-->>Agent: pending workloads + events
    end

    Note over Agent: Execute workload steps locally

    Agent->>API: POST /api/deployments/{id}/events
    Note right of API: step.started, step.progress,<br/>step.completed, job.completed

    loop Periodic
        Agent->>API: POST /api/agent/telemetry
        Note right of API: heartbeat, resource usage
    end
```

The agent runs on the satellite (or in simulation on a development machine). It communicates exclusively with the Console API — there is no direct connection to the CAE planner.

## How It Works

1. **Poll** — Agent checks for pending workloads during contact windows
2. **Execute** — Agent runs workload steps locally on the satellite
3. **Report** — Agent streams execution events back to Console
4. **Telemetry** — Agent sends periodic health/status heartbeats

The protocol is pull-based by design. Satellites have intermittent ground station contact windows — typically a few minutes per orbit. The agent polls when connectivity is available, executes autonomously, and reports results on the next pass.

## Deployment Modes

| Mode        | Description                                                                                 |
| ----------- | ------------------------------------------------------------------------------------------- |
| `simulated` | Console generates events from CAE plan data. No agent involved. Good for testing and demos. |
| `live`      | Agent polls, executes, and reports events. Real or hardware-in-the-loop execution.          |

## Event Types

The agent uses the same event format as the [CAE simulator](/cae/understanding-plans). Events track the full lifecycle of a workload execution:

| Event                          | Description                                  |
| ------------------------------ | -------------------------------------------- |
| `job.accepted`                 | Workload received and queued                 |
| `placement.decided`            | Step placement decision (on-board vs ground) |
| `plan.created`                 | Execution plan finalized                     |
| `step.started`                 | Compute step begins                          |
| `step.progress`                | Progress update (25%, 50%, 75%)              |
| `step.completed`               | Compute step finished                        |
| `transfer.started`             | Data transfer initiated                      |
| `transfer.completed`           | Data transfer finished                       |
| `checkpoint.saved`             | State checkpoint persisted                   |
| `security.encrypted`           | Data encrypted                               |
| `job.completed`                | All steps finished successfully              |
| `job.failed`                   | Execution failed                             |
| `constellation.step_assigned`  | DAG step assigned to satellite               |
| `constellation.step_completed` | DAG step finished                            |
| `constellation.failover`       | Step failed, reassigning                     |
| `isl_transfer.started`         | ISL data transfer initiated                  |
| `isl_transfer.completed`       | ISL transfer done                            |
| `checkpoint.predicted`         | Hazard prediction generated                  |

<CardGroup cols={2}>
  <Card title="Protocol Spec" icon="file-contract" href="/agent/protocol">
    Full protocol specification with auth, lifecycle, and error handling
  </Card>

  <Card title="Constellation Execution" icon="satellite-dish" href="/agent/constellation">
    Multi-satellite DAG orchestration with ISL coordination
  </Card>

  <Card title="Rust SDK" icon="rust" href="/agent/rust-sdk">
    Build agents with the Rust crate
  </Card>

  <Card title="Quickstart" icon="bolt" href="/agent/quickstart">
    Run your first simulation in 5 minutes
  </Card>
</CardGroup>