Nirdosha is quietly shipping real compile-time guarantees for AI-written backend code — no GC, no data races, no deadlocks, and a growing plugin + concurrency story

Most “AI-friendly” languages still leave the hard safety questions for later. Nirdosha (निर्दोष — “without fault”) is built the other way around: the compiler proves a fixed set of faults are impossible today , so an agent can write and run backend code without a human reviewing every line first. What that means in practice right now: Affine ownership (box / &) — no GC, no manual free, no use-after-move No mutexes in the language at all → classic lock-order deadlocks are simply unexpressible A real dynamic stall detector that aborts global chan/thread deadlocks instead of hanging forever SMT-backed (Z3) integer/buffer-overflow proofs with a runtime-guard fallback Native LLVM codegen for the compiled subset (within ~1.4× of gcc -O2 on the scalar benchmarks they publish) An LL(1) grammar that is also exported as GBNF so an LLM sampler can be constrained to never emit invalid syntax The project has been moving steadily through a series of RFCs that are unusually concrete: RFC 0006 — structured concurrency pillars (evidence crate with 19/19 adversarial tests, real numbers, and a clear statement of what is still open) RFC 0008 — native plugin ABI widening past scalars + Cargo-metadata discovery so plugins stay compile-time only (statically linked, nothing loaded at runtime) RFC 0009 — grammar-of-graphics charts + compile-time UI-plugin components so the closed catalog can grow without opening a runtime hole Resource-control kernel work (boundary-leased admission, fail-open telemetry) with actual measured baselines against the existing runtime-kernels All of this is happening on a deliberately small surface: the interpreter path has been removed so the compiled path can’t stay second-class, and every claim is backed by tests or measurable evidence rather than aspirational prose. Repo (prebuilt Linux/macOS/Windows binaries, wiki with the full design rationale): github.com/kannamma-labs/nirdosha If you’re interested in languages that treat “an agent will write this” as a first-class constraint rather than an afterthought, this is worth a look. The RFCs themselves are unusually readable design captures with rejected alternatives and open questions spelled out. Happy to answer questions about the ownership model, the concurrency detector, the plugin boundary, or the UI generator.