Ingress

When you mention Unveil Code, the message goes to ingress first. Ingress gets the message to an agent and makes sure it is never lost, even when the agent is busy or has crashed.

Answer Slack first

Slack waits about three seconds for a reply that says the message arrived. Miss that window, and Slack sends the message again. Real work takes longer than three seconds. So ingress confirms the message first, then starts the work. Slack stops resending, and the agent can take its time.

Ignore repeats

Slack sometimes delivers the same message twice. Ingress records each message it has finished and skips the repeats, so one mention makes one turn. A message stopped part-way by a crash is never marked finished, so it runs again instead of being lost.

Wait for a free agent

The right agent may be busy on an earlier message, or it may have died. So ingress does not hand the message over directly. It writes the message to a durable queue, where the message waits until an agent takes it. A new thread gets a fresh agent. An existing thread adds the message to its agent's queue for the next turn. If that agent has died, the reaper restarts it to work through the queue. A crash only delays the reply. It does not lose it.