Lesson 580 of 2116
Delivery Routing for Cron and Agent Outputs
Create a delivery router so agent outputs land in the right channel, format, and approval state.
Lesson map
What this lesson covers
Learning path
The main moves in order
- 1What the local Hermes build teaches
- 2delivery router
- 3channel
- 4notification
Concept cluster
Terms to connect while reading
Section 1
What the local Hermes build teaches
This build lab focuses on the delivery layer that decides where finished agent work should go. The goal is not to copy a private machine setup. The goal is to learn the architecture pattern well enough to build a small, classroom-safe version.
Delivery is a policy decision: some outputs stay local, some create drafts, some send notifications, and some require explicit approval.
Compare the options
| Hermes pattern | Student build | Risk to handle |
|---|---|---|
| Name the boundary | a delivery matrix for local console, email, Discord, dashboard, and teacher review queue | letting background jobs post public messages or emails without a human review path |
| Keep the interface small | Start with one happy path and one failure path | Avoid a demo that only works when everything is perfect |
| Make the system observable | Log decisions, status, and errors in plain language | Do not log private data or secrets |
Build the small version
- 1Draw or write a delivery matrix for local console, email, Discord, dashboard, and teacher review queue.
- 2Mark which parts are user-facing, which parts are internal, and which parts require approval.
- 3Choose one low-risk workflow and implement only that workflow first.
- 4Add one failure case before adding a second feature.
- 5Write a short operator note: what the agent may do, what it must ask about, and what it must never do.
A classroom-safe skeleton inspired by the local Hermes architecture scan.
delivery_policy:
lesson_digest:
channel: teacher_dashboard
approval: none
parent_email:
channel: email_draft
approval: required
public_discord_post:
channel: discord
approval: required
local_debug:
channel: console
approval: noneKey terms in this lesson
The big idea: delivery router is not decoration. It is part of the product architecture students need before an agent becomes safe enough to use with real people.
End-of-lesson quiz
Check what stuck
15 questions · Score saves to your progress.
Tutor
Curious about “Delivery Routing for Cron and Agent Outputs”?
Ask anything about this lesson. I’ll answer using just what you’re reading — short, friendly, grounded.
Progress saved locally in this browser. Sign in to sync across devices.
Related lessons
Keep going
Creators · 21 min
Gateway Sessions Across Discord, Slack, and CLI
Design session keys so one agent can talk through many surfaces without mixing users or channels.
Creators · 50 min
Evaluating Agent Performance: SWE-bench, WebArena, GAIA
Numbers on leaderboards are seductive and often wrong. Learn the big benchmarks, their leaderboard positions, their recently-exposed cheats, and how to run your own evals.
Creators · 52 min
Red-Teaming Agents: Injection, Escalation, Exfil
An agent is a new attack surface. Prompt injection, privilege escalation, data exfiltration — these are no longer theoretical. Learn the attacks and the defenses.