Nexo Is Evolving Along With the Series
A pause between parts 7 and 8: four places where running nexo_mail against a real inbox forced the design past what the earlier posts described.
Writing on software design, Ruby on Rails development, and AI convergence.
Where I share what I'm exploring in software development, Ruby on Rails, AI, and everything in between.
Merging the Sources Into One Digest
Why the merge, dedupe and narration of three email extractions lives in a Nexo skill rather than in Ruby, and the seam for fixing model arithmetic.
The Sandbox and Permission Seams in Nexo
Nexo's four sandbox tiers and four permission modes, and how an email agent gets write access to one folder and nothing else, enforced in code.
Running the Inbox Agents Concurrently, With a Bound
Fan three email source agents out with Nexo.concurrent: bounded concurrency, ordered results, and a sequential fallback when the async gem is missing.
Turning Three Inboxes Into One Nexo Workflow
Wrap three email source agents in a Nexo workflow that skips what it cannot run, records every step in an event log, and still finishes when a source fails.
Previous
Next