Context Overflow
Dynamic · Working definition · Checked against project sources, 19 October 2026 · Not externally verified
Context Overflow: Each new conversation requires so much background that explaining the situation uses up the capacity available to work on it.
What it looks like
Every new person entering a situation means rebuilding the full picture from scratch. The person explaining faces a structural choice: compress and lose accuracy, or stay accurate and lose the listener. Some situations are genuinely multi-factorial, and the expectation of a single-cause explanation is a model of how problems work, not a fact about this one.
Context can also land as pressure. A listener without slack may experience more context as more load, and a listener trained to spot manipulation may hear it as a tactic.
Illustrative example
Illustrative (constructed). A person describes the same history to a fourth helper this month. By the time the account is finished, little time or attention is left for deciding what to ask for.
What tends to help
- A shared, revisable map, so the history does not have to be retold. What goes on it is the owner’s choice (see the Lexicon’s entry on two boards).
- Say what the context is for, and tie each piece to a move: a question, a person to ask, a resource, a sequence.
- Ask before adding, and match the amount to the listener’s bandwidth.
- Invite correction, for example by asking the listener to say if this sounds like dodging.
The last three moves come from a draft protocol that is still the author’s call and has not been tried in practice.
Related
Referral Loop (each referral restarts the explanation) · Connection/Deflection Ambiguity · Command Collision · Lexicon
Claims and sources
Claim: Each new person entering a situation means rebuilding the full picture from scratch.
Status: Source claim
Source: Story Dynamics proposal (unpublished), pattern table
Claim: The person explaining must trade accuracy against the listener’s capacity.
Status: Source claim
Source: Mode-switching taxonomy (unpublished), Context Overflow entry
Claim: More context can register as more load for a listener without slack.
Status: Source claim; the notes cite Mullainathan and Shafir, not re-checked here
Source: Liminality lineage notes (unpublished), section 17
Claim: Saying what the context is for, and tying it to a move, lowers the chance it reads as deflection.
Status: Hypothesis
Source: Liminality lineage notes, draft protocol marked as the author’s call; untested
Status key: Checked = verified against a primary source. Source claim = stated in a source and not independently checked. Hypothesis = proposed and untested. Illustrative = constructed example, not a documented case.
Open questions
Does a shared map reduce repeated explanation in practice? Not yet tested. A composite or consented example can be added with its source, date and status.
Development sources: Story Dynamics proposal and mode-switching taxonomy (unpublished); Liminality lineage notes (unpublished), sections 16–17.
