From cb05300ba737a93ea594543340892f2a4a825f85 Mon Sep 17 00:00:00 2001
From: Tianyi Cui <53024+tianyicui@users.noreply.github.com>
Date: Sun, 12 Jul 2026 00:38:38 +0800
Subject: [PATCH] docs: remove duplicate scoped-event explanation

---
 .../architecture/2026-07-08-agent-scope-contexts.md           | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/docs/rfc/implemented/architecture/2026-07-08-agent-scope-contexts.md b/docs/rfc/implemented/architecture/2026-07-08-agent-scope-contexts.md
index d0cdefaee8..9fccc392da 100644
--- a/docs/rfc/implemented/architecture/2026-07-08-agent-scope-contexts.md
+++ b/docs/rfc/implemented/architecture/2026-07-08-agent-scope-contexts.md
@@ -223,9 +223,7 @@ dispatchScoped(subject, scopeKey, event, arguments):
       skip listener
 ```
 
-The real helpers fuse values that must agree: `agentEvents(context, agent)` supplies the same agent as subject, scope key, and first event argument; session storage captures its carrier once at `enter()`.
-
-`agentEvents(context, agent)` creates the carrier and injects that same agent as the first event argument. `assembleContextFor(agent)` similarly sets both the agent-facing field and the scope selector. The session store captures its carrier when a session enters because later appends and flushes may occur where the original agent context is no longer available.
+The real helpers fuse values that must agree. `agentEvents(context, agent)` uses the same agent as the subject, scope key, and first event argument. `assembleContextFor(agent)` similarly sets both the agent-facing field and the scope selector. The session store captures its carrier when a session enters because later appends and flushes may occur where the original agent context is no longer available.
 
 ### The carrier behaves like the subject but has distinct identity