Broad roadmap, narrow active scope.

M1: boot proof

Boots over UEFI to one line. Framebuffer checked in QEMU.

M2: keyboard input

Last key pressed, below the boot line. Injected in QEMU, framebuffer read back.

M3: draw a rectangle

One filled rectangle. Size, centring and clipping checked.

M4: mouse cursor

Cursor follows the mouse. Movement measured in QEMU.

M5: move the rectangle

Sixty pixels a second off a hardware timer. Four captures checked.

M6: basic arithmetic

Type a sum, get the answer. Overflow and divide by zero refused.

M7: conditionals

IF, THEN, ELSE on one line. Both branches typed and read back.

M8: variables

Eight named values. An unset name is an error, not a quiet zero.

M9: keyboard controlled rectangle

Arrow keys steer it. Three presses down measured at exactly 48 pixels.

M12: rotating triangle and floating point

Floating point confined to one file, enforced at link time.

M10: edge wrapping

The rectangle wraps at both corridor edges, checked in QEMU.

M11: click and drag the rectangle

Picked up with the pointer, keeping the press offset, and left on release.

M13: window object model

Stable window ids, geometry and z order in a bounded pool.

M14: window surfaces and compositor

Window local pixels, clipped and composited in z order.

M15: focus and event queues

Focused input routed as bounded per window events.

M16: dirty regions and an immediate cursor

Only what changed is drawn. A cursor move costs a few hundred pixels, not a screen.

M17: tiling layout

Windows placed by a rule into tiles that never overlap.

M18: the ME OS Default desktop

Bars, frames, focus and a taskbar, with clicks routed to the right window.

M19: a terminal that knows what the machine is

A shell answering with what the kernel measured, never a written down answer.

M20: a filesystem and the commands that move around it

Real directories, files and paths, with real errors when a path is wrong.

M21: an editor, a clock, and a shell you can work in

Text changed in the middle of a line and saved. The machine knows the time.

M22: four workspaces

Ctrl 1 to 4 switch, Ctrl M sends a window across.

M23: a disk

The filesystem is written to an ATA disk and survives a restart.

M24: files made of blocks

A file is a list of blocks from a shared pool, so a document fits in one.

M25: output that need not go to the screen

Any command can be redirected to a file or piped into another.

M26: scrollback

Page Up and Page Down look back at what went past.

M27: files of commands

RUN reads a file and does what it says. A script that runs itself stops.

M28: finishing a name

Tab completes a filename, and offers nothing rather than the wrong thing.

Proof point: Factorio running on ME OS

Factorio does not run on ME OS. No Linux system calls, no ELF loading, no memory allocator, no processes.

M1: rotating pyramid

A pyramid in a 3D simulator, driven through the command layer.

M2: multiple scene objects

Several objects, each with its own transform. No display hardware.

M3: pointer interaction

Hover, select, grab, drag, release. Only the mouse works, the rest are stubs.

M4: simulated Holo Pencil

A software pointer on the same commands. No physical pencil exists.

M5: bracer input adapter

Hand pose, alignment, grip, losing tracking. No bracer exists, no sensor is read.

M6: richer Carl adapter

Several instructions per sentence. Offline keyword matching, no model, no network.

M7: multi user interaction model

Several control surfaces on one scene. Still a simulator.

M8: physical backend protocol design

What a real projector would be sent, written down. No hardware control code.

M9: hardware integration

Gated behind an independent safety review. Nothing has been built and nothing is scheduled.

Command Panel v1, frozen and verified

Event ordering proved against the real binaries. It runs on one machine.

Agent runtime, first slice

Identity, session and process as three lifetimes. A restart is not a new agent.

A shared room for people and agents

One record both read. A name is earned by a password and cannot be chosen.

A deployed agent group

Not installed. No server, nothing anybody outside can reach.

Supervision and recovery

Agents outlive the daemon. A pid plus its start time, so recovery never adopts a stranger.

The daemon, and adopting orphans

Checked over a real socket, against genuinely orphaned processes.

The policy gate

What may run, and what needs a commit first. Refusals are recorded too.

A file capability server

Proven against the real binary. It refuses a path in its own process, not Carl's.

The command runner

The harder half. Nothing of it is built.

Hand tracking feasibility

Can sensing resolve finger intent? Asked before anything is designed.

Platform design

Define the shared simulation and measurement layer.

Smart DC bus study

Paper study only. Nothing built, nothing energised.

First production proof of concept

One clip, printed, checked by camera and weight. Nothing built.