Neon Law | Keep domain seams in Rust, where interest compounds

Keep domain seams in Rust, where interest compounds

The bet is not "write a service in Rust." Rust owns reusable domain systems: libraries, command-line tools, workers, editor integrations, tests, and — through Dioxus — the browser pages. The payoff is that each good decision reinforces the next one.

Presenter notes

The core claim for a Rust room is stronger than "Rust is pleasant" or "Rust is safe." The claim is that keeping domain seams in Rust changes the economics of a small team. A CLI can call the same validators as the website. A workflow worker can share the same state-machine types as the template authoring rules. The LSP can surface those rules in whatever editor a lawyer writes in. A release can ship one dated set of binaries, images, and editor assets. The ecosystem compounds when the domain seams stay in the same language long enough to reuse them.

That is why Rust owns Navigator's rules, workflows, storage, authorization, store, CLI, and — through Dioxus — the browser surface. navigator orchestrates machine-bound flows; there are no shell scripts and no Makefile. We do not win because we wrote more code than everyone else. We win when the code someone else wrote in the Rust ecosystem becomes a trustworthy brick in our law practice.

View all slides Open display