Let’s follow step by step how this magic happens:

(1)‍ ‍This is your normal copper stack

(2) This is your normal .copper onboard logging system. This becomes optional if you rely fully on this log streaming feature.

(3) You can set the series of minimal inputs to deterministically anything coming downstream of those input.

(4) Copper will stream its copperlists with FEC, it is done by sending after the fact error packet corrections for the past packets.

(5) Twin Copper decode, fix, reorder the stream from the lossy connection based on the redundancy in the protocol

(6) What if really we miss too much? No worries your stack can send recovery points (that are themselves self healing) to jump restart at any point your twin.

(7) Twin Copper stack is now exactly what is running your robot!

(8) You can log a standard .copper deterministic log

(9) You can build a full Telemetry display to expose exactly what is interesting for you operationally to watch: could be messages, task states, error states, even tasks fields or structured logging exactly like any locally running copper!