Container
Description
A bounded region of space, scope, or domain — there is an interior, an exterior, and a boundary that decides what crosses. Containment is one of the most pervasive cognitive primitives because it grounds three independent moves at once: scope (what does the rule apply to?), encapsulation (what does the consumer see vs not see?), and transition (what changes when something crosses the boundary?). The diagnostic: when a question implicitly asks “is X inside or outside Y?” — what’s in scope, what counts as covered, what the boundary lets through — the container schema is the right primitive to reach for.Triggers
User-initiated: User asks about scope, namespacing, encapsulation, “what counts as,” “what is inside this” — anywhere the question implicitly asks about an in/out boundary. Agent-initiated: Agent recognizes that a system has a boundary the right side of which an item must be on to count, be visible, or be affected. Candidate inference: “what does the boundary let through; what does it block?” Situation-shape signals: Anywhere “scope” makes sense. Anywhere “the rule applies inside but not outside” is the right framing. Anywhere a “wall,” “skin,” or “shell” metaphor lands without being weird.Exclusions
- Truly continuous / unbounded fields — gravitational fields, magnetic fields, market sentiment. The “where does it end?” question doesn’t have a sharp answer.
- Network or graph structures — graph nodes don’t have an interior/exterior; the connectivity is the structure, not the containment. Forcing container framing onto graph-shaped reality misrepresents.
- Process-shape rather than space-shape phenomena — feedback-loops, cadences, gradients aren’t containers; they’re shapes through time, not through space.
Structure
Relationships
- leaky-abstraction — leaky-abstraction is container + projection; the container is supposed to hide the substrate but the projection isn’t invertible so the substrate bleeds through.
- surface — the boundary of a container is its surface; the relationship is intimate enough that some treatments collapse them (the catalog separates them because the questions you ask differ).
- route-as-context — the route is a container; “the path is the meaning.”
- vertical-slice — a vertical slice is a thin container that crosses every stack layer; container + grain.
- grain — what counts as a single container shapes everything: a session vs a request vs a user vs an org is a container at a different grain.
Examples
Cell membranes in biology · biology
Cell membranes in biology · biology
Geographic / political boundaries · geography
Geographic / political boundaries · geography
HTTP context / sessions / transactions · computer-science
HTTP context / sessions / transactions · computer-science
Lakoff & Johnson (1980), *Metaphors We Live By* — CONTAINMENT image schema; foundational. · linguistics
Lakoff & Johnson (1980), *Metaphors We Live By* — CONTAINMENT image schema; foundational. · linguistics
Mark Johnson (1987), *The Body in the Mind* — extends the image-schema treatment. · linguistics
Mark Johnson (1987), *The Body in the Mind* — extends the image-schema treatment. · linguistics
Object encapsulation · computer-science
Object encapsulation · computer-science
Set membership in mathematics · mathematics
Set membership in mathematics · mathematics
Talmy (2000), *Toward a Cognitive Semantics* — formal articulation of force-dynamics + containment. · linguistics
Talmy (2000), *Toward a Cognitive Semantics* — formal articulation of force-dynamics + containment. · linguistics
Variable scope / namespaces in programming · computer-science
Variable scope / namespaces in programming · computer-science