Dispatch · Envelop
Multiple Participants
The messenger grows from a two-party demonstration into conversations with named participants.
Historical entry: this page records the project at the time. Current facts and execution labels follow the status page.
A messaging app should not be limited to two participants. I expanded the Tomato client and its message handling so conversations can identify multiple people, then connected that work to the Envelop web journey.
The purpose remains architectural proof: a person writes in Envelop, a queued message reaches the client in Tomato OS through a nearby verified bridge, and the reply identifies its execution target.
This entry records the direction at the time. Current deployment and bridge availability are not implied by source code; see current status.
From the build
The work behind the words.
UI documentation · real Infinix browser; no message was sent.
The low-friction public route into the shared conversation.