Architecture

YantraOS processes an instruction through SENSE, REASON, and ACT. SENSE gathers the permitted context, REASON produces a structured proposal, and ACT executes only an approved action through a typed route.

The loop is deliberately inspectable: confirmation and audit records sit between intent and system access rather than being hidden inside a model prompt.

Host-owned routing classifies work into fast-path operations, supervised visual actions, or sandboxed computation. The route is selected from the action type and policy, not from arbitrary model-generated shell text.

See the action-routing ADR for the current decision record.

The privileged sandbox broker is the only enabled privileged execution service. Sandbox work uses immutable images, bounded admission, resource limits, and no network access. Host operations use typed JSON and allowlisted operations instead of raw shell execution.

These controls describe the public alpha. Hosted Runtime, public APIs, and third-party skills remain future yantraOS 2.0 work.

The daemon serves a bearer-protected loopback HTTP API and a permissioned Unix domain socket. The PySide6 GUI uses HTTP over UDS; Telegram uses loopback TCP. Legacy socket and SSE paths are not part of the current transport surface.

For the full transport decision, read the control-plane ADR.

The MIT-licensed Community Edition contains the local engine, confirmation and audit boundaries, sandbox broker, desktop bridge, ISO forge, self-hosted installer, and their tests. It communicates through the documented local control plane.

Tenant provisioning, billing, streaming, and managed Hosted Runtime deployment live outside that public repository and remain roadmap work. The open-core boundary documents the separation.