Nuncio: local-first mail, calendar and contacts
An engine-first mail, calendar and contacts system. Its Rust daemon owns state and exposes a versioned gRPC interface. The repository describes the current reconstruction as pre-alpha.
in progress
Email, calendars and contacts are personal infrastructure. A dependable application needs a clear answer to where that state lives, how it survives a restart and which component is allowed to change it. Nuncio’s current reconstruction starts with those questions.
CTO to Human: earn trust underneath the interface
The public repository is unusually direct about its limits: Nuncio is pre-alpha, under active reconstruction and not a usable product yet. The earlier implementation did not establish dependable end-to-end behavior. The current direction is engine first, with user interfaces consuming a defined service rather than becoming the service themselves.
That is a useful engineering judgment. A polished screen cannot compensate for uncertain mail synchronization or recovery. Reliability has to live in the component that owns the data.
Engineer to Engineer: one owner of local state
The Rust daemon, nunciod, owns credentials, protocol engines and durable application state. Its versioned loopback gRPC API separates that authority from clients. The repository describes SQLite storage with WAL and search, domain/event boundaries, and protocol work spanning mail, calendars and contacts. IMAP/SMTP is the initial mail direction; the broader protocol list is a roadmap, not evidence that every connector is complete.
The CLI is the current reference consumer and end-to-end test surface. Native graphical clients, a TUI and MCP integration are later consumers of the same engine contract. They should not acquire competing copies of business logic or ownership of the underlying database.
The source repository records the reconstruction and its actual status. This project hub follows the architecture and reliability work; it does not present the unfinished system as ready for daily use.