--- title: "Status Update" author: "Milad Habibi" date: 2026-08-09 slug: status-update-genesis-version tags: ["genesis","beta","logos","pilot program"] canonical: https://simorg.tech/blog/status-update-genesis-version/ --- $$$Image fileName=the-future.jpg$$$ Genesis is out. Our first public release, <<>>, shipped in May 2026. It carries the first public version of the Simorg engine, the compiler and the toolchain around them, along with the reference book, a getting started guide and the first blueprints of the standard library. If you have been following us and waiting for something you can actually run, it is on the $$$ToPageLinker keyword=download page toRoute=/download$$$ now. This post is a plain status update. Where we are today, what we have been building since May, what is still missing, and how the Pilot Program that opens in September fits into all of it. ## Where Things Stand <<>> is a beta release, and we mean that literally. The language works, the engine runs, and the core ideas are proven enough that people can write real programs with them. It is not a finished v1 yet, so treat it as software that is still moving under you. What is in your hands today: - The engine and compiler, with the full eventflow model, gates, wrappers and containers. - The command line toolchain and an install script for macOS and Linux shells, plus platform binaries. - The reference book and getting started material for this baseline. - The first standard library blueprints, enough to build small, complete applications. What you should still expect: - Occasional crashes and unexpected errors. - Error logs that are less helpful than they should be. - Slower execution than the technology is capable of, since these builds are not tuned for performance yet. - Frequent updates, and changes to APIs and compiler behaviour without a major announcement. Known gaps on the platform side are tracked publicly. Intel macOS binaries are still in the build pipeline while Apple Silicon is prioritised, Windows on ARM is planned with x64 as the supported Windows tier, and Linux on ARM is not supported on this release line. ## What We Have Been Building Since May The whole team moved to the repository the week after Genesis shipped. This is the place where artisans publish blueprints and where your applications resolve their dependencies from. A language without a repository is a demo, so this is the piece that turns Simorg from something you try into something you build with. The repository itself is the furthest along. Publishing works, the admin side for early adopter artisans is close to a usable beta, and the shape of a blueprint is settled enough that we are no longer changing it every other week. Publish and resolve is the harder half and it is still in progress. Getting a package from an artisan's machine into the repository is one thing. Resolving it correctly on the way back down, with the infrastructure provisioning that comes with it, is another. This is where most of our engineering time goes right now. Alongside that, a few things landed that were not on the original plan but turned out to matter: Search now runs on vector search, so finding a blueprint works when you describe what you need rather than guess its name. We also shipped early support for an MCP server, which lets an agent query the repository directly instead of going through a human and a browser tab. Both of these come from the same observation: most of the traffic to a repository in the agentic era will not be human. It felt strange to build one in 2026 with only people in mind. We have also been connecting applications and agents to each other, which is the groundwork for the milestone after this one. ## What Is Not Done Being honest about the gaps is more useful than a list of wins. The beta of the IoT blueprints for Raspberry Pi, Arduino and ESP32 has not started. It is planned for this phase and it is the piece most likely to slip. The standard library is thin. It covers the basics, and you will find something missing in your first afternoon of serious work. This is exactly why the repository matters more than us writing more built-ins. Our target for opening the repository is 12 September 2026. We think we will make it. If we do not, we will say so here rather than quietly move the date. ## The Pilot Program That same day is when the Pilot Program starts, on 12 September 2026. The $$$ToPageLinker keyword=waitlist toRoute=https://logos.simorg.tech/signup$$$ is open now. The pilot is a small, deliberate group. We are looking for engineers who want to build something real on an early technology, engineering leaders and CTOs evaluating what an AI native stack actually costs, AI startups and product teams shipping fast, and artisans who want to publish the first blueprints and be part of the ecosystem from day one. What you get is straightforward. Early access to Simorg as it moves toward a stable v1. A direct line to the people building it, not a support portal. Help getting set up and running your first real experiments. And genuine influence over what ships next, because at this stage a single well argued use case can change a design decision. What we ask in return is equally straightforward. Use it, and tell us the truth about it. The pilot is not a marketing exercise. We would rather hear that a workflow is painful than that the syntax is elegant. We review every application ourselves and usually reply within a few business days. ## How You Can Help Before Then You do not have to wait for September. Download Genesis, work through the getting started guide, and build something small. Then tell us where it hurt. Open an issue on GitHub, which is still the fastest way to reach us. If you write something you are proud of, share it, since good examples teach the language better than documentation does. If you want to help in other ways, the $$$ToPageLinker keyword=support page toRoute=/support$$$ explains what donations and sponsorship go toward, and sharing what we are doing inside your own community is worth more than most people assume. ## Please Be Mindful Simorg is not a full fledged company. The team is small and the resources are limited, so expect delays and be patient with support requests. What we can promise is that every message and comment is read by a person on this team. There is no AI tool sitting between you and us, and there will not be one. Thank you for being here this early. See you in September.