Daily Life

Here’s how it works:

The building’s systems generate data as a byproduct of function, not as a goal. The food delivery system knows whether food was consumed, because unconsumed food is returned. The clothing system knows what was sent back. The environmental controls know when the unit was occupied, because temperature management requires it. The cleaning schedule knows whether access was granted. None of this is surveillance in the meaningful sense — it’s the ordinary data of a provisioning system doing its job — but in aggregate it creates a picture of how a person is actually living.

The enrolled individual consented to this at intake. Not in fine print — explicitly, in one of the twenty-four agreements. The Data and Provisioning Agreement specifies exactly what signals the system collects, what they are used for, and what they are not used for. They are used for provisioning calibration and wellbeing assessment. They are not used to monitor behavior, relationships, speech, or anything the person does in the privacy of their unit. The Arbiter knows you didn’t eat your dinner three nights in a row. It does not know what you were doing instead.

The intervention threshold is high and graduated. A single anomaly generates nothing. A pattern generates a gentle signal — a message on the unit device from the building’s wellness coordinator. A sustained pattern generates a wellness check — a human, not an automated system. Actual intervention is the last resort and requires a specific escalation protocol that the enrolled individual agreed to at intake, and that is designed to feel like care rather than surveillance, because it is care rather than surveillance.

The socialization problem is solved not through monitoring but through architecture and design. You don’t need to track whether someone left their apartment. You need to design a building where leaving your apartment is the natural, frictionless, pleasurable thing to do — where the building itself creates the conditions for social connection without requiring it. More on this in the description below.

The Building

What follows is a day-in-the-life description of a specific Arbitration residential building — let’s call it simply a Type Four, which in Arbitration’s internal classification means a building for enrolled professionals in their thirties and forties who are occupationally intensive, socially selective, and provisioning-preferential. No cooking. High privacy baseline. Strong occupational output. Assessed as benefiting from structured social contact they would not generate independently.

There are forty-seven units. All forty-seven residents are enrolled. The building is owned outright by an Arbiter subsidiary, built to specifications developed through twelve years of provisioning data, designed by an architectural firm whose principal was herself enrolled and whose occupational assignment was exactly this.

The Physical Plant

The building does not look institutional. This was a design requirement, because the psychological research is unambiguous: people’s experience of their home is shaped by whether it feels chosen, and a building that looks like a facility feels unchosen regardless of how good the provisioning is. The building looks like a well-designed residential building in whatever city it occupies. The lobby is warm and specific — not hotel-generic, but calibrated to the assessed aesthetic preferences of its residents, which in this building run toward the particular combination of material warmth and visual simplicity that characterizes people who have spent too much of their lives in open-plan offices and have a compensatory craving for texture and enclosure.

Behind the lobby, invisible to anyone entering, is the building’s operational infrastructure — the systems that make the provisioning work at the scale and precision that Arbitration requires.

The provisioning corridor runs the full perimeter of each residential floor, accessed not through the hallways where residents live but through a separate service circulation route that building staff use exclusively. Residents never see the provisioning infrastructure in operation. Deliveries do not happen through the front door. Packages are not left in hallways. The building’s operational life and the residents’ domestic life are completely separated, because the research — Priya Mehta’s original research, refined through decades of enrolled population data — showed that the visibility of provisioning operations was one of the most reliable predictors of the psychological failure mode where enrolled individuals began to feel managed rather than cared for.

Each unit has two connection points to the provisioning corridor. The first is the food interface — a climate-controlled pass-through built into the kitchen wall, with separate compartments that maintain hot, cold, and ambient temperatures independently. The second is the garment interface — a larger pass-through adjacent to the unit’s dressing area, with hanging space on one side and folded-garment shelving on the other, that functions as the connection point for clothing provisioning.

Both interfaces are accessible from the provisioning corridor without anyone entering the unit. The resident interacts with them only from inside. From the resident’s perspective, food and clothing simply appear in designated spaces, maintained at the correct conditions, ready to use.

A Tuesday in the Building

5:47 AM

The unit’s environmental systems have been tracking the resident’s sleep cycle through the mattress’s pressure and temperature sensors — which exist for climate regulation purposes and generate the sleep data as a byproduct, not a goal. The data shows the resident is in a light sleep phase. At 5:47, the bedroom’s light level begins its transition — not an alarm, not a sound, but a slow brightening of the eastern-facing window panel that mimics the specific light curve of a clear morning at this latitude, starting below the threshold of perception and arriving at gentle dawn-light by 6:15.

The resident wakes, or doesn’t. If they don’t, the system recalibrates. There is no alarm that must be snoozed, no obligation to account for the non-waking. The system knows what time this resident needs to be functional for their occupational assignment and works backward from there. On days when the occupational schedule is lighter, the light curve starts later. On days when it is demanding, it starts earlier. The resident does not set an alarm. The building manages their morning.

6:15 AM

The resident showers. The water is at the temperature their profile specifies — not the temperature they set each time, but the temperature that was determined, through intake assessment and the first six weeks of enrolled residency, to be the temperature at which they actually shower rather than the temperature they think they prefer. These are often different. The distinction matters because one produces a five-minute shower and the other produces an eleven-minute shower, and the eleven-minute shower is the one this resident’s profile indicates they need.

The bathroom is clean. It was cleaned yesterday afternoon, during the window the resident specified on their unit device as their preferred cleaning window — 2 to 4 PM on weekdays, when they are invariably at work. The cleaning team entered through the service corridor using a code that changes daily and is generated by the building’s access system. They cleaned to a standard that the resident cannot achieve in the time they would be willing to spend, using commercial equipment that produces results no consumer product matches. They did not move any of the resident’s personal items. The protocol is explicit: nothing is relocated, nothing is reorganized without specific instruction. The cleaning is of surfaces, not of arrangements. The resident’s life is their own. The surfaces belong to the building.

6:35 AM

The food interface has been active since 6:00. Behind the pass-through, the morning’s provisioning arrived at 5:30 from the building’s central provisioning kitchen — a facility three floors below street level that serves all forty-seven units and whose operation the residents never encounter. This morning’s delivery for this resident includes a hot breakfast calibrated to their current health data — the building’s passive health monitoring, which runs through air quality sensors and the mattress system and generates no individual health record but does flag patterns that the provisioning system uses for calibration — and a cold component and a beverage.

The resident opens the food interface from inside the kitchen. The hot compartment contains what it contains. The resident did not choose it this morning. They chose, at intake, the parameters of their food provisioning — preferences, restrictions, cultural context, the specific foods they find comforting versus the foods they find optimal, the days when they want something indulgent versus the days when they want something that serves their physical performance. The provisioning system runs these parameters against the current health data and the day’s occupational demands and produces a recommendation that the provisioning kitchen executes.

If the resident opens the interface and feels, this morning, that they cannot eat what’s there — that something is wrong, that the food is not what they need today — they can note this on the unit device. The notation goes into the provisioning record. Three such notations in a week generates a check-in from the building’s wellness coordinator. Not a reprimand. A check-in, from a human, whose role is to understand what’s happening and whether the provisioning calibration needs adjustment or whether something else is going on.

The resident eats. The empty containers go back through the interface. They will not wash them. There is nothing to wash. The containers are the building’s containers, returned to the provisioning kitchen through the corridor system, cleaned and reused. The resident’s kitchen has no dish soap, no sponges, no drying rack. The kitchen is for eating, not for the management of eating.

7:15 AM

The garment interface. Yesterday’s clothing went back through the pass-through last night — the resident places worn items on the return side of the interface before bed, and they are collected overnight by the provisioning team. This morning’s clothing is on the other side.

The resident did not choose today’s outfit. They specified, at intake, their occupational dress context — in this case, professional but not formal, with a preference for darker colors, natural fabrics, and a specific fit profile that was captured during the intake physical assessment. They specified that they prefer not to think about clothing. This preference was noted, weighted, and acted upon. Each morning’s garment selection is made by the provisioning system based on the day’s schedule — pulled from the building’s central wardrobe allocation, which holds the resident’s full wardrobe in a climate-controlled facility one floor below — weather, any noted events or meetings, and the resident’s recent clothing rotation.

The clothing arrives on the hanging side of the interface for items that should hang, folded on the shelf side for items that should be folded. They are the resident’s clothes, in the sense that they are calibrated to the resident’s measurements and preferences. They are not the resident’s clothes, in the sense that they belong to the provisioning pool, are maintained and replaced by the building’s system, and will eventually be reallocated when the resident’s profile changes or when the items wear out. The resident does not own a wardrobe. They have a wardrobe, which is different, and the difference is one of the things enrolled people describe as either liberation or estrangement, depending on who they are and how they arrived at enrollment.

The resident gets dressed. The clothing fits. It is appropriate for today. There is no decision. There is no mirror-time consumed by uncertainty. There is simply a person, dressed correctly, who can now direct their attention to other things.

7:45 AM

The resident leaves for work. The unit door locks behind them. The building’s systems register the departure — not through surveillance, but through the routine data of a building that needs to know when units are occupied for climate management purposes. The unit temperature adjusts to an unoccupied setting. The food interface receives the day’s lunch delivery at noon, which will be held at temperature until the resident returns.

In the lobby, two other residents are also leaving. The three of them have crossed paths in this lobby perhaps forty times since the building opened. By this point, they know each other’s rhythms. Not their secrets, not their inner lives, but their rhythms — the comfortable ambient knowledge of people who share a building and have been sharing it long enough for that sharing to feel like something.

This is the building’s social architecture in its least glamorous form: the accumulation of ordinary lobby encounters, elevator rides, and package-less hallways that turn strangers into recognizable presences. The building was designed for this. The lobby is sized and arranged so that it is a place people pass through rather than hurry through. The resident cannot exit the building without crossing this space. This is not surveillance. It is architecture as social infrastructure, and it works the same way it has always worked in buildings where people actually live rather than merely sleep.

The Social Layer

The forced socialization problem you’ve identified is genuinely difficult, and the right solution is probably not to force it at all but to make it unnecessary to force. Here’s the design principle: you cannot make people want to socialize, but you can make the conditions for natural socialization so present and so frictionless that people who are capable of wanting it find it happening.

The building has three shared spaces that are not amenities in the hotel sense — not a gym, not a business center, not a rooftop terrace with Instagram potential — but spaces that serve functions the residents actually need, around which social contact naturally crystallizes.

The communal dining room is available every evening from 6 to 9 PM. Dinner can be taken in the unit, through the food interface. It can also be taken in the communal dining room, where the same provisioned meal is served in a shared setting with whoever else has chosen to eat there tonight. The resident does not RSVP. They do not plan. They decide at 6:30 whether they want to eat alone or with people, and they act accordingly. The dining room is sized for twelve — not a crowd, not a party, but the number of people at which conversation happens naturally across a table. On most nights, between four and nine residents eat there. On some nights, the table is full and the conversation is good and people stay past 9. On some nights, only two people show up and eat mostly in comfortable silence and that is also fine.

The building’s provisioning data shows who ate in the communal dining room and who didn’t — because the food interface tracks this, as it tracks all provisioning, for calibration purposes. It does not use this data to assess sociability or flag residents who prefer to eat alone. It uses it to calibrate portion sizes and meal timing. The social data is a byproduct. It is not a goal.

The building’s wellness coordinator is a person — always a person, never an automated system — who lives in the building and whose occupational assignment is the wellbeing of the building’s residents. Not a therapist. Not a manager. A coordinator: someone who knows the residents, who is available, who notices when someone’s provisioning patterns suggest something might be off, and who can have a conversation about it in the way that a person who knows you and lives near you can have a conversation that a clinical service cannot.

The wellness coordinator’s interventions are almost always small. A knock on the door. A mention over dinner that they noticed the resident hadn’t been down in a while. An offer to have coffee. The escalation protocol — which is real and is in the enrollment agreement — is almost never activated, because the small interventions work, and they work because they are human.

The unit device is not a smart home system in the consumer sense. It is the resident’s interface with the provisioning system and nothing else. It is not connected to any external network in a way that generates data outside the building’s systems. It does not listen. It does not watch. It has a screen and a simple input interface through which the resident can:

Adjust their food parameters for the next day — not choose the specific meal, but flag preferences or restrictions that the provisioning system should weight differently. If the resident is vegetarian this week for whatever reason, they note it. If they are having a guest for dinner and would like the food interface to provision for two, they note it.

Adjust their cleaning schedule — the default is daily, during the specified window, but the resident can push it to every other day, can request a specific time, can flag that they would prefer to handle a particular area themselves and have cleaning supplies left at the interface for that purpose.

Flag clothing preferences — the default is provisioned selection, but the resident can note that tomorrow is an important meeting, or that they are attending a social event, or that they have been cold this week and would like warmer options weighted in the selection.

Request a conversation with the wellness coordinator — a direct and uncomplicated option on the device’s main screen, because the design principle is that asking for help should be frictionless.

The device does not have social media. It does not have entertainment streaming. It is not a phone. It is a provisioning interface, and its simplicity is intentional — the research showed that the residents most likely to experience the enrolled life as surveilled rather than cared for were the ones whose interface with the system most resembled the interfaces of commercial surveillance capitalism, and the design response was to make the device as specific and as limited as possible.

The Deterioration Protocol

This is the sharpest edge of the day-to-day system, and it deserves careful description because it is where the Arbiter’s care most obviously shades into control.

The passive monitoring signals — unconsumed food, uncollected clothing, unrequested cleaning, absence from communal spaces over an extended period — are not individually alarming. Any single one might reflect a busy week, a preference shift, a temporary bout of introversion. The pattern matters, and the pattern is assessed over time by the provisioning system’s calibration algorithms and by the wellness coordinator’s direct observation.

The first signal is always human and always relational. The wellness coordinator knocks on the door. Has a conversation. This conversation is not a wellness check in the clinical sense — it is not scripted, it is not documented in a formal record, it is not an assessment. It is a neighbor checking on a neighbor. Its power is exactly that.

If the pattern persists through several such conversations — if the resident is declining to engage, declining to eat, declining to maintain the basic personal care that the building’s provisioning is designed to support — the wellness coordinator escalates to the building’s health liaison, who is a clinically trained professional. The health liaison’s involvement is disclosed in the enrollment agreement, and its trigger conditions are specified. The resident cannot be surprised by this escalation. They agreed to it.

What the escalation does is not punishment. It is additional support, structured around what the resident’s assessment indicates they need. It might mean a temporary adjustment to the provisioning system — simpler food, more frequent wellness coordinator contact, a gentle restructuring of the daily environment toward what the assessment indicates supports this person’s functioning. It might mean a referral to a mental health professional whose occupational assignment is enrolled individuals experiencing difficulty.

What it cannot do is ignore the pattern. This is the hardest thing about the Arbiter’s daily care system, and it is worth being honest about: the system cannot let someone deteriorate in isolation without responding, because the enrollment agreement is a promise — from the Arbiter to the enrolled individual — that their wellbeing will be actively supported, and a promise that is only kept when times are easy is not a promise at all.

The enrolled individual agreed to this. They agreed, in the Personal Autonomy and Daily Life Agreement, that there was a floor below which the Arbiter would not allow them to fall without intervening. The floor is not comfort. It is not happiness. It is something more basic: the minimum conditions of a functioning human life — nutrition, cleanliness, social contact at whatever level the person’s profile indicates is their baseline need — that the Arbiter has committed to ensure are present.

The person who argues that their isolation is their choice is correct, and the Arbiter’s response is to honor that choice up to the point where the choice is clearly being made by a version of the person that is not the person the assessment knew. The Arbiter is not trying to make everyone happy all the time. It is trying to ensure that the enrolled individual it assessed — the specific person, with their specific needs and capacities — continues to exist in conditions that support who they are. When the conditions collapse, the Arbiter does something about it, because that is what it promised to do.

What This Feels Like

The day-to-day of the Type Four building is, from the inside, not remarkable. This is the point. The enrolled resident wakes to a managed morning, dresses in appropriate clothing, eats appropriate food, leaves a clean unit, and goes to work. They return to a clean unit, eat dinner alone or with neighbors as their mood dictates, and sleep in a managed environment.

The remarkable thing is the absence. No decision about what to wear. No decision about what to eat. No anxiety about whether the apartment will get cleaned this week. No background awareness of the refrigerator that needs restocking, the dry cleaning that needs picking up, the Amazon order that needs returning. The ambient cognitive load that this infrastructure produces in an ordinary life is, in the enrolled resident’s life, simply gone.

What goes in its place is — what the resident makes of the space. For some residents, this space fills with work, and the work is better than it was before. For some, it fills with the communal dinner table and the conversations that happen there. For some, it fills with a creative practice that was previously squeezed out by the noise of managing a life. For some, it fills with a particular quality of solitude that is different from the solitude of an unmanaged life — quieter, less anxious, more genuinely restorative.

For some residents, the space is uncomfortable, at least at first. The absence of friction is itself disorienting when friction has been the texture of every day. These residents are the ones the wellness coordinator pays quiet attention to, because the disorientation of enrollment is a real phenomenon — documented in the system’s outcomes data, anticipated in the building’s design — and the period of adjustment is the period of highest risk for the kind of withdrawal that the system is designed to prevent.

Most of them come through it. Most of them arrive, after some months, at the specific quality of ease that the early adopters described and that became the system’s most persuasive advertisement. Not happiness, exactly. Not comfort, exactly. The closest word is settledness — the experience of a life that has stopped fighting itself, that has been arranged into alignment with who the person actually is, that runs now without the grinding friction of mismatch.

It is, by every measure available to the system, better than what came before.

Whether it is enough is a question the system cannot answer and does not ask.