DataBorder · patent pending
A ring of blocks around the edge of the frame carries live values, strings, and trends in the video stream. Wherever the video goes, the data goes with it.
01 The ring
The camera draws a thin ring of blocks around the picture and writes the data into it. It is part of the image, so it is encoded, recorded, exported and played like the rest of the frame. The ring carries everything on this page.
02 Survival
The data is in the pixels, so every copy and clip of the video carries it. Second-generation copies, downscaled and re-encoded, decode in full.



03 Values first, then a carousel
The values that changed go in every update. The space left over is a carousel with layers, each turning at its own pace. Names and context come round every few seconds, recent history over a minute, and the camera's stored history over longer. Clip a minute and the values arrive with their context. Clip a few minutes and the history comes with them.

Alongside the values, the ring carries the names of every record, the camera's identity and its state labels, recent history, the strings that were live, the signatures, and the camera's stored history for clips long enough to carry it. Which layer carries what is in the DataBorder docs.
04 Trust
Every update links to the one before it, and the camera signs the chain with a key that never leaves the device. Cut a clip, splice two together or change a value, and the chain breaks at exactly that update. The decoder shows where.
Signed, chained, decoded, tampered, gap. The decoder marks every span of a clip, so you know what came from the camera untouched and what did not.
05 Adaptive format
The ring thickness is a camera setting. A thicker ring carries more per update, and a thinner one takes less of the picture. Whatever the size, the DataBorder fits its carousel to the ring: live values first, then as much context and history as there is room for.