BEROUNOS for AI-native devices

Architecture

One system. Clear responsibilities.

The assistant coordinates work through the system dispatcher. Specialist agents do their assigned work within declared permissions. Underneath, a lean Linux built for small devices.

From the assistant down to the kernel.

AI Assistant · Caroline
↕
System Dispatcher · Tasks · Resources · Permissions · Audit
↕
ApplicationsSpecialist agentsHardwareNetworkStorageSecurity
↕
Weston · WaylandWPE WebKitPower serviceMemory serviceHardware layerTask broker
↕
Linux foundation · minimal Buildroot image · ARM64

Under the hood

The components.

LayerWhat it does
Kernel and baseLinux; on the device a minimal image (Buildroot, BusyBox init)
Window systemWeston (Wayland): one screen, windows managed by the system
Interface engineWPE WebKit: a light web engine for embedded devices, the same in the simulator and on the device
System dispatcherStarts and measures apps and services, checks manifests, serves the system's programming interface to the shell and the assistant
Task brokerPart of the dispatcher: the registry of app agents, tasks with states, the log, agents' access to the Camerlengo API with the owner's session and keys kept in the system
Power serviceA separate process: sleep, wake, power off and power on, working even if everything else hangs
Memory serviceThe memory budget, compressed swap, write-back to flash with a daily write limit
Hardware layerOne interface to every device: real hardware on the device, virtual hardware in the simulator
ProcessorARM64 (Cortex-A55), 4 cores, 2 GB of memory on the first device

The coordinator

Caroline is part of the system.

Privileged by design

  • Her service is never stopped for memory and keeps running while the device sleeps.
  • She may take the screen when something is urgent.
  • Her views live in the system: the text chat on the first tile, the voice dialogue with her face over the screen, the first-run wizard and her section of Settings.
  • She cannot be closed or unloaded like an app.

Direct means, not screenshots

  • She works through the system's own interfaces: app manifests, the list of services, windows, files and the network.
  • Each app's tools and agents are hers to use.
  • She remembers the owner's standing rules and keeps to them.
  • Everything she does is signed and visible to the owner.

The trust model

Security is where the boundary runs.

The boundary is the device

Everything the assistant manages is inside the system. The owner's phone, computer, bank and verification codes are not.

The assistant's own accounts

The assistant works from accounts of its own; the owner's stay the owner's, unless the owner decides otherwise.

Separated data

Each app sees only its own part. System data lives apart.

Privilege only where needed

Only the assistant is privileged. App services cannot take the screen or outlive a memory shortage unless their manifest allows it.

Agents stay in their app

An agent works with its own app's data and the permissions declared in its manifest. Paid AI calls go through the dispatcher and into the log.

System buttons are untouchable

No app can see or reassign the assistant, power and volume buttons. Every action is signed and can be checked.

Beroun

A lean Linux. A clear chain of command.

From Caroline to the kernel, every layer knows its job.

Build on BerounSystem models