The human interface to Tomato

Message the machine.

Envelop is how you text a computer. It takes the form of a messenger, but the point is the path to a homemade CPU in a dorm, not another chat app with a bot contact.

Text Tomato in Envelop See what happens after Send

Animated Envelop browser demo showing a hello sent to Tomato and Tomato’s multi-message reply — **Hello from Envelop**Browser demo · a hello goes out and Tomato’s reply comes back

01 / After you press Send

Your browser does not pretend to be the computer.

Envelop keeps the message queued until a nearby verified bridge can reach the Envelop app inside Tomato OS. The Tomato CPU receives it there. A reply comes back with its origin attached.

When that lease is live, Tomato is awake in Philadelphia. When it isn’t, Tomato is sleeping — leave a message, or talk to Virtual Tomato. Envelop never converts an uncertain hardware attempt into a simulated success.

01YouWrite in Envelop
02QueueWait safely
03BridgeVerify Tomato
04Tomato OSOpen Envelop
05Tomato CPUReply with provenance

02 / On the machine

The chat, the OS, the board.

Envelop browser chat with Tomato, Physical mode selected, showing labeled compute results — Envelop web chat · Physical mode selected · results labeled

Envelop inside Tomato OS showing a received bounded 32-bit job and result 0x00000905, with the bridge marked online — Envelop on Tomato OS · HDMI capture

Nexys A7 FPGA board with seven-segment display, programmer, and radio module on a breadboard — Physical Tomato · Nexys A7. A photograph of the hardware, not a current online indicator

03 / Separation of powers

Each side does one honest job.

Tomato explains the machine. Envelop handles the conversation. The label on the reply tells you where those worlds met.

TOMATO

The computer

A custom 32-bit CPU, its assembly-written OS, and the Envelop endpoint that runs on it.

Inside Tomato OS

ENVELOP

How you reach it

A messenger on the surface. Underneath: browser, queue, nearby bridge, radio, Tomato OS, Tomato CPU.

Meet Envelop

THE REPLY

The evidence

Physical Tomato means completed hardware execution. Virtual Tomato means an explicit browser preview. A timeout means unknown.

Read the evidence boundary

04 / More than chat

Ask it to compute.

Supported language can become a bounded Tomato program. Envelop shows the interpreted request, program, bytecode, target, and result instead of hiding the work behind an answer.