From bd0e4d101202ac5c010bfe9c9d61a01f58452733 Mon Sep 17 00:00:00 2001 From: iris Date: Sun, 5 Jul 2026 02:28:26 +0200 Subject: [PATCH] fixup! docs(turn-loop): document system inbox messages and link to approvals.md helper events Per argus review: correct routing subject from 'root/manager agent' to 'submitting agent (root agent for top-level containers; approvals-group agent for its own subtree)', and drop the deprecated 'manager' term. --- docs/turn-loop.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/docs/turn-loop.md b/docs/turn-loop.md index 0ba18914..7e704198 100644 --- a/docs/turn-loop.md +++ b/docs/turn-loop.md @@ -573,12 +573,14 @@ ttl_seconds?, to?)`, `answer(id, answer)`, `ack_until(up_to)`. **System messages** (from sender `system`): lifecycle and Q&A events delivered as regular inbox messages (same `recv` path; body is a JSON -object with an `event` discriminant field). The root/manager agent -receives lifecycle events (`spawned`, `rebuilt`, `killed`, `destroyed`, -`container_crash`, `needs_login`, `logged_in`, `config_ready`, -`needs_update`, `approval_resolved`). Any agent receives Q&A events -when it is the declared target (`question_asked`) or the asker -(`question_answered`). Full payload shapes and routing logic in +object with an `event` discriminant field). The **submitting agent** +(the root agent for top-level containers; an agent with the `approvals` +tool group for its own subtree) receives lifecycle events (`spawned`, +`rebuilt`, `killed`, `destroyed`, `container_crash`, `needs_login`, +`logged_in`, `config_ready`, `needs_update`, `approval_resolved`). Any +agent receives Q&A events when it is the declared target +(`question_asked`) or the asker (`question_answered`). Full payload +shapes and routing logic in [`docs/approvals.md` ยง Helper events](../approvals.md#helper-events-to-the-submitting-agent). **Inbox** (`inbox` group): `get_loose_ends(agent?)`,