MISSION 05

RbMail

Several mailboxes as one day's feed, with the commitments inside them surfaced. Headers only, never bodies.

CLIENTPrivate client
ENGAGEMENTMail connector with AI workflows
STACKNEXT · NEST · FASTAPI
The RbMail Today view showing a single day's mail across accounts, with extracted tasks and upcoming items alongside
PLATE 01One day's feed, with commitments pulled out alongside
RbMail reading a thread, with category counts in the sidebar and actions to read later, create a todo, or summarise the thread
PLATE 02A thread in its category, with the per-thread actions

THE PROBLEM

Four mailboxes is worse than four times one inbox, because nothing tells you which of the four the important thing landed in. And most commitments arrive as a sentence in the middle of a message, so they get copied out by hand or missed.

WHAT WE BUILT

  • One feed across every account, organised by day rather than by inbox.
  • Categories with live counts, so fifty newsletters can be dealt with as fifty newsletters.
  • Commitments extracted with a due date and a priority, linked back to the thread.
  • A custom RSS feed beside the mail, so reading and answering live in one place.
  • Per-thread actions: read later, create a todo, summarise.

THE DECISION THAT MATTERED

Encrypted headers only. No message bodies in the database, ever. A connector that keeps bodies quietly becomes the most sensitive database in the organisation, and a target for as long as it exists. The scheme is versioned and the keys can be rotated.

Nothing is sent, deleted or archived on a model's reading of a sentence. Extraction suggests, the person decides.

ALL MISSIONSSTART SOMETHING LIKE THIS