Blog

Clear arguments about the computer work we want to remove and the system we are building to remove it.

A pixel arrow cursor made of black halftone dots, carried on a current of gray dots across warm paper

What is an AI operating system?

Explainer
Three overlapping blank screen frames, each with a pixel arrow cursor in a different spot

What is a computer use agent?

Explainer
A scribbled note whose lower edge dissolves into loose halftone dots

Why AI agents forget everything between sessions

Memory
A hand holding a rubber stamp above a blank sheet of paper

How much access should an AI agent have?

Security
A twisting paper ribbon torn through the middle

Why AI agents fail at long tasks

Reliability
A human hand passing computer work to a machine hand

Why computer work should become optional

Perspective
An AI resident framed inside a machine aperture

What changes when the computer's user is purely AI

Product
Exploded machine layers surrounding a halftone agent figure

Why ERIKA is an operating system, not an app

Product
Power cable connected to a compact monitorless computer

The case for a monitorless AI computer

Hardware
One persistent agent aligned with one operating system machine

One operating system, one persistent agent

Architecture
Layered machine-readable documents forming a native browser

Why an AI operating system needs a native browser

Architecture
Archived memory layers flowing into a persistent agent

Why memory belongs to the operating system

Identity
A physical key inserted into an open agent computer chassis

Why agent capability should be owned, not rented

Ownership
Editorial note

These essays explain our current reasoning. Product architecture can change as experiments and builds reveal better answers. Research results live separately in the dated research ledger.