Mission Health · Founder's flagship · Status as of 21 October 2026

Know why it failed. Before it fails.

Every 5 to 10 minutes the rover captures the health of its main hardware and software subsystems and sends a signed health receipt via the orbiter to Earth. If a part degrades, Earth sees it while there is still time to act.

CadenceEvery 5–10 minutes
PathRover → orbiter → Earth
Each beatSigned · chained
StatusIn development
01 The problem

Missions go silent, and nobody ever learns why.

Spacecraft and rovers fail far from help. Too often the last thing anyone knows is that the signal stopped. Engineers reconstruct what they can from the final passes, and the full cause is never established.

One example: a Mars rover that landed in 2021 went silent about a year later. Orbiter imagery later located it, but a full public account of why it stopped has not been published. That is not a criticism of anyone; it is what happens when health data arrives too late, too sparsely, or not at all.

The health heartbeat is our answer: a small, regular, signed statement of how the vehicle is doing, so the trend is visible before the end, and the record survives if the end comes anyway.

02 How the heartbeat works

Five steps, every five to ten minutes.

Health heartbeat · simulated01 / 05
01 · CAPTURE

Read the main subsystems

Power, thermal, communications, mobility, compute and instruments: a compact summary of each, plus the software state that runs them.

02 · SIGN

Seal it as a health receipt

The summary becomes a receipt, signed twice and chained to the previous heartbeat. A missing beat is as visible as a bad one.

03 · RELAY

Rover to orbiter to Earth

The receipt goes up to an orbiter on its next pass and down to Earth. If no relay is in view, the beats are stored and forwarded later, in order.

04 · SEE THE TREND

Earth watches the slope, not the cliff

A battery that holds a little less charge each sol, a motor drawing a little more current: small drifts across hundreds of beats show a failure coming.

05 · ACT

Respond while the rover can still listen

Reassign the task, shed load, disable the failing function or push a signed software update, and every one of those actions is receipted too.

03 What each beat carries

Six subsystems, summarised small.

POWER

Energy

Battery state of charge and health, solar or generator output, bus voltage, and how load is shared.

THERMAL

Temperature

Key component temperatures and heater duty, the early sign of a failing heater or a cold night that ran long.

COMMS

Link

Radio health, recent pass quality and the size of the store-and-forward backlog.

MOBILITY

Motion

Motor currents, wheel and joint state, and any slip or stall events since the last beat.

COMPUTE

Software

Processor load, memory errors corrected, resets, and the version of every running component.

INSTRUMENTS

Payload

Whether each instrument is on, idle or faulted, and its own health flags.

04 The cadence

Why five to ten minutes.

Often enough that a degrading part leaves a clear trail of readings before it fails; rare enough that the heartbeat stays a small fraction of the link budget and of on-board energy.

The interval is a mission setting, not a constant. A rover in a dust storm may beat less often to save power; one under investigation may beat more often. Each change of cadence is itself recorded.

Because each beat names the one before, Earth can tell the difference between "the rover was healthy and quiet" and "beats are missing". Silence stops being ambiguous.

05 What Earth can do

Four responses, all signed.

01

Reassign the task

Move the work to another unit, another instrument or another rover in the same mission.

02

Shed load

Switch off non-essential consumers so a weakening battery lasts through the night.

03

Disable the function

Turn off the failing function before it takes something healthy down with it.

04

Push a signed update

Send a software fix as a signed intent; the rover applies it only if the signatures check.

06 A worked example

A battery, caught early.

An illustration of how the heartbeat changes the story. Simulated, not a real mission.

Beat 1,200

All subsystems nominal

Power reads normal. The chain is unbroken.

Beat 1,480

A small drift in power

End-of-night charge is a little lower than the week before. Nothing alarms; the trend is noted.

Beat 1,640

The rover keeps working

With load shed, the battery holds. If it fails later, the cause is already on record.

07 One health receipt

Small, signed, chained.

An illustrative health receipt. The real format is defined by the mission; the shape is always the same: summary, previous beat, two signatures.

// illustrative health receipt (simulated values)
{
  "type":    "health.beat",
  "unit":    "rover-02",
  "beat":    1610,
  "power":   { "soc": 0.41, "trend": "falling" },
  "thermal": "nominal",
  "comms":   { "backlog": 12 },
  "compute": { "resets": 0, "sw": "edge-2.4.1" },
  "prev":    "sha256:a7f3…09c1",
  "sig":     { "ed25519": "…", "mldsa65": "…" }
}
09 Honest status

In development.

The founder reports that the heartbeat code was written around 27 August 2026. It is not yet part of the published test totals: the 692 product tests and 410 integrated tests on this site do not include it.

Until it has its own tests, gates and evidence, its status is In development. The scenes on this page are simulated illustrations, not telemetry from any real vehicle.

Nothing here describes the heartbeat as flown, flight-qualified or externally audited.

10 Questions

About the heartbeat.

Doesn't a rover already send telemetry?

Yes, and the heartbeat does not replace it. It adds a small, regular, signed summary that cannot be quietly edited and whose gaps are visible, so the health story survives even when the full telemetry does not.

What if the orbiter is not in view?

The beats are stored and sealed on board, then forwarded in order at the next pass.

Can a bad actor fake a healthy beat?

Not without the rover's signing keys. Each beat is signed twice and chained; a forged or replayed beat would fail verification.

When will it be tested?

It needs its own test suite and gate review first. We will update this page and the newsroom when that changes.

11 Talk to us

Working on a mission that cannot afford to go quiet?

We are interested in research partners with real telemetry to test against.

ContactPartnerships