Co-living

Shared-facility residential: private bedrooms or micro-studios with shared kitchens, living areas, workspaces, and social spaces. Tenures run short to medium, and the density of residents per shared amenity is the highest of any residential type. In co-living, the standard's distinction between a dwelling and its amenities collapses — the shared kitchen is not a perk, it is where the resident cooks dinner.

That collapse is the type's defining behavioral fact: expectations that other buildings test weekly, co-living tests several times a day.

Domain activation

All six domains fully active, with expanded scope in Spaces and accelerated cadence in Lifecycle. Deliveries and Support behave as in any dense residential building; Environment adds the shared-kitchen and shared-bathroom systems to the monitored estate; Access carries more credentialed thresholds per resident than any comparable type — bedroom, kitchen, laundry, workspace, social floor.

Behavioral patterns acute in co-living

Shared spaces are essential infrastructure, not amenities. The readiness expectation (Spaces × Grace) and the published-condition baseline (Spaces × Harmony) are tested at the cadence of meals and laundry, not bookings. A gym closed for a day is a disappointment; a kitchen unusable for a day is a building that failed at housing. Turnover, cleaning rhythm, and condition reporting carry domestic weight here, and the standard's space expectations apply at that weight.

Onboarding at the speed of the tenure. With move-ins weekly or monthly, a three-business-day activation is not a delay — it is a meaningful fraction of the tenure spent without full access. Lifecycle × Harmony (one event activates every system) and Lifecycle × Reliability (day one, everything works) are the type's table stakes, and the deactivation half matters equally: in high-churn stock, orphaned credentials accumulate fast.

The densest propagation surface. A credential change that must reach bedroom, kitchen, laundry, workspace, and social floors simultaneously makes Access × Harmony the most mechanically demanding expectation in the building — and the first to expose a subsystem that processes changes on its own schedule.

Neighbor friction becomes support volume. Density converts noise, cleanliness, and shared-resource conflicts into a continuous stream of reports. The standard governs the building's side: every report received and progressed (Support × Reliability), severity-proportionate response (Support × Grace), recurrence visible rather than re-discovered (Support × Harmony). Whether the community thrives socially is outside the standard's scope — deliberately. The standard guarantees the booking works, the kitchen is ready, and the complaint is handled; it does not promise the dinner party succeeds.

Where co-living feels the standard first

Spaces at domestic cadence, Lifecycle at churn cadence, Access at propagation density. An examination starts in the shared kitchen at 8 AM — readiness, condition reporting, and what happened to the last report — and follows a move-in from signature to first dinner.