Young, working, and deliberately not for sale.

Honesty is part of the design, so here are the plain limits.

• It is a working system, and a young one. Declared machines boot and judge themselves in an emulator today; no customer yet runs a critical production workload on it. The first iteration of the Cousbox restaurant platform is delivered and its box is the first Harobanda target; the Diko engagement is won and is in its study phase.
• The kernel underneath is borrowed on purpose. It is the same long-term-support Linux that Ubuntu, Red Hat and the major distributions ship — its source fixed by a fingerprint, so any change to it would show, and built by your own compiler — and a board's firmware is the supplier's, fixed by fingerprint too. Borrowed is not the same as withdrawable; that distinction is the whole point.
• Single-binary deployment is the goal, not yet the whole reality. Declaring, judging and emulating a machine need only the harb binary; producing a flashable hosted image still calls a standard kernel build under the hood today. Folding that into the one binary is a committed direction.
• The application layer is further along than the machine. HaroServ and HaroScript are at version 0.9, ready to use and not finished, and MicroHaro is underway; today programs run through the engine's Luau and Ring surfaces, with Python, JavaScript and PHP as the surfaces broaden. The Softanza foundation and its intelligence layer are in active development.
• The agent guarantees are the floor's, and they are real. The walls around each program, the per-program budgets, a boundary of routes declared in the file, the signed record of every boot and the judged trial exist today; pointing an autonomous agent at them, end to end, is the frontier.
• The enterprise answers are at mixed maturity. The security posture is largely a property of the design and holds today (what it rests on, and what is not built); fleet-scale rollout, standard sign-in and integration connectors are partly built and partly a committed direction. The cloud is six steps, of which two are built and half of a third, in an emulator and for no customer (where the cloud stands).
• It will never be a product you buy from a vendor — because a vendor inside the system is the one thing it refuses. That is not a gap to close. It is the design.

It came from real work, in Niamey and in France.