Operator-signed cluster
Bootstrap tokens, membership grants, capability checks, and versioned configuration gossip establish who may join and what each node may do.
FIELD SYSTEM / 07RUST · HYBRID PQC · ADAPTIVE DEFENSE
THE PATH
IS ALLOWED
TO BURN.
Imperium is an adaptive defensive VPN cluster that assumes routes will fail, protocols will be fingerprinted, and recovery must be automatic—but never silent.
ATOM COMPOSITIONNO ACTIVE SOURCE DEPENDENCY
SPIDERWEB FABRICNOT CURRENTLY IMPLEMENTED
HYBRID CRYPTOGRAPHYCLASSICAL + POST-QUANTUM
INTERNAL COORDINATIONTYPED IMPERIUM BUS
LIVE EXPLANATION / FAILOVERFive nodes.
Five nodes.
No sacred route.
Trigger a path burn, watch relay transport take control, restore the quarantined path as standby, or force double degradation to see Imperium fail closed.
IMPERIUM CLUSTER / SIMULATIONSTEADY
CYAN / DIRECTACID / RELAYRED / DEGRADED
01 / THREAT SIGNAL02 / PROMOTE STANDBY03 / HEAL + SELF-TEST04 / FAIL CLOSED
5 / 5MEMBERS APPROVED
20DIRECTED SESSIONS
2RELAY FALLBACKS
5 / 5HARDENING PROFILES
254WORKSPACE TESTS PASS
Fresh local proof: all 254 workspace tests pass, including cluster-VPN, seeded hardening, unauthenticated-probe, burn-and-loss, closed-loop signature, and emergency-shutdown paths. Simulation assertions are not public-network throughput claims.
SYSTEM SHAPEHybrid in two
Hybrid in two
different senses.
Cryptography combines classical and post-quantum primitives. Transport combines an active path with a warm standby. Neither use of “hybrid” means Atom composition or Hybrid DB.
Hybrid-PQC sessions
X25519 is combined with ML-KEM-768 for key exchange; Ed25519 is combined with ML-DSA-65 for dual-signature identity and control messages.
Adaptive mesh paths
Direct UDP, STUN mapping, bounded coordinated probes, MASQUE and peer relay fallback give each peer more than one route through hostile network conditions.
Fail-closed transport
An active transport and warm standby are watched by deterministic orchestration. A burned path triggers promotion and healing; double degradation triggers emergency shutdown.
DYNAMIC VPN SECURITYTraffic refuses
Traffic refuses
to hold still.
Imperium changes the path, protocol role, traffic shape, key epoch, and response surface according to bounded policy. Probabilistic sensors can raise evidence; deterministic mechanisms own the action.
MEASURE SCORE MORPH REKEY STRAIN QUARANTINE HEAL OR KILL
Traffic morphing
Bounded padding shapes, deterministic jitter, cover-traffic budgets, and packet-batching windows alter the observable traffic profile without allowing an unbounded overhead policy.
Three-trigger rekey
Profiles can rotate key epochs by age, byte volume, or a threat signal. Stagger windows keep a cluster-wide change from becoming a synchronized fingerprint.
Burn-aware path hopping
Candidates are scored from latency, jitter, loss, handshake reliability, relay cost, and burn state. Dwell windows prevent frantic route flapping.
Probe illusion space
Authenticated-first gates keep untrusted probes away from the real endpoint. Shadow endpoints or decoy transcripts rotate personas, enforce per-source budgets, then degrade to silent drop.
Leak guard
DNS and route violations engage a kill-switch state and preserve the reason, so a collapsed tunnel cannot quietly become an ordinary network path.
Composable strainers
Timing, byte-jitter, truncation, and two-stage authentication-shape filters compose deterministically. They deform reconnaissance without placing a model in the packet path.
Sensor agreement
A signature match is deterministic ground truth; two agreeing sensors can burn a route; a lone high-confidence classifier narrows traffic through a strainer instead of receiving unilateral control.
Operator-approved signatures
Rejected traffic can produce a deterministic candidate rule, but promotion stays staged. The operator approves, rejects, or rolls it back while bundled and extracted defenses remain separate.
Dormant forensics
Diagnostics and emergency snapshot tools remain budget-gated and dormant until a high-confidence threat or double degradation requests them through the bus.
CONTROL BOUNDARYTHE MODEL MAY OBSERVE. IT DOES NOT OWN FAILOVER, KEY ROTATION, MEMBERSHIP, SIGNATURE PROMOTION, OR THE KILL SWITCH.
Bus-driven.
Not yet Spiderweb.
Imperium crates communicate through a typed, prefix-subscribed in-process bus. That is a strong coordination layer, but the active source does not yet implement Spiderweb’s four elevations, emergent threads, intersections, ramps, preloading, or vibration-driven rerouting. Publishing it separately keeps both architectures honest.
net.cluster.* net.mesh.* net.transport.* net.sensors.*One Rust workspace. One runtime. Operator-gated membership. Hybrid-PQC sessions. Adaptive routes. Deterministic failover. Emergency shutdown when trust in the path collapses.