██╗ ██╗ ██╗ ███╗ ██╗ ██████╗ ██╗ ██╗ ██╗ ██╗
██║ ██║ ██║ ████╗ ██║ ██╔══██╗ ██║ ██║ ╚██╗ ██╔╝
██║ █╗ ██║ ██║ ██╔██╗ ██║ ██████╔╝ ███████║ ╚████╔╝
██║███╗██║ ██║ ██║╚██╗██║ ██╔══██╗ ██╔══██║ ╚██╔╝
╚███╔███╔╝ ██║ ██║ ╚████║ ██║ ██║ ██║ ██║ ██║
╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚═╝ ╚═╝ ╚═╝ ╚═╝ ╚═╝
Systems developer · Rust
📍 Rouen, France
Still no mana, still no power — but the systems keep converging.
I build systems that don't need permission to exist.
Distributed protocols, CRDTs, event ordering - infrastructure where there's no central authority and every node figures things out on its own. Rust is my primary tool for that.
When the project needs it, I go wider: Go, Python, React, Kubernetes, Flutter. But the core stays low-level and built to run without coordination.
convergent |
Composable CRDTs for decentralized systems — GCounter, PNCounter, LWW-Register, OR-Set |
hlc_id |
Hybrid Logical Clock IDs for distributed event ordering |
json_cleaner |
CLI tool to strip null/empty values from JSON — on crates.io |
convergentuseshlc_idunder the hood for causal timestamps. They're designed as an ecosystem.
architecture shapes responsibility.
If this way of thinking resonates — follow along.



