The model
Local-first by default. One OS under every app.
Two ideas shape how you build on Harobanda — and both keep the operating system at the centre, as the one floor every part of your solution stands on.
Local-first by default
The data lives on the device, and the app works straight from it. The network is optional: when it is there you sync, when it is gone nothing stops. A shop till, a clinic queue, a bank counter cannot pause every time the connection drops — and here they do not have to.
The machine is what makes it real: a fixed network address, and a disk that keeps its data through a power cut, both set up before any program starts — so local-first is a property of the operating system underneath, not a hope inside each app.
One OS hosts the whole Haro family
Harobanda is the floor, and it hosts everything the Haro family produces — each declared as a service on the same machine: the Haro language and engine; the web and agentic server; hy-native mobile apps (hybrid + native) and local-first pages; and IoT and edge programs.
One family, one language, one host. Your rules are written once, and the OS runs them unchanged wherever it places them — the counter, the tablet, the sensor — with no second runtime to stand up and no rewrite at the boundary. A small team keeps one floor, not four stacks.
The connection is a guest, not a foundation — and the operating system is the one host beneath the server, the app, the page and the device.