v0.4.0 — M4 cluster + multi-platform
THALIOX is now an operating system for a distributed society of agents. This release completes the H1 software arc through M4.
Highlights since v0.1.0
- M2 microVM-ization — one-command deploy + snapshot/restore + self-update rollback; the agent runs inside a real Firecracker microVM (vsock deploy, VM snapshot/restore), validated on KVM bare-metal. (RFC-0004)
- M3 multi-instance HA — per-field CRDT merge,
Node+migrate, and aSupervisor(heartbeat → self-heal → reconcile). (RFC-0005) - M4 cluster + multi-platform (RFC-0006):
- fabric —
VectorMessagetransport between agents (in-process) and across nodes (TCP), INV-2/INV-3 enforced at the boundary. - cross-host live migration validated on two KVM machines — at both process-level and microVM-level, covering the full {VM, host-process} × {VM, host-process} migration matrix.
- teams in four paradigms — Pipeline / Hierarchy / Market / Swarm — with INV-2 on every cross-member hop and INV-3 on every agent's input.
- cluster front door — the
apigateway generalized: one capability-based authorization model (INV-2 at the door), an SSE streaming surface, and peer routing for a fleet across nodes.
- fabric —
INV-2 and INV-3 hold between agents and at the cluster door — the team/cluster boundary is not a hole in the invariants.
All four CI gates green: fmt · clippy -D warnings · test (103) · doc -D warnings.
Next: M5 learned control plane (RL scheduling + a supervisor agent + self-optimization — "AI manages AI").
Full roadmap: docs/MASTER_PLAN.md · Cluster design: docs/rfcs/0006-cluster-multiplatform.md