Limits first. Wins second. Disclosures third. What we can't do yet · Capability ledger · Honest disclosures
Some pieces are not finished. We are not going to pretend otherwise.
| Capability | Status | What it means |
|---|---|---|
| biRT on consumer ARM phones (where the boot chain unlocks) | Shipped | Bare-metal bring-up on consumer ARM phones where the post-BIOS chain hands off — boots through the device's bootloader to biRT, no OS. Framebuffer, debug, sensors, runtime all on the metal. The proof that biRT lands wherever the bootloader is reachable; per-device bring-up clears each new vendor's chain. |
| biRT-A — Android-form runtime | Shipped | When a device's bootloader is locked and the unlock path is exhausted, biRT-A ships the same intent contract as a single Android kiosk app — fullscreen AMOLED, all hardware sensors via SensorManager, identical 16-byte event log. When the device unlocks, the bare-metal binary takes over. Until then, biRT-A is what runs. |
| biRT on GCP — ELITE + FOUNDATION (x86) | Shipped | Two VM tiers running biRT bare metal in production, six nodes across three continents. ELITE (c2-standard-8) handles bulk translation, repo import, mesh hubs. FOUNDATION (e2-micro) serves encrypted triples at the edge. From-scratch gVNIC driver, UDP/IP/DHCP/ARP, bare-metal libc replacement, HW-accelerated crypto (AES-NI, SHA-NI) with software fallback. |
| Intelligence stack | Shipped | Natural-language understanding, reasoning, multi-format ingestion (PDF, JSON, CSV, plain text), intent ingestion with multi-source corroboration, 155,000+ word lexical database. ~28,000 lines of production C. |
| Cryptographic primitives | Shipped | AES-256-GCM, SHA-256/512/1, HMAC, PBKDF2, Ed25519 implemented from finite-field arithmetic up. Authentication uses constant-time comparison — no timing side channels. |
| Console & QR provisioning | Shipped | Cross-platform interactive terminal with F-key command bar (search, try, feed, confirm, ship, refactor, trace, save, inspect). QR generation from scratch (Galois field GF(256), Reed-Solomon error correction) for scan-to-register device provisioning. |
| Translation proofs (BASICI) | Shipped | ~50,000 lines of validated roundtrips proving every Intelligence skill survives translation between C, BASICI, and natural language. The receipts behind the BASICI claim. |
| Noise On The Wire (NOTW) | Shipped | Core protocol, mesh, and relay are done. Discovery, routing, store-and-forward, AES-256-GCM transport encryption, cross-platform. Additional transport backends (BLE, LoRa, WiFi/UDP, serial) being added. |
| Intelligent Data Store (IDS) | Shipped | Memory-mapped, journaled, encrypted at rest, indexed for sub-microsecond seek. Tested across persistence, growth, scope, and journaling. Wikipedia-scale public benchmarks pending; the architecture itself is done. |
| Pure-intent authoring tools | In Progress | Engineers can author and edit intents directly. End-user authoring (no engineer required) still in development. |
| Manifest delivery over mesh | In Progress | Signed payload broadcast over the mesh, applied at next runtime tick. The transport, signing, and broadcast paths are shipped; manifest-as-runtime-config is in active integration. |
| Operator console for AI (metal console) | Drafting | Operator-facing console that mediates AI conversations and authors manifests. Designed; planned and scoped in the metal repo. Not yet running end-to-end. |
| Multi-AI desktop edition | Drafting | Single surface routing to multiple popular AI providers. Designed; not yet built. Will not be claimed shipped until anonymization behavior is implemented and demonstrated. |
| Conversational manifest authoring | Drafting | Operators describe behavior changes in plain language; the system drafts a signed manifest. AI-assisted, multi-language. Designed and scoped; not yet running end-to-end. |
| biRT on RISC and emerging architectures | Drafting | Architectural targets identified with our hardware engineer. Bring-up work not yet started. |
| Custom silicon | Not Yet | Direction, not deliverable. Stated for honesty, not as a commitment. |
| External operator deployments | Not Yet | Internal use across multiple repos. No third-party in production yet. |
Every caveat across this site, in one place. None of these are buried.
No external operator has shipped on this in production yet. The cost and timing claims on this site are grounded in internal use across multiple deployments, not third-party measurement. We will publish real numbers the first time a customer ships.
The "less than 90 days" speed-to-ship prediction is a prediction, not a measurement. It comes from internal observation of how quickly the platform moves through a deployment in our own use, not from third-party benchmarking.
The three industry flows on the How to use it page are illustrative of the design, not transcripts from a production system today. The runtime, the manifest pipeline, and the mesh transport are shipped; the conversational manifest authoring layer is in active development.
Internal seek-speed measurements on the Intelligent Data Store are very promising. We will not claim "fastest on Earth" until we have published the numbers. We are running the architecture against Wikipedia and other public datasets next. Methodology, hardware, raw numbers, and comparisons will be published in full and reproducible by anyone who wants to verify them.