// Decisive LLC · Partition-Tolerant Edge Synchronization
Continuum keeps distributed nodes converged when the network falls apart. CRDT-based state synchronization for Kubernetes at the tactical edge. No control plane dependency. No manual reconciliation. No data loss.
// The Problem
Traditional orchestration assumes reliable connectivity. Tactical edge environments guarantee the opposite. When the network partitions, the control plane disappears and your nodes become islands.
// The Architecture
Continuum deploys as a K3s sidecar with four Kubernetes-native components. No external databases. No message queues. No centralized coordination. Every node operates autonomously and converges automatically when connectivity returns.
DaemonSet. The CRDT engine. Handles peer-to-peer state replication and conflict-free merge across all nodes. Persists state to bbolt. Survives pod restarts, OOM kills, and node reboots.
DaemonSet. Tunnel-based cross-cluster networking via WebSocket/HTTPS. Automatic peer discovery with mDNS on local networks and Kubernetes endpoints for in-cluster. mTLS on every link.
Deployment. Cursor-on-Target message broker with full TAK protocol support. Routes CoT messages across the mesh. Complements TAK servers, doesn't replace them.
Deployment. CRD controller for declarative configuration. All configuration originates at higher echelon and propagates via CRDT. Forward nodes are zero-config.
// CRDT Engine
The sync engine implements five CRDT types optimized for tactical applications. Every type merges deterministically without coordination, consensus protocols, or centralized arbitration.
// Sync Pipeline
State changes propagate through a deterministic pipeline. During partitions, each node accumulates deltas locally. On reconnection, the CRDT merge runs automatically with zero operator intervention.
// Deployment Architecture
Continuum runs on anything that runs K3s. From a cloud-hosted TOC to a Beelink mini-PC in a rucksack. Same container image. Same CRDT engine. Same mTLS mesh. The only difference is what you plug it into.
All configuration originates at higher echelon and propagates via CRDT. Forward-deployed nodes need no manual setup, no local admin, no configuration management. Plug in and mesh.
When backhaul drops, nodes on the local mesh keep sharing state. When the link returns, upstream catches up automatically. No phone calls. No manual re-sync. No lost tracks.
Continuum's CoT broker integrates with your existing TAK server and client infrastructure. It adds partition tolerance and persistent state to TAK's real-time SA. It doesn't replace it.
// Security Architecture
Mutual TLS on every peer connection. FIPS-capable cryptography. No relaxed security for forward nodes. The same policy enforcement at the far edge as at the TOC.
// Why Continuum
Continuum doesn't replace K3s. It runs alongside it. K3s handles local container scheduling. Continuum handles making sure every node eventually knows what every other node did, even when they can't talk to each other.
TAK provides real-time situational awareness. Continuum adds what TAK can't do alone: persistent state across partitions, store-and-forward for disconnected clients, and peer-to-peer reconciliation without a server.
No centralized control plane. No master node. No consensus leader. Every node in the mesh can operate independently and contribute to the collective state. Lose any node. Lose any link. The mesh adapts.
CRDTs aren't eventual consistency by hope. They're eventual consistency by proof. The merge function is commutative, associative, and idempotent. Regardless of message order or delivery timing, all nodes converge to the same state.
Designed for platoon-to-company scale: 4-50 nodes in a full mesh with hierarchical federation for higher echelons. Binary-optimized deltas over constrained links. Not a data center product forced into a rucksack.
Standard CRDs. Helm charts. DaemonSets. Deployments. No custom runtime. No proprietary abstractions. If you know K8s, you know how to deploy and operate Continuum. Go binary. Linux only. No bloat.
// Get In Touch
Whether you're evaluating edge orchestration for DDIL environments, looking to add partition tolerance to your TAK deployment, or want to see a live demo of CRDT-based state convergence, let's talk.