Anomaly Intelligence · COSRYX-WATCH + health heartbeat

Know why it failed, and before it fails.

Missions often go silent and nobody ever learns why. The health heartbeat sends a signed health receipt for each main subsystem every 5 to 10 minutes, via the orbiter to Earth. A degrading part shows up as a trend, and engineers can act while the rover is still alive.

Health heartbeatIn development
COSRYX-WATCHBuilt · Simulation-validated
Monitor figuresSimulated
00 The silent failure

When a mission goes quiet, the evidence usually goes with it.

A last telemetry frame rarely explains a failure. A trend does.

A Mars rover that landed in 2021 went silent about a year later. Orbiter imagery later found it on the surface, but the public still lacks a full account of why it stopped. That pattern is common across spaceflight: when contact ends, the record that would explain it often ends too.

The heartbeat changes what is left behind. Every 5 to 10 minutes the rover captures the health of its main hardware and software subsystems (power, thermal, communications, mobility, compute, instruments) and seals it as a signed health receipt, relayed via the orbiter to Earth.

If a part degrades, Earth sees it before the rover dies. Engineers can reassign the task to another unit, shed load, disable the failing function, or push a signed software update. And if the rover does go silent, the last receipts say where to look.

01 Heartbeat console

Six subsystems, one rhythm.

A sketch of the heartbeat workspace. All values are simulated; the feature is in development.

Health heartbeatSIM-MARS-07 · rover R1 · relay via orbiter ASimulated · In development
Subsystems Simulated
Power · battery78.4%
Thermal · core-12.4 °C
Comms · link margin6.1 dB
Mobility · wheel 41.47 A
Compute · memory errors2/h
Receipts since sol start88
Heartbeat feed Simulated
    Evidence Receipts
    H1Health receipt · every 5–10 min6 subsystems · Ed25519 + ML-DSA-65 · parent link
    H2Mobility trend · sol 1,150 → now212 receipts · draw +11% · limit not crossed
    H3Relay hand-off · orbiter ADSRP light-cone timestamp · 36 receipts
    Simulated: values are generated in your browser to show the design. The health heartbeat is in development and is not yet in the published test totals.
    02 One heartbeat, end to end

    Capture, sign, relay, trend, act.

    Heartbeat01 / 06
    01 · CAPTURE

    Health, on a fixed rhythm.

    Every 5 to 10 minutes the rover samples each main subsystem: power, thermal, communications, mobility, compute and instruments, hardware and software alike.

    02 · SIGN

    Each sample becomes a receipt.

    The sample is sealed with a sequence number and a parent link, and signed with Ed25519 and ML-DSA-65. A missing heartbeat is itself a visible gap.

    03 · RELAY

    Via the orbiter, to Earth.

    Receipts ride the next orbiter pass, forwarded hop by hop by DSRP. If a pass is missed, they wait sealed on board.

    04 · TREND

    Degradation shows before failure.

    On Earth, the anomaly layer compares each receipt with the history. A wheel drawing a little more current every sol is flagged long before it stalls.

    05 · ACT

    Four ways to respond.

    Reassign the task to another unit, shed load, disable the failing function, or push a signed software update. Each response is itself a receipt.

    06 · IF IT GOES SILENT

    Silence is now evidence.

    If the rover stops, the last unbroken run of health receipts says which subsystem was failing and when. The investigation starts from records, not guesses.

    03 What Earth can do with an early warning

    Act while the rover is still alive.

    REASSIGN

    Move the task

    Give the work to another rover, drone or instrument that is healthy.

    SHED

    Reduce the load

    Drive slower, on fewer wheels, or less often, to stretch a weakening part.

    DISABLE

    Turn it off

    Isolate the failing function before it takes others down with it.

    UPDATE

    Signed software

    Push a signed update; the rover receipts that it applied, and what changed.

    04 COSRYX-WATCH

    Conjunction and anomaly alerts, with proof of warning.

    COSRYX-WATCH is the COSRYX conjunction and anomaly alert product (33 tests; Built · Simulation-validated). Each alert is a receipt bound to the exact observations it was derived from, so an operator can later prove what was known, when, and who was told.

    Beneath it, COSRYX-SPACETRACE records the chain from sensor observation to conjunction alert to spacecraft action (29/29 tests; Built · Ground-demonstrated). SSA ACCOUNTABILITY turns that chain into liability evidence for satellite and debris-removal operators, in the international CCSDS format (34 tests; Built · Ground-demonstrated).

    ProductEvidence it producesTestsStatus
    COSRYX-WATCHConjunction and anomaly alerts bound to source observations33Built · Simulation-validated
    COSRYX-SPACETRACESensor → alert → spacecraft-action chain29/29Built · Ground-demonstrated
    SSA ACCOUNTABILITY"We warned you; the manoeuvre was safe": liability evidence in CCSDS format34Built · Ground-demonstrated
    COSRYX-HYBRID-01Replay mismatch quarantines a record before a clean compute receipt is issued24/24Built · definition-of-done sign-off pending
    Health heartbeatSigned subsystem health every 5–10 minutes, relayed via orbiterNot yet in published totalsIn development
    05 How the AI reads anomalies

    Flags with their receipts attached.

    BASELINE

    Learn normal from receipts

    Each subsystem's normal range is built from its own signed history, not from a vendor's dashboard.

    DRIFT

    Small changes, early

    Slow drifts across hundreds of receipts are flagged long before a hard limit is crossed.

    EXPLAIN

    Every flag cites

    A flag names the receipts that triggered it, so an engineer can check the evidence, not just the alarm.

    Status. The founder reports the heartbeat code was written around 27 August 2026. It is labelled In development and is not part of the 692 product tests until it has been tested and counted.
    06 Our own test bench

    Fault drills on a satellite we control.

    With a COSRYX-owned satellite, we can run our own payload tests: power-cycle the payload, check that it re-acquires the signal, and run controlled fault drills, with every step receipted.

    The plan is a 6U CubeSat, targeted about 18 months after radiation testing. It is at the planning stage, subject to funding and licensing. No launch contract is signed.

    Radiation testing (G3)Pending · next
    Own 6U CubeSatPlanning
    Second, larger CubeSatPlanning · funding-dependent

    A silent rover should still leave a record.

    07 Questions

    About anomalies and the heartbeat.

    Why every 5 to 10 minutes?

    Often enough to catch a trend well before failure, rare enough to fit relay budgets. The interval is a mission setting; receipts batch on board between passes.

    Is the heartbeat tested?

    Not yet in published form. It is In development and will be labelled differently only after its tests are run and counted.

    Which rover are you referring to?

    We describe the case neutrally: a Mars rover that landed in 2021 went silent about a year later, and the public still lacks a full account of why. The point is the missing evidence, not any agency.

    Can a heartbeat be faked?

    Each receipt is signed with two legs and chained by sequence and parent. A forged, missing or reordered heartbeat breaks the chain and shows.

    08 Pilot

    Give one asset a heartbeat.

    Start with simulated or historical telemetry, receipt it on a fixed rhythm, and see what the trends would have told you.

    Request pilot accessDigital twin