Skip to main content

Anduril Lattice

Lattice is the taskable antenna and the common operating picture; Constellation is the judgment. A bridge you run next to Lattice pulls workflow forecasts and puts them on the map as a forecast layer, and decides ReservePass tasks on an antenna by its forecast. Delivering to Lattice needs the Enterprise plan.

ConstellationIn Lattice
Each antenna a workflow sends this bridge forecasts forA forecast service named Constellation forecast · <antenna>, never the antenna itself. Its asset panel lists the antenna's next passes with their expected GB, and raises an advisory for each of the two soonest passes below the workflow's floor.
The same forecast serviceA taskable agent for ReservePass
Each listed forecast passA line along the ground under the satellite from AOS to LOS, named with its expected GB, expiring 2 minutes after LOS
A rain-fade swap advised for one of the antenna's passesA caution alert on its forecast service naming the backup and the cancel deadline, and a hazard circle over the station until the pass's LOS
A swap approved in ConstellationA warning alert (CONSTELLATION_SWAP_APPROVED) naming the backup and the cancel deadline; a ReservePass task for that pass is denied SWAP_APPROVED until the cancel deadline
Swaps held for approval in ConstellationA status row counting them on the antenna's forecast service
A ReservePass task for a pass forecast at or above the floor (p10)STATUS_DONE_OK
A ReservePass task for a pass below the floor, or none forecastSTATUS_DONE_NOT_OK with ERROR_CODE_REJECTED and a diagnostic, such as EXPECTED_GB_BELOW_FLOOR: p10=3.1 GB < min=5.0 GB

Every decision is the task's status.result: a one-line summary with the decision, p10, p50 and p90, the floor and any rain-fade advice. The bridge never re-tasks after a refusal: the Lattice operator decides.

Your own stations and satellites are never doubled. The bridge publishes forecast services, not antennas, and draws stations and satellites only when you turn that on for an empty sandbox.

Run it with Docker Compose​

The bridge is one container you run anywhere that reaches both Constellation and Lattice, outbound only. Run one per Lattice environment: two at once both receive every task and race to decide it.

  1. Download compose.yaml and .env.example from bridges/lattice/deploy/ in the connectors repository, at the tag of the release you run, and save .env.example as .env beside the compose file.
  2. Fill in .env: CONSTELLATION_API_KEY (a live key with predictions:read and config:read), LATTICE_URL and LATTICE_TOKEN, and LATTICE_SANDBOX_TOKEN in Lattice Sandboxes only.
  3. docker compose up -d. docker compose logs -f shows it reading results.

The compose file pins the image ghcr.io/constellationhq/lattice-bridge at the version it was released with, keeps the bridge's state on a named volume at /var/lib/constellation, and marks the container unhealthy after 2 minutes without progress. For an enterprise API, set CONSTELLATION_API_URL in .env. Compose reads .env on every later up, restart or recreate, so nothing needs exporting in the shell.

The two decision settings have defaults, and the bridge's first log line says which values it uses, marking the defaults:

VariableDefaultMeaningChange it when
MIN_P10_GB0The expected GB p10 floor a ReservePass decision uses for an antenna no workflow has forecast yet; a workflow's own floor wins once it forecasts the antennaAntennas without a forecast should refuse low-yield passes
MAX_FORECAST_AGE_S21600 (6 hours, one weather-model cycle)The oldest forecast, in seconds since its run was made, a decision may use; an older one is denied with STALE_FORECASTYour workflows run less often than every 6 hours, or you want fresher forecasts only

A value that is not a number at least 0 stops the bridge at start.

Lattice credentials stay with the bridge; Constellation never receives them. The image runs as a non-root user (amd64 and arm64). Without Docker, set the same variables and run constellation bridge run lattice with the Python SDK and its [lattice] extra installed, or python3 lattice-bridge.pyz from Downloads, with Python 3.11 or newer.

VariableValue
CONSTELLATION_API_URLDefault https://api.constellation.space. Plain http only to this machine (localhost): the bridge stops at start rather than send the key over plain http to another host.
CONSTELLATION_API_KEYA live key with predictions:read and config:read. The bridge reads your antennas from GET /topology/config.
LATTICE_URLhttps://<environment>
LATTICE_TOKENThe environment's bearer token ("Lattice Auth Token" on the environment page)
LATTICE_SANDBOX_TOKENLattice Sandboxes only: the account bearer token (Sandboxes portal, Account & Security)
CONSUMERThis connection's name. Default lattice-bridge.
MIN_P10_GB, MAX_FORECAST_AGE_SSee the table above
TASK_TYPEThe task type antennas advertise. Default type.googleapis.com/google.protobuf.Struct; the registered ReservePass once you push it.
POLL_SECONDSHow often it reads results. Default 15.
STATE_DIRWhere the bridge keeps its state. /var/lib/constellation in the image, a volume; outside it, $XDG_STATE_HOME/constellation, or ~/.local/state/constellation when XDG_STATE_HOME is not set.
CURSOR_FILEWhere it keeps the last results position it applied and the forecast it holds. Default lattice-bridge-cursor.json in STATE_DIR.
PUBLISH_STATIONS, PUBLISH_SATELLITES, PUBLISH_COVERAGEtrue only where Lattice holds none of your own stations or satellites, such as an empty sandbox. Default false.

Its state​

The bridge keeps its results position and the forecast it holds in CURSOR_FILE, on the state volume, so a recreated or upgraded container resumes there and shows and decides as before. A first start, or one without that file, applies only the newest run for its connection, never the history; each other workflow's forecast arrives with its next run.

The compose file's health check reads STATE_DIR/heartbeat; the bridge touches it only after a poll whose runs it applied and Lattice took, so the feed down, a run it cannot apply, or Lattice refusing what it publishes turns it unhealthy. It reads your network config again every 10 minutes, so new stations and antennas become taskable without a restart.

The startup check​

On start the bridge reads your network config from Constellation and lists one Lattice Object, which Lattice answers only for the right LATTICE_URL and a token it accepts. It exits with code 2 and one line saying what to fix when:

  • a required variable is missing, or MIN_P10_GB or MAX_FORECAST_AGE_S is not a number at least 0,
  • CONSTELLATION_API_URL is plain http to another machine,
  • STATE_DIR is missing or not writable,
  • PUBLISH_SATELLITES is on and sgp4 is not installed,
  • Lattice rejects the token,
  • LATTICE_URL answers 404 or another 4xx.

When either side is down, or answers 5xx, it logs and retries, backing off up to 5 minutes, and never exits. When Constellation refuses the key, or answers 429 or 402, it says why once and waits (15 minutes for a refused key), so a restart loop never locks out the address. After an exit, fix what the line names in .env and run docker compose up -d again.

Send a workflow to Lattice​

On Integrations, Results out, choose Add connection, then Anduril Lattice (or open its row once it is in Connections). Under Send, pick the workflow and choose Send Pass yield to Anduril Lattice (the button names both): it saves a new version of the workflow with the output, wired from the step that feeds /predictions. Its connection is lattice-bridge, and its settings are the Lattice mapping:

SettingMeaning
min_p10_gbThe floor: a ReservePass for a pass below this many GB at p10 is refused
passes_listedHow many passes each antenna lists
advisoriesWhether rain-fade swaps ride along as alerts
pass_entitiesWhether forecast passes are their own entities on the map
antennasWhich antennas it covers, 1 to 500; leave it out for every antenna the run forecasts

Send a rain-fade-swap workflow to the bridge as well so swap advice reaches the antennas. A swap run is its workflow's whole advice for its window: it replaces what that workflow advised before, and one advising nothing takes it down.

ReservePass​

Each forecast service takes ReservePass tasks over Lattice's agent stream, with the fields satelliteId and, optionally, aos. A decision uses the floor of the workflow whose forecast it used, and records it.

When the workflow's advisories is on and a swap of the pass was approved in Constellation, the task is denied SWAP_APPROVED with the backup to book until the swap's cancel deadline: a person has decided that pass is not to be flown. The bridge still books nothing. Swaps held for approval are counted in a status row on the antenna and do not change a decision.

Until you register the ReservePass type, create tasks through the Tasks API with the specification {"@type": "type.googleapis.com/google.protobuf.Struct", "value": {"satelliteId": "...", "aos": "..."}}. The Lattice UI shows a Struct task without a form.

To give operators a ReservePass form under Assign Task, register the type in the Lattice Schema Registry. This needs a Lattice Developer login:

  1. Sign in to https://schema-registry.developer.anduril.com and create a repository lattice in your organization. A package must be <org>.<repository>.<package>.<version>: if your organization is not constellation, rename the package in bridges/lattice/proto/constellation/lattice/tasks/v1/reserve_pass.proto in the connectors repository (and its directory) and the module in bridges/lattice/proto/buf.yaml to match.
  2. From bridges/lattice/proto/ in the connectors repository: export BUF_TOKEN=<token>@schema-registry.developer.anduril.com, then buf push.
  3. Within 15 minutes the type reaches Lattice. Run the bridge with TASK_TYPE=type.googleapis.com/constellation.lattice.tasks.v1.ReservePass (your package, if renamed). Tasks of either type are decided the same way.

How it fails​

  • The bridge exits with code 2. Its last log line says which variable, key or URL to fix.
  • A task fails at once with "asset is offline". No bridge is connected for that antenna. Check the bridge is running.
  • A task fails with UNMARSHAL_ERROR ... not found. Lattice does not know its type. Register ReservePass, or send a Struct task.
  • An output to lattice-bridge without a Lattice mapping is a Yamcs output, so the bridge skips it, logs it and reports it as refused.
  • Lattice Sandboxes environments last at most 12 hours, 2 hours idle, so a sandbox URL and token change with every new environment.