Lefteris Notas

xiom

Open-source funding for XIOM, a systems language with native contracts - Supporting the compiler, stdlib, registry, and tooling.

Contributions


About


 
Our Story 
XIOM started from a simple frustration: as AI-assisted coding became normal, the tools didn't change to match it. Compilers still assumed a human wrote every line with full context in their head. But increasingly, code is written by a model that's guessing at intent and guessing wrong in ways traditional type systems don't catch, because the bug isn't a type error, it's a misunderstood assumption. 
XIOM's answer was to put contracts directly into the language itself  not as documentation, not as an optional annotation, but as something the compiler enforces and can even prove mathematically. Whether the code was written by a person or an AI, the contract holds. If an AI model has never seen a line of XIOM before, it can still query the language's own tooling for real function signatures and contracts instead of guessing  so correctness doesn't depend on the model having memorized the language. 
What began as a systems-language design has grown into a full ecosystem: a compiler, 60 standard library modules, a growing package registry, and an interactive playground with hundreds of lessons  built and maintained from Kastoria, Greece, alongside a small, cross-platform toolchain that runs natively on macOS (Intel and Apple Silicon), Windows, Linux, and WebAssembly. 

Our Purpose 
This collective exists to fund the infrastructure, tooling, and eventual community contributions that keep XIOM open, independent, and free to use  hosting, CI/CD, the registry, and the playground that lets anyone try the language with zero setup. 
XIOM is not owned by a company with commercial incentives to lock in its users. It's built to remain open-source (MIT/Apache-2.0), verifiable  every performance and safety claim we make is backed by a reproducible, open benchmark anyone can run themselves  and genuinely useful in a world where more code is written alongside AI than without it. 
Contributions here go directly toward keeping that infrastructure running and, as the project and community grow, toward formalizing XIOM as a proper open-source foundation rather than a single maintainer's side project.