Appendix 2: network isolation (air gap) and synchronisation by mobile courier
The Cube never touches a cloud. The proof is carried out from the field.
On an isolated or sensitive site, an authorised user's secured smartphone carries the signed audit log out of the site — and nobody along the way can alter it.

The Cube decides locally and stores its telemetry and its signed audit logs as signed, versioned packets. If your site must remain strictly isolated from the network (air gap), no network exit path exists. Instead, an authorised user's phone acts as a trusted courier, based on their movements in and out:
On entry: When this person enters the zone and proves their identity (hardware challenge-response, identity consent on the smartphone), the Cube hands over the outgoing packets over an encrypted Bluetooth link, signed by the Cube. The courier thus carries the data without being able to alter it: the slightest change would be detected by the server.
On exit: When the phone later regains connectivity, it sends the packets to the server over an encrypted, authenticated connection. Signed acknowledgements and new signed policy sets travel the opposite way with the next authorised carrier. Every step is recorded in the app's transfer log.
In the app
For the carrier, the courier role comes down to one screen. The Sync tab shows what there is to carry, and the transfer log, on the Cube's detail screen, records every step of the journey: from the server to the app, from the app to the Cube, then the other way round for the logs. A line is written only once the recipient has acknowledged receipt: with no network, that is the proof nothing was lost along the way.


Screenshots taken in demonstration mode with fictitious data; the app interface is currently in French.
