THE SUBSTANCE.

Runtime architecture #

biRT is a complete computing platform written from scratch in C. It runs directly on hardware — no operating system, no kernel, no filesystem, no external libraries. One binary. From power-on to thinking in under a millisecond.

Because the runtime is pure machine code and small enough to fit beside the silicon — not on top of a half-gigabyte of operating-system overhead — the hardware does what it was built for. The OS isn't in the way.

biRT lands on any hardware that doesn't lock the boot chain after BIOS. Production today:

• Production-class compute — bulk translation, repo import, mesh hubs. Multi-region.
• Edge nodes — sealed-record serving at the edge. Multi-region.
• ARM bring-up on consumer phones where the bootloader is reachable. Per-device bring-up clears each new vendor's chain.
• Android-hosted form ships the same intent contract on devices whose bootloader is currently locked. When the device unlocks, the bare-metal binary takes over.
• RISC and emerging architectures next, on the recommendation of our hardware engineering lead.

Crypto and key model #

Cryptographic keys are generated on the device and never transmitted off it. Local storage is sealed with passphrase-derived keys. Brute-force lockout is built into the vault.

Modern primitives, implemented in-house. No third-party crypto libraries on the trust path. Hardware acceleration where the silicon supports it; software fallback when it doesn't. Specifics available under NDA — or for partners with the key, in the technical detail page.

This is what we have shipped, in the codebase, today. The conversational privacy layer for AI interactions — the part that mediates between operators and external models — is being designed now. We will describe it here when we can point at running code.

Mesh — NOTW #

Devices find each other and talk securely without cloud infrastructure. Store-and-forward across multiple physical layers. The system keeps working when the network doesn't.

• Discovery + routing — nodes announce themselves and route through whichever path is up.
• Store-and-forward — messages survive intermittent connectivity. Delivered at the next sync tick.
• Encrypted transport — the same key model as on-disk sealing. End-to-end.
• Multi-transport: short-range wireless, long-range radio, IP, and physical. New backends drop in beside the existing ones.
• Cross-platform — same wire protocol on every supported runtime.

Offline-first stance: the mesh assumes the network may not be there. Nodes carry their own truth and reconcile when they reach each other.

Intelligent Data Set (IDS) #

A novel persistence layer for sovereign, encrypted, indexable knowledge. Knowledge and code share the same representation, which means the system reasons about its own behavior the same way it reasons about anything else.

Manifest pipeline #

One linear flow from operator's voice to runtime tick:

The runtime never sees the conversation; the conversation never has to know about the runtime. Two worlds joined: machine-level code that runs as fast as the silicon allows, and human thought translated into runtime instructions.

Current state of each link in the chain:

• Mesh transport + signed broadcast — shipped. NOTW carries signed payloads end to end.
• Conversational manifest authoring — drafting. The operator-facing console that mediates AI conversations and authors manifests is designed and scoped; not yet running end-to-end.
• Manifest-as-runtime-config — in active integration. The transport, signing, and broadcast paths are shipped; manifest application at the runtime tick is being wired up.

See the capability ledger for the full status surface.