Dispatch · Compute
Virtual Tomato, Not an Invented Answer
Bounded compute keeps the program visible and the execution target explicit.
Historical entry: this page records the project at the time. Current facts and execution labels follow the status page.
A greeting is a useful messaging proof, but Tomato’s ALU can do more. The compute preview lets Envelop normalize a supported request, show the bounded program and bytecode, then ask Tomato to execute it.
Each job has eight private registers, 256 private words, at most 32 straight-line instructions, and a mandatory return. Unsupported requests fail instead of producing a host-computed answer labeled as Tomato.
The compute explainer documents the current boundary and reproducible local preview.
From the build
The work behind the words.
UI documentation · hardware and virtual execution remain separate labeled paths.
FramePort capture of a bounded job displayed inside Tomato OS.