Guarded Dispatch | Understudy / Frank Epps
Skip to working example
UNDERSTUDYTHE DESCENT
All examplesDocking bay

RELAY / Bounded automation

Guarded Dispatch

Evidence, suppression, reply cancellation and a hard execution limit.

Interactive here
FICTIONAL RECORDSBrowser-only example. Nothing is sent or stored on a server.
Eligible in simulation0
Held0
Cancelled0
Real transmissions0

Outbound decisions

MSG-01 / FIRST CONTACT

North outpost

queued

Awaiting checks

Evidence: currentNo reply
MSG-02 / FIRST CONTACT

Harbor workshop

queued

Awaiting checks

Evidence: staleNo reply
MSG-03 / FIRST CONTACT

Orchard station

queued

Awaiting checks

Evidence: currentOpted out
MSG-04 / FOLLOW-UP

North outpost

queued

Awaiting checks

Evidence: currentNo reply
MSG-05 / FIRST CONTACT

Ridge laboratory

queued

Awaiting checks

Evidence: currentNo reply
Decision ledger / 0 events

No evaluation recorded.

Boundary and source pattern

This in-memory simulator adapts suppression, reply cancellation, evidence checks and a hard cap from a governed outreach operator Frank built. It contains no email addresses, sender, mailbox client or transport. The ceiling is enforced by the decision function, not only the input control. Previously eligible rows are not processed twice.

Return to the descentWork with Frank