# Container Design

URL: https://mechanisticmindset.com/wiki/container-design
Tags: system-architecture, practical-application

# Container Design

#system-architecture #practical-application

## What It Is

A **container** is a bounded context that makes some activities possible, excludes others, and changes the probability of what happens inside it. A gym, timer, walk, OBS recording session, work-only laptop, or job can provide that boundary. Container design changes behavior by changing the context people enter.

The container is the unit of behavior design. It sets the [macrostate](/wiki/statistical-mechanics) conditions within which behavioral microstates are sampled. In the terms of [Intelligence Is Water](/wiki/intelligence-is-water), it gives the flow a riverbed. Designing one for yourself is the same move as designing a DSL for an AI agent: the available structure determines what the process can do.

In a June entry, Will said this belonged in a book "if ever I were to write a book":

> "It's a special environment that constrains the types of activities possible and enforces rules about those activities — when, where, how often. It increases probabilities of certain activities... like enzymes interacting because of regulated temperature."

The cell comparison describes control through conditions. A cell maintains a membrane and regulates temperature; reactions follow within those conditions. "The container is like a cell. The container is the thing that creates the environment... everything is about container. It's container engineering."

## Environments Are Runtimes

An environment acts as a **runtime** that loads and executes behavioral scripts, mostly without a decision:

> "Home is a bad runtime that reloads YouTube / porn / drift scripts, while outdoor walking creates generative thought that feels endogenous rather than injected."

Will observed the same state-dependent change repeatedly. "This environment — my home — feels suffocating... activates the YouTube state." Another entry recorded: "As soon as I enter home, it's time to go to sleep." Leaving home stopped loading the YouTube, lounging, and masturbation loops. Their strength had not changed; the runtime that invoked them was absent.

[Buffs and debuffs](/wiki/buffs-debuffs) describe the corresponding probability changes. An environment applies them whether or not its occupant planned for them.

| Runtime | Scripts it auto-loads | Valence |
|---------|----------------------|---------|
| Home room | YouTube, porn, lounge/sleep, drift | Consumption default |
| Outdoor walk | Generative thought, dictation, ideation | Generative default |
| Commercial gym (right one) | Training, staying, next set | Productive lock-in |
| Timer / OBS session | Focused work, "I am in the mode of doing this" | Declared mode |
| Job / school | Assigned work, structured hours | Externally scaffolded |

This changed what Will meant by luxury:

> "Luxury is runtime execution — not owning the thing, but having an environment where the thing actually runs."

An unused squat rack provides less than a gym in which training happens. The test is observed behavior: "Even if something logically makes sense, reality has variables you are not accounting for. The real test is empirical: is it actually working? Am I actually going to the gym regularly or not?" Execution counts alone validate a container. This applies [reality contact](/wiki/reality-contact) to the environment itself.

In April, a home-adjacent gym option kept failing. Walking to Fitness SF, with its selectorized machines, changed what happened:

> "My mental state is like a microstate within the gym environment. The macrostate is the selectorized machines, which bend the probability that I will pick something up and stay with it."

The arrangement made those actions more likely "until those actions dominate." Training followed from entering the runtime.

## Freedom Needs a Container

Unbounded freedom diffuses into whatever activities are easiest. It expands like gas into available space without doing useful work:

> "Every time I hear the word 'freedom' I should think 'needs container' — because freedom means desire to explore these microstates, but then we have to construct those macrostates to make sure that it converges."

> "You know what I learned is freedom is bad. Total freedom is bad. It leads to YouTube."

People discount containers "because they compare to their willpower": they imagine freely choosing well without constraints. But open space selects the lowest-cost attractor. A boundary can preserve choice within a region that still converges. Will applied this to other people too: "I'm not controlling, I'm shaping their environment. They still have autonomy... you unlock layers of trust."

Distinguish **enablers** from **attractors**. Freedom, money, capability, runway, equipment, and spare time make an activity possible. They do not make it start. They supply neither a next action nor a narrower set of choices. If a life has many enablers and few attractors, whatever is nearby supplies the pull.

Will noticed this while living in the apparently ideal arrangement of runway, unlimited time, and equipment at home:

> "The conditions are perfect, but they're enablers. They're not attractors. The right configuration exists, inhabiting this right configuration also exists, but it's too leaky. I need to define the right configuration or the right macro state."

A container provides the pull that turns a possible state into one someone actually occupies.

The strongest evidence for Will came from the role of set and setting in a psychedelic session:

> "It's not just the timing — it's also about location, it's about the clothes you wear, it's about your plan."

> "It felt like I could rewrite myself. It felt like, because of the container, I could rewrite myself... I feel like I am exporting that insight into all the domains of my life."

His intended result was an arrangement that continued producing value without continually feeling effortful:

> "I like to do things where I don't think about it, and it just adds up. If I can construct the container, then I can just live on with my life. It doesn't have to feel like I am doing anything that adds up. That's the big idea: construct a container."

Living inside the boundary compounds without registering as work. The container pays [activation energy](/wiki/activation-energy) once at entry instead of repeatedly during the activity.

## Leakiness and the Vacuum

A configuration with resources but no pull loses time through repeated moments in which nothing directs the next action. The strongest available container takes over by default.

A main project can rank above a day job on paper while the job occupies 9-to-7 and the project loses every evening to the feed. The job supplies waking pressure, a place, people, and a cadence. The declared priority supplies none of those. Priority has no effect until it has a container.

The gap is especially sharp when a deadline, job, or crisis ends:

> "The old emergency container disappeared and no replacement work container automatically loaded, leaving feeds as the strongest available attractor."

Knowing what should happen next does not fill the open schedule. The missing part is a replacement with a route into it. The end of the current container is a predictable event, so build its replacement before the gap opens.

The inverse problem is **capture without ignition**. A well-equipped board can record everything while providing no reason to enter the work. Comparing the same engine across two task boards made the difference visible: finished work within 48 hours showed that throughput was available under a container, while "the personal board has capture without ignition." Without that structure, the next task has to be generated at the moment of greatest weakness. A capture system alone does not supply the start.

## Constraint as Discovery

A five-figure supply of unused cloud credits showed Will that capability did not identify its own purpose:

> "I can't proceed from capability... I can only proceed from constraint. I need to discover it through constraint, walking through those constraints... It's almost like a principle: you can only discover what you need via the constraints."

Abundance adds possibilities without selecting actions. Scarcity makes the resource's function visible: "the function of a resource becomes clearest at the edge of its absence." The relevant state is **resources × urgency**. "I had the resources but no urgency, but now I have no resources and I have urgency" described a second state that was more productive than the first.

The design problem is to cover the floor without allowing the safety net to remove urgency. Constraints also reveal priorities:

> "If I had boundless free time and endless options, I would do anything, but the constrained environment forced me to discover and decide what was actually important."

The boundary supplies information about what is needed and what the available resources are for. Freedom alone supplies none of that selection.

## A Container Taxonomy

A container need not be a room: "the AI is a container, your workflow is your container, your environment is your container."

| Kind | Examples | Boundary mechanism |
|------|----------|-------------------|
| Spatial | Gym, library, walk route, work-only laptop | Physical entry/exit cost; equipment defines the activity menu |
| Temporal | Timer, OBS session, sprint, "morning block" | Declared start/stop; the clock enforces the mode |
| Social | Job, school, standing meeting, workout partner | Other people's expectations hold the boundary for you |
| Ritual | Warm-up sequence, recording light on, specific clothes | Crossing marker that loads the mode |
| Chemical/physiological | The psychedelic session, caffeine timing | State change bounds what cognition is available |
| Institutional | Accelerator, degree program, employment | Structure as a service: ambiguity pre-resolved at scale |

Every real container answers when, where, and how often before another decision is needed. Its boundary also has to be perceptible from inside. A timer works because "it's a container that implicitly says: I am currently in the mode of doing this." An imperceptible boundary does not influence the choice.

## The Occupant Enforces the Boundary

A calendar label does not itself protect the activity:

> "An empty boundary is a fence around nothing. It has no defender. The occupant is the enforcement mechanism."

An empty block remains available to YouTube. Evening behavior expands into the space actually unoccupied, regardless of the label. Once the lesson is loaded or the gym entered, the person is already doing something. Leaving now means abandoning work in progress and carries a cost.

Enforcement therefore requires one unit of [ignition](/wiki/ignition) at the start, rather than repeated [resistance](/wiki/willpower) during the block.

Will worked this out while arranging mornings for his body and evenings for contract work and Korean. Neither “protect your time” nor “do or do not” explained how the schedule should hold: "I felt like this could be given more specificity without resorting to mysticism to seem wise."

The distinction explained the earlier schedules that decayed:

> "The block existed on paper before the practice existed in reality. I was building fences first and hoping the livestock would show up. The order is backwards. Practice first; the boundary condenses around it."

A decaying boundary is empty, so fill it rather than defending its label harder. A dashboard has the same obligation: keep the activity ready to run, not merely display its allocated block. A parked thread does not enforce the boundary.

## Attractor-State Design

[Ignition](/wiki/ignition) reduces the cost of starting. Attractor-state design makes continuing easy and stopping expensive.

Will's unplanned 9-hour walks showed the effect: "I explicitly said, 'I'm going to stop at three hours,' but then I just continued onward."

> "The reason why I continued to walk was because at one point, I would have to decide to go back. Walking is one of those things where once you start, it's hard to stop — because you have to go back. And the further you are, the harder it is to go back."

Continuing at a desk requires another decision each minute. Continuing a walk is the default; stopping requires choosing to return, walking uphill, or interrupting the flow with a taxi. The route supplies momentum through its exit cost.

> "That's how we need to create those attractor states for things that are naturally productive. Go out and find the things where you can continue for hours — because, just like walking, they convert into productive energy when you have the systems that convert it."

The capture system is part of the requirement. The walk creates retained output because Plaud records it. Hours of flow without capture leave no artifact. [Agent Body](/wiki/agent-body) describes the machine version of providing somewhere persistent for output to go.

> "If you want to do something for a long time, just make it hard to stop. Make it hard to stop and also make it fun to continue. It's just about the environment engineering."

Distance and ritual can supply that cost. Walking to the gym creates "a ritualistic boundary such that when you go there, you just want to stay there." A home gym downstairs fails because leaving costs nothing; easy exits guarantee collapse.

This is Boltzmann selection over an energy landscape. [Gradients](/wiki/gradients) determine the pull, and [activation energy](/wiki/activation-energy) determines the transition costs. Designing an attractor deliberately deepens the local well.

## Mode-Lock

[Mode-lock](/wiki/mode-lock) is Will's strong behavioral inertia. It holds a mode for hours, reinforces identity, and can collapse a whole behavioral sequence when its anchor is removed. The container initializes that lock.

Entering the gym loads the mode: "as soon as I just enter the gym for like five minutes, I flip my mind to: oh, I'm a gym person". The exit cost keeps another activity from preempting it. In [attention routing](/wiki/attention-routing), attention is directed once at entry instead of every minute. In a [state machine](/wiki/state-machines), the raised exit cost makes the state absorbing.

The lock does not distinguish useful from harmful activity. Choosing the container determines what it holds in place.

## Pressure Needs Structure

Pressure alone did not produce Will's best work:

> "I do not work well under pressure. I work well under structure for that pressure to channel through. If I don't have the structures available to me, pressure is not going to solve it. Pressure gives you impetus to create those structures."

> "I don't want pressure. I want structure. Structure is good because it still allows freedom — I need a structured schedule where my time is allocated, and then I have the freedom within it."

Deadline pressure, financial pressure, and urgency from doom content all degrade performance without a process to receive them. "watching [doom content] gives me urgency without structure. Structure means: do I know what the rest of the day is going to look like?"

Pressure can power a turbine when there is a channel through it; applied to an unstructured day, it creates stress. Its only legitimate role is to prompt construction of the channels. Once they exist, "you can amp up the intensity."

| Input | Without structure | With structure |
|-------|------------------|----------------|
| Deadline pressure | Shutdown, avoidance | Intensity dial |
| Urgency (news, doom content) | Anxiety, "agency is removed" | Ignored or converted |
| Ambition | Diffuse guilt | Scheduled throughput |
| Free time | Diffusion into low-cost attractors | Caught by a container |

This raised a question about what institutions provide:

> "I'm wondering how much structure school actually gives you. How much structure does a company actually give you?... What is actually needed when you need to design your own structure? I would like to study what type of structures school gives you, or your job gives you."

Schools, jobs, accelerators, and investors provide **structure as a service**. "That's one of the things that feels scary when you're out of school, out of an accelerator program, when you don't have VCs — when you don't have structure."

A founder has to supply that structure personally. Part of a job's compensation is having ambiguity resolved: "you get to see what happens when all the ambiguity is taken care of for you — the world does not need to be so scary". Will connected it to his own history: "I feel like I am actually super successful within structures — that's why I excelled at school as a kid."

Leaving an institution therefore requires deliberately replacing each container it supplied. The conclusion is not a requirement to return to the institution; it is a requirement to replace its functions.

## Designing Containers for Others

Commands require repeated enforcement. Unbounded freedom disperses. A designed context gives another person freedom over the particular actions, order, and style within a bounded class of activity:

> "I'm not controlling, I'm shaping their environment. They still have autonomy... you unlock layers of trust."

Managers, parents, and teachers can provide this structure. Will described the engineering role:

> "I can help them construct the container where they can feel the most productive... a senior engineer should design a container for the other engineers to go in with AI."

The senior engineer builds the harness, conventions, and verifiers within which less-experienced engineers and AI produce good work by default. That gives the group the kind of guidance the selectorized machines provide in the gym.

Authorship also carries an obligation to check the fit. A container designed for one person can confine another, regardless of the designer's intentions.

## Failure Modes

**Free time arrives before a protocol.**

> "I do not really hate time itself. The problem is free time arriving before a protocol does. When unstructured time opens up without a preassigned macrostate, discretized menu, and low-friction first move, it diffuses into low-cost attractors and later registers as regret. The solution is to build containers that catch time the moment it opens."

The lowest-energy attractor in reach already has a claim on unallocated time.

**The container becomes a prison.** Fit varies with the person and the season:

> "It was interesting watching the same container that is helping me become a prison for somebody else."

There is no universal container. Check whether the present boundary still directs useful activity or has begun to confine it.

**Weak containers are bypassed.** Appetites also follow the [available routes](/wiki/intelligence-is-water): "mind and body adapt to whatever constraints are truly enforced; addiction will route around weak constraints." A known bypass leaves the unwanted path open. [Prevention architecture](/wiki/prevention-architecture) requires the boundary itself to hold, independently of intention.

**[Mode-lock](/wiki/mode-lock) holds the wrong activity.** If the runtime loads YouTube, the same mechanism can hold it for two and a half hours.

**Enablers are mistaken for attractors.** Runway, time, equipment, and access allow activity but do not start it. An inventory with no source of pull has identified where time is leaking.

**Pressure is mistaken for a container.** A deadline supplies pressure without terrain. If urgency is the only structure, expect shutdown rather than output.

## Building Containers

The April–June observations produced this procedure:

1. **Inventory the runtimes.** For home, desk, gym, phone-in-hand, and walking, record what happened on the last ten occasions. Use actual execution rather than intended activity.
2. **Match an activity to a boundary.** Ask where the activity executes. If no such context exists, build one before attempting it again.
3. **Set conditions and leave the interior free.** Specify when, where, and what kind of activity belongs. Leave the particular sequence open, as regulated conditions allow enzymes to interact without commanding each reaction.
4. **Make stopping expensive.** Use distance, a ritual boundary, or a framed session. Declare the mode at entry; a timer "implicitly says: I am currently in the mode of doing this".
5. **Connect capture.** Dictation records a walk, commits retain a session, and [tracking](/wiki/tracking) retains results. The attractor compounds only if something persists.
6. **Validate and replace.** Execution count is the only metric. Replace a context that does not produce the activity rather than renewing the same resolution.

[Zeitgebers](/wiki/zeitgebers) can schedule entry through an external rhythm, removing another daily decision.

| Block | Container | What executes by default | Exit cost engineered by |
|-------|-----------|-------------------------|------------------------|
| Morning | Walk + dictation | Generative thinking, captured | Distance from home grows with every step |
| Midday | Gym (walkable, machine-dense) | Training, staying for the next set | Ritual boundary; the trip itself |
| Afternoon | Library / work-only laptop | Deep work under mode-lock | No other scripts installed on the device |
| Evening | Timer / recording session | Focused shipping | Declared mode; the session frames stopping as an event |
| Open time | Pre-built protocol container | Whatever the menu says | Free time is caught the moment it opens |

The day becomes a sequence of contexts that each handle a class of work. Decisions are made at design time, so none is required during execution. Willpower is spent creating the boundaries rather than enforcing them repeatedly.

## Integration with the Mechanistic Framework

### Connection to [Intelligence Is Water](/wiki/intelligence-is-water)

Containers shape the available paths for behavioral flow. They direct generative activity, while enforced boundaries are the only constraints appetites cannot route around.

### Connection to [Macrostate Engineering](/wiki/macrostate-engineering)

A container is a macrostate with a physical boundary. Define the aggregate conditions, enter the context, and leave the specific microstates free to resolve within it.

### Connection to [Statistical Mechanics](/wiki/statistical-mechanics)

The environment changes the energy landscape, placing desired behavior in a low-energy basin. The container is a locally engineered Boltzmann distribution.

### Connection to [Forcing Functions](/wiki/forcing-functions)

A forcing function acts at a point in time; a container sustains a field of influence. The first can cause entry, while the second keeps the activity going inside.

### Connection to [Ignition](/wiki/ignition)

Ignition handles starting, and attractor-state design handles continuation. A complete container has a low entry cost and a high cost of leaving its mode.

### Connection to [Agent Body](/wiki/agent-body)

An AI agent's constraints and persistent interfaces determine its effective behavior more than its raw capability. Designing those conditions and designing a person's containers use the same discipline.

## See Also

- [Intelligence Is Water](/wiki/intelligence-is-water) - Shaping the routes behavior can take
- [Macrostate Engineering](/wiki/macrostate-engineering) - Physically bounded aggregate conditions
- [Prevention Architecture](/wiki/prevention-architecture) - Enforcing a boundary against bypasses
- [Buffs & Debuffs](/wiki/buffs-debuffs) - Environmental changes to action probabilities
- [State Machines](/wiki/state-machines) - States with expensive exits
- [Activation Energy](/wiki/activation-energy) - Paying the starting cost at entry
- [Forcing Functions](/wiki/forcing-functions) - Events that cause a boundary crossing
- [Zeitgebers](/wiki/zeitgebers) - External rhythms that schedule entry
- [Attention Routing](/wiki/attention-routing) - Directing attention when a mode starts
- [Mode-Lock](/wiki/mode-lock) - The persistence initialized by a container
- [Gradients](/wiki/gradients) - Why the strongest available pull wins
- [Ignition](/wiki/ignition) - Making the start affordable
- [Agent Body](/wiki/agent-body) - Designing containers for machine agents