ผลกระทบจากข้อมูลที่หายไปตรงกลาง

When you pack a long prompt into Claude's context window, the model does not attend to every token equally. Information near the start and the end of the context is recalled far more reliably than information buried in the middle.

This is the lost-in-the-middle effect. It is not a bug you can patch — it is a property of how attention behaves over long inputs. As an architect, you design around it.

On the Claude Certified Architect exam, this sits in Domain 5: Context Management & Reliability. The practical risk: a critical instruction, policy rule, or transactional fact that you placed in the middle of a bloated prompt gets silently ignored.

The failure is quiet. The model still produces a fluent answer — it just dropped the constraint you cared about. That makes lost-in-the-middle a reliability problem, not a formatting preference.

The simplest mitigation: put your most important instructions where attention is strongest. Lead with them in the system prompt, and restate the critical constraint at the end, right before the model generates.

Remember the API contract: the model keeps no state. You send the FULL messages history every turn. So every turn is a fresh chance — and a fresh risk — for middle content to be under-weighted.

A robust pattern is to bookend: state the rule up front in system, then echo a short reminder of it as the final line of the last user turn. The start anchors it; the end keeps it top-of-mind at generation time.

Keep the echo short. You are not duplicating the whole instruction — just the single decision the model must not forget.

A major source of middle-bloat is raw tool output. An API or MCP tool can return hundreds of fields when you need three. Dumping all of it pushes your real signal into the low-attention middle.

Trim tool results to the relevant fields before appending them to the message history. Less noise in the middle means the model spends its attention on what matters.

When context grows, teams reach for progressive summarization. Useful — but it makes numbers, percentages, and dates vague. Combined with lost-in-the-middle, a summarized transactional fact sitting mid-context is doubly fragile.

The fix: pull transactional facts into a separate "case facts" block kept verbatim, outside the summary. Don't let an order total or a refund threshold survive only as a paraphrase in the middle of a summary.

In Claude Code, /compact compresses the conversation to free up context. The benefit is room to keep working; the risk is identical to progressive summarization: numbers and dates become vague.

Before compacting a session that hinges on exact values, capture those values somewhere durable — for example in CLAUDE.md via /memory, which persists across sessions — so they survive compaction rather than dissolving into a fuzzy middle summary.

If you inject N retrieved chunks, their order changes what the model uses. The most relevant evidence should sit at the start or the end of the block — not at chunk number 7 of 14.

Two practical moves:

• Re-rank so the highest-relevance chunks bracket the block.
• Cut the block down. Fewer, sharper chunks beat a long tail of marginal ones diluting attention.

Lost-in-the-middle is one reason single-pass multi-file review dilutes attention. Cramming ten files into one prompt buries the middle files.

Decompose instead: a per-file local pass, then a separate cross-file integration pass. Each pass has a focused, shorter context where nothing important is stranded in the middle.

Multi-agent systems are hub-and-spoke. Subagents do not inherit the coordinator's conversation history — every fact must be passed explicitly in each subagent prompt.

This intersects with lost-in-the-middle: when the coordinator builds that subagent prompt, the critical instructions still belong at the start and end, and verbose blobs still get trimmed. Context isolation is an opportunity to hand each subagent a clean, well-positioned prompt instead of an inherited mess.

Before you ship a long-context prompt, run this checklist:

• Top: most important instruction in system, stated explicitly.
• Bottom: short echo of the single critical constraint at the end.
• Middle: trimmed tool output, re-ranked docs, no raw blobs.
• Facts: exact numbers/dates kept verbatim in a case-facts block, never only in a summary.
• Length: if it's huge, split into focused passes.

Position is design. Treat the middle as low-trust real estate.

Apply the lesson to a concrete architecture decision.

Key takeaways on the lost-in-the-middle effect:

• Models attend to the start and end more than the middle — treat the middle as low-trust space.
• Put critical instructions in system and echo the one constraint that matters at the end.
• Trim verbose tool output and re-rank retrieved docs so signal brackets the context.
• Keep exact numbers and dates verbatim in a case-facts block; summarization and /compact make them vague.
• For large work, split into focused passes rather than one diluted prompt.
• Position mitigates the symptom — but for rules with financial, legal, or safety stakes, enforce with hooks, not placement.