Where Sanguis is today and what comes next.
Sanguis is a language for building artificial life. You write organs, structures with their own fields and methods, and the toolchain pours them into a fixed kernel. The grid settles, and where it settles is the answer.
The same program gives the same bytes on every machine it runs on. That means the graphics card, the JIT, the C floor, bare metal, and the compiler that builds itself. Because of that, a running core can be saved to a small file and picked back up in a new process exactly where it left off, and anything it does can be replayed years later.
Since 3.0 we've added cells that check their own inputs and outputs, tests that fail if the PC and bare metal disagree, and tasks that take turns at the same points everywhere. 445 tests pass and none fail. Faster loops are already on the nightly build.
Invite only. You get the SDK, the Marrow editor, the language reference and the examples, plus a direct line to us.
We want people outside the company running the compiler and executors on their own machines and finding the problems we can't see from in here. What you find shapes the release after it.
The repository opens, and the SDK and docs are available to everyone. Sanguis ships under the VPL‑1.0. You can read it, test it and adapt it for free. Commercial deployment needs an agreement with us.
Our first core ships here too.
First, learning. The being already runs at human speed. Next it learns from the time it lives, rests and sorts through what happened, and changes because of it. All of that can still be replayed.
Then size. The same being should run on one column small enough for a microcontroller, or on a rack full of them. The kernel stays the same and only the programs change.
Further out is our own chip, where the runtime and the hardware are one thing. It's meant to help the technology people already have, not replace it. It gets a date when we've earned one.