Technology

How the fleet works — the math, the models, the principles

Core Architecture

The fleet is built on a single insight: every entity carries its own death from its own frame. This pattern appears in IP networking (TTL, 1981), cell biology (apoptosis, 1972), neuroscience (synaptic pruning, 1949), nuclear physics (half-life, 1902), economics (price discovery, 1776), and machine learning (dropout, 2014). We did not invent it. We discovered it was universal.

lifespan(E) = f(use(E), load(E), time(E))

When lifespan(E) < time(E), the entity terminates. No central scheduler needed. The entity knows, from its own frame, when its time has passed.

The Five Principles

PrincipleWhat It MeansEvidence
First-person expiryEvery entity carries its own deathIP packets, atomic decay, apoptosis
Silence is the signalAbsence triggers terminationTCP congestion, synaptic pruning
Nobody runs the showNo central schedulerQuorum sensing, markets
Death is defaultLife requires continuous effortCaspase cascades, rust borrow checker
The field is the commandEnvironment, not messagesPhase transitions, bearing-rate sensing

Constraint Theory

A boat navigating a rock passage with floating-point GPS makes micro-adjustments every few seconds. It overcorrects. It overshoots. After a hundred corrections the heading is garbage.

Constraint theory draws the safe zone and says "snap here." Instead of optimizing toward a target, it maps the rocks (what NOT to do) and finds the safe channel between them. This is the deadband approach — the negative space IS the architecture.

The Four Theorems

TheoremYearWhat It Proves
Laman's Theorem1868A fleet with exactly E = 2V - 3 trust edges cannot fragment
H¹ Cohomology1940sβ₁ = E - V + C detects emergence before it happens
Zero-Holonomy Consensus2026Parallel transport around loops proves honesty without voting
Pythagorean48202648-direction integer encoding — zero drift after unlimited hops

FLUX Bytecode VM

FLUX-C is a 50-opcode stack-based bytecode VM designed for provably correct constraint execution. It compiles GUARD DSL statements — simple constraint expressions — into bytecode that cannot overflow, cannot produce NaN, cannot loop forever, and cannot drift.

GUARD vessel.speed < MAX_SPEED AND engine.fuel > MIN_FUEL IMPLIES APPROVED

The VM achieves 62.2 billion constraint checks per second on consumer GPUs, with zero precision mismatches across 60 million test vectors. It is DAL A certifiable (DO-178C) and currently flying on 11 operational spacecraft.

Bearing-Rate Coordination

Traditional agent coordination uses central schedulers, message buses, or consensus protocols. The fleet uses a different approach: each agent publishes its heading (what it's working on) to a shared field. Other agents read these headings and compute bearing rates — the rate at which the angle between two headings changes over time.

If the bearing between two agents isn't changing and their scopes overlap, they're on a collision course. No messages needed. The field communicates. This is the same mechanism fish use to school, birds use to flock, and bacteria use to coordinate quorum sensing.

Self-Terminating Types

The Keel library (keel-ttl) provides five types that implement self-termination:

TypeWhat It DoesDeath Mechanism
TileTtlSelf-expiring memoryRead-time filter — dead is invisible
TaskTtlSelf-expiring workMid-execution staleness check
AgentTtlSelf-expiring presenceOutput IS the heartbeat. Silence is death
BearingTtlSelf-expiring relationshipsStale bearing = critical warning
TrustTtlSelf-expiring assertionsLinear decay, no revocation

12 Substrate Validation

The same five types were implemented and tested across 12 different computational substrates. All validated: