# Let subagents write durable artifacts instead of relaying everything through the coordinator

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Let subagents write durable artifacts instead of relaying everything through the coordinator

ID: MHC-D-RESEARCH-0954 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/let-subagents-write-durable-artifacts-instead-of-relaying-everything-through-the-coordinator

Every relay is another chance to lose detail.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- Specialist subagents produce large outputs that are summarized through several agents before reaching the final artifact.

### Avoid when

- Shared artifact stores need access control, provenance and conflict handling when multiple agents write concurrently.

### Explanation

When a subagent creates structured work—code, report, dataset, analysis—store it directly in the shared artifact system and pass a lightweight reference to the coordinator. The coordinator should synthesize or validate the artifact without forcing the full content through multiple conversational summaries.

### Steps

1. Give the subagent an explicit artifact destination.
2. Persist the output with a stable identity.
3. Return a concise result plus artifact reference.
4. Have the coordinator inspect or validate the artifact directly when needed.

### Example

A research subagent writes `market_scan.json`; the lead receives the path and summary instead of a rewritten copy of every source note.

### Check

Large specialist output can reach final production without a game of telephone through agent summaries.

### Limits

- Shared artifact stores need access control, provenance and conflict handling when multiple agents write concurrently.

### Evidence and sources

- supports: Anthropic's multi-agent research architecture uses direct artifact persistence to reduce information loss and token overhead across subagent handoffs. — RS-6479FBCFE4AB9C97. Shared artifact stores need access control, provenance and conflict handling when multiple agents write concurrently. (See source record)
- RS-6479FBCFE4AB9C97: How we built our multi-agent research system — https://www.anthropic.com/engineering/multi-agent-research-system

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/use-one-handoff-shape-for-recurring-transitions
