--- title: "Context Flow · concept · Agentic Atlas" description: "Context Flow: how context enters, stays in, and leaves a model's window, and how well it's recalled." canonical: "https://agentic-atlas.dev/nodes/context-flow" last-updated: "2026-09-23" --- 1. [Agentic Atlas](https://agentic-atlas.dev/) 2. [Patterns in the Agentic Atlas](https://agentic-atlas.dev/atlas) 3. Context Flow Parent of [Momentum](https://agentic-atlas.dev/nodes/momentum). 1. concept # Context Flow **How does information move through an agent’s context window?** Context is a pipeline: an artifact is admitted to the window, stays resident, then is evicted, and recall can shift with placement and later arrivals. Hook how context enters, stays in, and leaves a model's window, and how well it's recalled Laws & fences - Recall is tracked per artifact, so a summary starts a fresh recall history even with the same information. - Recall distance, placement, and surrounding context can each change recall accuracy, but no curve is universal. - Decay can lower recall accuracy while an artifact stays in the window, but decay is not eviction. - This node models movement and does not prescribe when to load, drop, or place an artifact. When to reach - Reach for this when a design question is about how context moves, not how full the window is. - Reach for this when comparing techniques that delay, shrink, reroute, or remove context in shared terms. Provenance [context-flow/definition](https://agentic-atlas.dev/nodes/context-flow#definition) · v1.0.11 Addresses atlas_cards context-flow 2. [Context Efficiency](https://agentic-atlas.dev/nodes/context-efficiency) 3. [Momentum](https://agentic-atlas.dev/nodes/momentum) 4. [The Context Economy](https://agentic-atlas.dev/nodes/context-economy) 5. [Deferred Context](https://agentic-atlas.dev/nodes/deferred-context) 6. [Cost Relocation](https://agentic-atlas.dev/nodes/cost-relocation) 7. [Subagent Offload](https://agentic-atlas.dev/nodes/subagent-offload) 8. [Context Alignment](https://agentic-atlas.dev/nodes/context-alignment) 9. [The Session Bill](https://agentic-atlas.dev/nodes/session-bill) 10. field notes - “the travelling declared-shape contract specialization” Context AlignmentThe Session Bill unfold the map fold the map The card, in place · its connections drawn edges from atlas_links context-flow On this plate [definition](https://agentic-atlas.dev/nodes/context-flow#definition) [why-it-matters](https://agentic-atlas.dev/nodes/context-flow#why-it-matters) [model-and-claims](https://agentic-atlas.dev/nodes/context-flow#model-and-claims) [scope-and-boundaries](https://agentic-atlas.dev/nodes/context-flow#scope-and-boundaries) [implications-the-consequence-map](https://agentic-atlas.dev/nodes/context-flow#implications-the-consequence-map) [evidence](https://agentic-atlas.dev/nodes/context-flow#evidence) [relationships](https://agentic-atlas.dev/nodes/context-flow#relationships) [lineage](https://agentic-atlas.dev/nodes/context-flow#lineage) [open-questions-todo](https://agentic-atlas.dev/nodes/context-flow#open-questions-todo) [relationships-ledger](https://agentic-atlas.dev/nodes/context-flow#relationships-ledger) Every section is addressable on its own. Read only the ground you need. ## Definition [Permalink to Definition section](https://agentic-atlas.dev/nodes/context-flow#definition) **Context is a pipeline, not a pile.** An artifact is **admitted** into an [actor](https://agentic-atlas.dev/glossary/actor)'s [window](https://agentic-atlas.dev/glossary/window-context-window), **resident** for a span, then **evicted**. During residency it has a relative **placement** within the window and a changing recall profile: **recall distance** is the proportion of resident context admitted between the artifact's admission and an attempted use; **recall efficacy** is percentage accuracy on those attempts. All three belong to the resident artifact — the artifact, not the signal it carries, is the unit of recall. ## Why it matters [Permalink to Why it matters section](https://agentic-atlas.dev/nodes/context-flow#why-it-matters) The context-engineering family has prices (the economy) and moves (the mechanisms), but without flow it has no model of *movement*. Context gets discussed as a pile — a window that is some percentage full — while the questions that shape an architecture have no vocabulary: what enters whose window, when, where it sits, how far it must travel before use, how accurately it can be recalled, and when it leaves. ## Model and claims [Permalink to Model and claims section](https://agentic-atlas.dev/nodes/context-flow#model-and-claims) - **Model — the lifecycle verbs.** *Admission* is the event that loads an artifact into a window. Its trigger may be the actor's own **boot**: [inherited context](https://agentic-atlas.dev/glossary/inherited-context) such as the system prompt or memory-file lines arrives by lineage, chosen by nobody downstream. *Residency* is the span the artifact stays, and what [statelessness](https://agentic-atlas.dev/glossary/statelessness) re-bills every turn. *Eviction* ends residency through compaction, summarization, truncation, a [dispatch](https://agentic-atlas.dev/glossary/dispatch) [returning](https://agentic-atlas.dev/glossary/return), or a session ending. Eviction ends recall from the artifact and removes its steering trajectory ([Momentum](https://agentic-atlas.dev/nodes/momentum)'s second motive for eviction, beyond the budget arithmetic). - **Model plus empirical result — recall during residency.** In an append-growing window, recall distance can change an artifact's placement. Controlled evaluations show that recall distance and placement can each change recall efficacy — and the wider resident context matters on its own. The direct distance-to-efficacy path captures separation and interference that can matter even without a coarse placement change. The resulting profile need not decline monotonically and is conditional, not universal ([Liu et al. 2024](https://aclanthology.org/2024.tacl-1.9/); [Veseli et al. 2025](https://openreview.net/forum?id=vlUk8z8LaM); [Du et al. 2025](https://aclanthology.org/2025.findings-emnlp.1264/)). ``` recall distance ──▶ placement ────────┐ │ ▼ └──────────────────────▶ recall efficacy ◀── wider resident context ``` - **Measurement model — state, flow, outcome.** Placement is the artifact's state at the moment of recall, not merely where it was admitted. Describe it proportionally relative to both window boundaries rather than with durable token thresholds. The two boundary readings are complementary views of the same relative placement; total resident length remains a separate covariate. Recall distance is the flow of intervening context since admission, not wall-clock delay. Under ordinary appending it changes placement; reconstruction or reordering can make the two diverge. Recall efficacy is the outcome: one attempt produces a scored result, while comparable attempts yield percentage accuracy. Within this model efficacy does not feed back into the placement or distance already observed. - **Model — artifacts carry signals.** Placement, recall distance, and recall efficacy belong to the artifact actually resident. A signal is the fact, instruction, or evidence that may continue across representations. **Summarizing an artifact evicts the source and admits a new artifact** — even when the new one preserves the same signal or a subset. The replacement starts its own placement and recall-distance history. Information omitted by the transformation is a transformation-fidelity failure, not a recall failure against the replacement. ## Scope and boundaries [Permalink to Scope and boundaries section](https://agentic-atlas.dev/nodes/context-flow#scope-and-boundaries) Placement is a property during residency, not a lifecycle stage. Recall is an attempted use during residency, not a fourth stage. One artifact may therefore have several recall measurements over one residency. Recall efficacy is behavioral accuracy, not the artifact's raw attention weight, salience, or influence. Those may help explain a positional effect, but they are not substitutes for the measured outcome. Decay can reduce recall efficacy while an artifact remains resident — but decay is not eviction, the event that ends recall from the artifact. This is a concept — the model, not a move. It does not prescribe when to admit, what to evict, whose window to use, or where to place an artifact. Those are [Context Efficiency](https://agentic-atlas.dev/nodes/context-efficiency)'s questions. Nor does it claim a universal positional curve or fixed threshold; each profile is conditional on the model, task, prompt, artifact, resident context, and scorer. ## Implications — the consequence map [Permalink to Implications — the consequence map section](https://agentic-atlas.dev/nodes/context-flow#implications-the-consequence-map) - **The mechanisms become comparable moves.** Deferral delays admission and shortens residency; distillation shrinks what is admitted; subagent offload routes a segment through another actor's window; a dispatch return evicts the whole working set at the boundary. - **Eviction has two consequences.** It ends the economy's residency bill and removes the trajectory that momentum says resident context exerts. - **A transformation restarts the artifact lifecycle.** A summary may carry forward all or part of the source's signal, but its admission begins a new placement and recall-distance history. - **Recall claims need their conditions.** Percentage accuracy means little without the artifact, recall distance, placement, wider resident context, model, task, prompt, and scorer under which it was measured. - **A residency can be sampled, not summarized by one score.** Repeated recall attempts observe the same artifact at different placements and recall distances, producing a profile over its residency rather than one permanent efficacy value. ## Evidence [Permalink to Evidence section](https://agentic-atlas.dev/nodes/context-flow#evidence) - **Placement can change accuracy, but no curve is universal.** Moving the same answer-bearing material within a fixed prompt changes accuracy in many controlled long-context evaluations, while some models and tasks remain robust. Primacy can weaken or reverse as relative window occupancy grows ([Liu et al. 2024](https://aclanthology.org/2024.tacl-1.9/); [Veseli et al. 2025](https://openreview.net/forum?id=vlUk8z8LaM)). - **Distance and wider context can matter separately.** Intervening material can reduce accuracy through separation or interference, while total input length can hurt even when relevant evidence remains immediately before the question ([Wang et al. 2025](https://aclanthology.org/2025.findings-naacl.256/); [Du et al. 2025](https://aclanthology.org/2025.findings-emnlp.1264/)). - **Attention is not efficacy.** Positional-attention studies offer possible mechanism evidence, but the recall measure remains scored output accuracy ([Hsieh et al. 2024](https://aclanthology.org/2024.findings-acl.890/)). - **Lifecycle is the model's inference over the evidence.** Most controlled studies construct a completed prompt and vary position or intervening material. Mapping those results onto an artifact moving through an append-growing window is structural inference, not a directly observed multi-turn lifecycle. The full research trail is in the placement-and-recall synthesis. ## Relationships [Permalink to Relationships section](https://agentic-atlas.dev/nodes/context-flow#relationships) - **Dynamics, beside statics and objective:** [The Context Economy](https://agentic-atlas.dev/nodes/context-economy) prices what residency costs; this node models how context moves; [Context Efficiency](https://agentic-atlas.dev/nodes/context-efficiency) says what to optimize. - **The mechanisms execute on this pipeline:** [Deferred Context](https://agentic-atlas.dev/nodes/deferred-context), [Subagent Offload](https://agentic-atlas.dev/nodes/subagent-offload), and *the travelling declared-shape contract specialization* are each a move described in this node's verbs. - **Child: [Momentum](https://agentic-atlas.dev/nodes/momentum)** — a dynamics phenomenon of the pipeline: resident context does not just inform the model, it steers it. - Lifecycle and recall-term definitions (admission, residency, eviction, placement, recall distance, recall efficacy) live in the [glossary](https://agentic-atlas.dev/glossary); this node teaches the model. ## Lineage [Permalink to Lineage section](https://agentic-atlas.dev/nodes/context-flow#lineage) The working set model (Denning, CACM, 1968) and stack distance (Mattson et al., *Evaluation Techniques for Storage Hierarchies*, 1970): admission, residency, and eviction under a capacity bound, with reuse counted in intervening references, not elapsed time. Recall distance is that measure over admitted context. The delta: a cache hit is binary and placement-blind, while residency guarantees nothing and placement changes the odds. ## Open questions / TODO [Permalink to Open questions / TODO section](https://agentic-atlas.dev/nodes/context-flow#open-questions-todo) - Live-lifecycle evaluations: most evidence manipulates completed prompts, not repeated recall attempts across one artifact's residency. - Flavor-lane candidate: the pipeline metaphor is inherently narratable (admission gates, residency meters, eviction valves). The relationships ledger Evidence-bearing references ## Relationships Every connection keeps the section where it was found. The map above orients; this ledger carries the evidence. ### Outbound references 8 1. in-slice · occurrence 1 [Momentum](https://agentic-atlas.dev/nodes/momentum) how context already in the window steers the model along its current path Evidence: [Model and claims](https://agentic-atlas.dev/nodes/context-flow#model-and-claims) · occurrence 1 2. in-slice · occurrence 1 [Context Efficiency](https://agentic-atlas.dev/nodes/context-efficiency) how much task value you get for each unit of context spent Evidence: [Scope and boundaries](https://agentic-atlas.dev/nodes/context-flow#scope-and-boundaries) · occurrence 1 3. in-slice · occurrence 1 [The Context Economy](https://agentic-atlas.dev/nodes/context-economy) what each piece of context costs, in quality, dollars, and latency, and who pays Evidence: [Relationships](https://agentic-atlas.dev/nodes/context-flow#relationships) · occurrence 1 4. in-slice · occurrence 2 [Context Efficiency](https://agentic-atlas.dev/nodes/context-efficiency) how much task value you get for each unit of context spent Evidence: [Relationships](https://agentic-atlas.dev/nodes/context-flow#relationships) · occurrence 2 5. in-slice · occurrence 3 [Deferred Context](https://agentic-atlas.dev/nodes/deferred-context) keeping a short pointer loaded and fetching bulky context only when a session needs it Evidence: [Relationships](https://agentic-atlas.dev/nodes/context-flow#relationships) · occurrence 3 6. in-slice · occurrence 4 [Subagent Offload](https://agentic-atlas.dev/nodes/subagent-offload) handing work to a subagent so its material never fills the orchestrator's context Evidence: [Relationships](https://agentic-atlas.dev/nodes/context-flow#relationships) · occurrence 4 7. undisclosed · occurrence 5 Undisclosed relationship the travelling declared-shape contract specialization Evidence: [Relationships](https://agentic-atlas.dev/nodes/context-flow#relationships) · occurrence 5 8. in-slice · occurrence 6 [Momentum](https://agentic-atlas.dev/nodes/momentum) how context already in the window steers the model along its current path Evidence: [Relationships](https://agentic-atlas.dev/nodes/context-flow#relationships) · occurrence 6 ### Inbound references 9 1. in-slice · occurrence 2 [Context Alignment](https://agentic-atlas.dev/nodes/context-alignment#relationships) how context enters, stays in, and leaves a model's window, and how well it's recalled Evidence: [Relationships](https://agentic-atlas.dev/nodes/context-alignment#relationships) · occurrence 2 2. in-slice · occurrence 1 [The Context Economy](https://agentic-atlas.dev/nodes/context-economy#scope-and-boundaries) how context enters, stays in, and leaves a model's window, and how well it's recalled Evidence: [Scope and boundaries](https://agentic-atlas.dev/nodes/context-economy#scope-and-boundaries) · occurrence 1 3. in-slice · occurrence 3 [Context Efficiency](https://agentic-atlas.dev/nodes/context-efficiency#scope-and-boundaries) how context enters, stays in, and leaves a model's window, and how well it's recalled Evidence: [Scope and boundaries](https://agentic-atlas.dev/nodes/context-efficiency#scope-and-boundaries) · occurrence 3 4. in-slice · occurrence 2 [Context Efficiency](https://agentic-atlas.dev/nodes/context-efficiency#relationships) how context enters, stays in, and leaves a model's window, and how well it's recalled Evidence: [Relationships](https://agentic-atlas.dev/nodes/context-efficiency#relationships) · occurrence 2 5. in-slice · occurrence 1 [Cost Relocation](https://agentic-atlas.dev/nodes/cost-relocation#forces) how context enters, stays in, and leaves a model's window, and how well it's recalled Evidence: [Forces](https://agentic-atlas.dev/nodes/cost-relocation#forces) · occurrence 1 6. in-slice · occurrence 2 [Cost Relocation](https://agentic-atlas.dev/nodes/cost-relocation#relationships) how context enters, stays in, and leaves a model's window, and how well it's recalled Evidence: [Relationships](https://agentic-atlas.dev/nodes/cost-relocation#relationships) · occurrence 2 7. in-slice · occurrence 5 [Deferred Context](https://agentic-atlas.dev/nodes/deferred-context#relationships) how context enters, stays in, and leaves a model's window, and how well it's recalled Evidence: [Relationships](https://agentic-atlas.dev/nodes/deferred-context#relationships) · occurrence 5 8. in-slice · occurrence 1 [Momentum](https://agentic-atlas.dev/nodes/momentum#relationships) how context enters, stays in, and leaves a model's window, and how well it's recalled Evidence: [Relationships](https://agentic-atlas.dev/nodes/momentum#relationships) · occurrence 1 9. in-slice · occurrence 5 [The Session Bill](https://agentic-atlas.dev/nodes/session-bill#implementation-the-six-shifts) how context enters, stays in, and leaves a model's window, and how well it's recalled Evidence: [Implementation](https://agentic-atlas.dev/nodes/session-bill#implementation-the-six-shifts) · occurrence 5 [↑ back to the top](https://agentic-atlas.dev/nodes/context-flow#content) [← the survey](https://agentic-atlas.dev/atlas) Node context-flow · corpus 78c0e17 · Catalog revision e0cb75881244b1a82193ca738b82a0d508dd62e822524ae82873ec79d51dbb61