Skip to content
03 · Back the thesis

A phone that owns its stack — and de-risks the hard part.

The wedge is an operating system organized around your work, not apps. The strategy separates a fast, low-risk product track (in emulation today) from slow hardware bring-up — so value ships without being hostage to silicon.

The case

Four load-bearing bets.

The wedge

AOS-RES-013

An entity-and-agent OS with inspectable agents and local-first authority — a category difference from iOS/Android app silos, not a feature difference. Value is shifting from the model to access to data and actions, which app-centric systems structurally can’t provide.

Two-track de-risking

AOS-BRIEF

The product runs in emulation now; a pre-certified-module “demo brick” carries the OS on real radios years before a custom device. Almost no reverse-engineering on the critical path — a failed hardware route never invalidates the portable architecture.

Business model

AOS-PROD-013

Subscription sells storage and elastic server compute; a mid-range device plus subscription can feel like a flagship, widening the hardware design space. A self-host tier proves offload is a protocol, not a trap.

Honest ceilings

AOS-BRIEF

Camera is “decent,” not flagship, without closed tuning; the demo brick is a demonstration device, not a security product. Claims are evidence-gated, not marketing — every public statement traces to a spec.

Why now

The market converged and stopped differentiating.

Feature-based differentiation is exhausted; paradigm-based differentiation is wide open. Fuchsia is alive and open, but Google isn’t aiming it at phones — no competition for the Fuchsia phone, and no help either.

APP-LAST
system object model

Durable work and life entities remain primary while applications become replaceable providers and views.

ONE
typed action model

UI, CLI, scripts, agents and micro-apps invoke the same operations with the same capability and receipt rules.

MESH
transport-neutral delivery

Direct, off-grid, gateway and delayed paths share one envelope, identity and policy model.

LOCAL
authority by default

User-controlled state remains primary; remote providers receive bounded and inspectable inputs.

Diligence

What exists today vs planned.

This is a research-and-engineering programme. Nothing here claims certification or financial projection — it documents intent, strategy and evidence gates.

Cross-linked Engineering Bible and stable specifications Today
Task graph and evidence registers Today
APP-LAST product and capability model Designed
Text-to-Micro-App builder and runtime Designed
Agent Mesh, LoRa accessory and DTN programme Designed
Reference platform and first isolated process Next
Entity Store, actions, history and first agents Planned
Real-device and integrated-radio bring-up Planned

Identity and distribution are designed, not deferred: a system-wide Global Account and an App-Store-free micro-app model. See how they work →

Read the strategy

Source documents.

Planning ranges only: Wave 0 / first 90 days ≈ USD 28,940–79,080; total listed programme equipment and initial professional-services envelope ≈ USD 44,540–122,080 before payroll, tax, cloud, NRE and certification. Not quotes.

Back the thesis.

Want the full brief and the data room? Leave your email and we’ll be in touch.

No spam. A research programme — you’ll hear from us when there’s something real to try.