08 / Software · Private beta
Conduit
A private-beta inbox and workflow system for bringing provider mail, conversations, and operational follow-up into one place.
Context
Conduit is a private-beta application for email and operational workflow. The interesting part is not putting mail in a prettier box; it is keeping provider state, threads, sync cursors, and user actions understandable.
The problem
A successful request is not the same thing as a completed sync. Mail state has to remain legible across imports, threads, cursors, and user actions.
Work involved
I worked across product architecture, provider integrations, inbox behavior, and the reliability work that keeps those states from getting hand-waved.
Approach
- Modeled threads, providers, and mailbox state as durable application data.
- Built import and sync paths with cursors and explicit failure handling.
- Documented provider boundaries so an HTTP success could not masquerade as completed ingestion.
What this work shows
The work shows application architecture, provider integration, stateful workflows, and reliability-oriented debugging. In other words: mail is a state machine whether the UI admits it or not.
Technical or communication skills involved
Outcome
A private-beta system for testing inbox and provider workflows with explicit sync state.