Skip to main content

Module delivery

Module delivery 

Source
Expand description

Split out of the single-file bootstrap module unchanged (SPEC_LARGE_FILE_MODULE_ANALYSIS_2026_09_30.md §4.3).

Enums§

AgentRoute 🔒
Where a message for an agent block goes.

Functions§

install_agent_turn_delivery
Give the reactive handler a delivery route to SubprocessController agents.
install_close_on_exit_handler
Wires blockcontroller::close_on_exit (see that function’s own doc comment) up to the real close action, now that AppState exists. Mirrors install_agent_turn_delivery just above — same “backend code needs a capability only available once AppState is built” shape, solved the same way (a process-wide callback set once at boot).
install_cron_delivery
Deliver cron fires in process, through the server’s shared inject path (server::reactive::deliver) on the instance-key tier — identity M4c-3 (SPEC_AGENT_IDENTITY_CARRIED_NOT_DERIVED_2026_09_23.md §6.5.9). The fire keeps every tier the route has (this instance, cross-instance, cross-channel, LAN, cloud) and audits the job’s creator UID here only.
route_agent_message 🔒
The routing half of the reactive sender below, shared with the Swarm broadcast (server::app_api::fleet) so a broadcast reaches ACP, App Server, running persistent and not-yet-spawned agents exactly as an inter-agent message does.
route_agent_message_from 🔒
route_agent_message, saying who the input is from: the Swarm broadcast labels its delivery to a running persistent agent as the user’s (deliver_agent_message_from). None is exactly route_agent_message.