diff --git a/docs/guide_multi_agent_conductor.md b/docs/guide_multi_agent_conductor.md
index a37b61a7..dbdb0fd4 100644
--- a/docs/guide_multi_agent_conductor.md
+++ b/docs/guide_multi_agent_conductor.md
@@ -289,15 +289,13 @@ class WorkerPool:
 
 ---
 
-## Sub-Agent Invocation (`mma_exec.py`)
+## Sub-Agent Invocation (Application MMA WorkerPool)
 
-The ConductorEngine does **not** spawn `mma_exec.py` directly. Sub-agent invocation is a **synchronous CLI bridge** at `scripts/mma_exec.py` invoked from a Tier 3 worker (see [conductor/workflow.md](../../conductor/workflow.md) "MMA Bridge" section). Each sub-agent is invoked via:
+**UPDATED 2026-06-27 (clarifying the domain distinction):** This section is about the **APPLICATION domain** — the manual-slop app's internal WorkerPool that spawns Tier 3 / Tier 4 worker subprocesses. It is **distinct from** the META-TOOLING domain (where OpenCode Task tool is the canonical sub-agent mechanism; see `docs/guide_meta_boundary.md`).
 
-```bash
-uv run python scripts/mma_exec.py --role tier3-worker "[PROMPT]"
-```
+The ConductorEngine does **not** directly spawn workers. The WorkerPool in `src/multi_agent_conductor.py:WorkerPool.spawn` creates a Python subprocess (via `subprocess.Popen`) that runs the worker's `run_worker_lifecycle`. **NOTE:** the worker's subprocess was historically invoked via `scripts/mma_exec.py --role tier3-worker` (the legacy meta-tooling bridge script). **That bridge script is DEPRECATED as of 2026-06-27 for meta-tooling use.** The application's WorkerPool uses its own internal subprocess template (`src/multi_agent_conductor.py:run_worker_lifecycle`) — NOT the meta-tooling mma_exec.py.
 
-The `--role` flag selects between `tier1-orchestrator`, `tier2-tech-lead`, `tier3-worker`, and `tier4-qa`. Sub-agents receive context via stdin (or as additional CLI args) and exit after one round-trip. The actual prompt construction lives in `run_worker_lifecycle` at `src/multi_agent_conductor.py` (the free function referenced by both `ConductorEngine.run` and the worker spawn flow).
+For meta-tooling sub-agent delegation (Tier 2 → Tier 3 / Tier 4 to do work on this repo), see `conductor/workflow.md` §"Conductor Token Firewalling" + the OpenCode Task tool (replaces the legacy mma_exec invocation).
 
 The "Token Firewall" effect — each worker starts with a clean context window — is achieved by the `ai_client.reset_session()` call at the start of `run_worker_lifecycle` (see [guide_mma.md](guide_mma.md) "Context Amnesia").
 ---