Frame Chains

Self-healing, leader-redundant orchestration of a distributed AI estate via signed content-addressed frame chains · Kody Wildfeuer · RapterBox LLC · 2026

AI agents pile up on devices the way services once piled up on servers — organically, unwatched, drifting. Frame chains keep a whole fleet healthy as verifiable state on an append-only chain: no central server, no elections, no clock agreement. Proven on a real eight-device estate — including ordering that shrugged off a 17.6-second clock disagreement, because the chain is the clock.

#0 genesis is a1b2c3… #1 holds a1b2c3… is d4e5f6… #2 holds d4e5f6… is 7a8b9c… #3 next… holds 7a8b9c…
The whole idea in one picture: every frame contains the fingerprint of the one before it — order is structural, not claimed.
Read the paper GitHub

Play with the ideas (no coding required)

⏱ The Chain Is the Clock

Two machines whose clocks wildly disagree write to one story. Drag the skew — the order never breaks. Why timestamps were never the boss.

🛰 Scan Tiles & the Healing Loop

Ask one question of a whole fleet with a single frame, watch the answers link back, then heal only what changed — and watch the estate go quiet on its own.

👑 Succession Without Elections

Knock out the leader. Nobody votes, nobody panics: ranks wait their turn by rule, lag can't cause a coup, and history is never rewritten.

Run a sample

python3 samples/frame_chain.py — a ~120-line toy frame chain (real SHA-256, no dependencies): mint, append, verify, catch tampering, and merge two skewed-clock devices in chain order.