Dispatch · Envelop
Envelop — Tomato Gets a Message App
A messenger becomes a real Tomato OS application, not merely a host-side mockup.
Historical entry: this page records the project at the time. Current facts and execution labels follow the status page.
Envelop began with a simple benchmark: connect Tomato to a screen, then let it exchange messages with another device. The Tomato-side client became assembly linked into Tomato OS.
The name fits the machine: an envelope carries a message across distance. The current system is larger than this first moment, but the boundary stays clear. Envelop’s web and native clients, backend queue, and nearby bridge live in the separate Envelop project; its firmware, setup data, and bounded executor run inside Tomato OS.
The stable Envelop explainer describes the current path and the live evidence required before a completed FPGA reply may be labeled Physical Tomato. Available client, backend, and bridge software does not establish that a nearby authenticated bridge is currently online.
From the build
The work behind the words.
Browser emulation · current OS image, simulated controls, bridge offline.
A person and Tomato sharing the same focused conversation.