Apareé Digital Architecture Guidelines

A behavioral standard for residential buildings.

1. The Thesis

Physical buildings are governed by codes and standards that have evolved over decades — structural, fire, mechanical, electrical. The behavioral experience of living in those buildings is governed by nothing.

A resident's relationship with their building is defined by dozens of daily interactions: entering, receiving deliveries, booking shared spaces, reporting issues, paying rent, understanding what the building is doing around them. Each of these interactions involves systems — access control, parcel management, booking engines, support workflows, payment portals, building automation. In most buildings, these systems were selected independently, configured by different vendors, and connected by hope.

The result: a marble lobby and a broken intercom. A designed gym with a booking system that double-books. A front door that sometimes recognizes your phone and sometimes does not. A maintenance request that disappears into silence. Five apps that do not talk to each other. A water shutoff that nobody mentioned.

Nobody designed how this building should behave.

The Apareé Digital Architecture Guidelines exist to close that gap. They define what residents have the right to expect — not from technology, but from the building itself. How it responds when you arrive. How it tells you when something breaks. How it handles your parcel, your guest, your complaint, your move-in day. How every system, every notification, and every silence comes together as one coherent experience.

What residents hold as expectations, the building holds as definition: a stated, durable description of its own conduct that survives staff turnover, operator transitions, and vendor changes.

The expectation is simple:

The building always responds.
When it can act, it acts. When it cannot act, it speaks.
Silence is the only failure.

These guidelines are for anyone who shapes how a building behaves: architects, developers, owners, operators, brand custodians, system integrators, and designers.

Every behavioral expectation in these guidelines was tested against one question:

Does this make someone want to live in a building that meets it — and uncomfortable living in one that does not?

If it does, it stays. If it does not, it is not a guideline. It is a wish.

A second filter follows the first: if an observer cannot determine whether the expectation is met, it is not an expectation. What survives both is the standard — behavior worth wanting, written so it can be tested.

ADAG is a voluntary standard, published openly. What a reference to it means is defined in Status of the Standard; what meeting it requires is defined in Conformance.

2. The Qualities

Every digital behavior in a building can be evaluated against six qualities. These are human constants — what people need from any system they depend on. They form a hierarchy: you cannot achieve the higher levels without first securing the lower ones.

Foundation

Reliability — Does it work?

First Try. Every Time.

You come home after a long day. You reach the front door. It opens. You do not think about it. That is reliability.

Usability

Clarity — Do I understand what is happening?

What, So What, Now What.

Your water was shut off for two hours. You knew a day in advance. You knew which hours. You knew it was back on before you checked. At no point were you confused, surprised, or left waiting for information that should have come to you.

Control — Can I act on it?

Earn the Interruption.

Your friend arrives while you are across town. You open the door from your phone. Done. No calls to the front desk. No explaining. You acted, and the building responded.

Emotional

Harmony — Do all parts agree?

One Truth, Everywhere.

You asked for a repair three days ago. You run into the building manager in the elevator. She says: "The part arrives Thursday — you will have it fixed by end of day." The same thing the app said. The same thing the technician told you. One story. No cracks.

Grace — Does it feel considered?

Design for the Fifth Time, Not the First.

You report a water leak. The response: "Got it — sending someone to 4B now. Expect them within the hour." Not a ticket number. Not a form confirmation. A name, a timeline, a human sentence.

Care — Does it anticipate and protect?

Know Only What You Need.

Two weeks after the flood repair, your phone buzzes: "Just checking — any signs of damp in 4B? If so, we will send the team back." Nobody asked for this. The building remembered.

The Hierarchy

Reliability is the foundation. Without it, Clarity is noise and Grace is theatre.

Clarity and Control are the usability layer. The resident understands what is happening and can act on it.

Harmony, Grace, and Care are the emotional layer. The building feels like one place, respects your time, and thinks ahead.

A building cannot skip levels. Invest in this order.

Each quality is defined in depth — its principle, and how it manifests across every domain — in Qualities.

3. The Domains

The qualities define how you judge building behavior. The domains define where you look.

A resident's relationship with their building happens through six recurring activities. These are anthropological constants — they will not change in fifty years. People will always enter buildings. People will always receive things. People will always share spaces. People will always need help. People will always go through transitions. People will always live inside a physical environment.

The domains

Access is the experience of coming home. You enter and leave your building more than any other interaction — hundreds of times a month. You bring guests. You expect the parking gate to open. You need your credentials to work at 2 AM the same way they work at 2 PM. When access fails, you are locked out of your own life. Nothing the building does well afterward matters if you cannot get through the front door.

Deliveries is the experience of receiving something you are waiting for. A parcel, a grocery order, a document. It is a small moment with outsized emotional weight — because when something you ordered does not arrive, or arrives and nobody tells you, or sits in a mailroom for three days while you wonder where it is, the building has broken a promise it did not even know it made.

Spaces is the experience of sharing resources with your neighbors. The gym, the rooftop, the meeting room, the pool. Every shared space carries an implicit social contract: it is available when promised, it is fair, it is clean, and booking it does not require a negotiation. When shared spaces are poorly managed, they become a source of conflict. When they work, they become one of the reasons people stay.

Support is the experience of something going wrong and needing help. A leak. A broken appliance. A noise complaint. A billing error. This domain defines the building's character more than any other — because how you treat people when they have a problem reveals more than how you treat them when everything works. The gap between "request submitted" and "problem solved" is where trust is earned or destroyed.

Lifecycle is the experience of every transition. Moving in. Setting up payments. Signing documents. Registering a vehicle. Renewing a lease. Moving out. These moments are infrequent but high-stakes — they shape the resident's first impression and last memory. A chaotic move-in poisons the relationship before it starts. A graceful one earns goodwill that lasts years.

Environment is the experience of living inside a building that communicates its own physical state. The heating failed overnight — but nobody told you, and nobody knows. The elevator has been slow for a week — but there is no acknowledgment, no timeline, no sign that anyone noticed. Environment is the domain where the building proves it is paying attention to itself — and telling you what it finds. ADAG does not define how the building's physical systems should perform — that is the domain of building codes and engineering standards. ADAG defines how the building communicates about its physical state to the people living in it.

Domain activation

Not every domain applies equally to every building — a building without shared amenities has no expectations around shared spaces. The principle: the expectation does not change. The implementation does. How domains activate, narrow, and enter a building's declared scope is defined in Domains and Conformance.

4. The Behavioral Standard

Six domains multiplied by six qualities yields thirty-six behavioral expectations. Each one is specific, testable, and universal.

Every expectation page follows the same anatomy: the expectation itself — a single sentence with a single shall — then the Required and Recommended behaviors, concrete scenarios of the expectation met (In practice), named patterns of it breaking (Failure modes), and a Test whose steps produce binary outcomes. The full format and its language conventions are defined in the Methodology.

Every expectation is universal; how a building meets it depends on what the building has. Required defines the floor for any building. Recommended describes what deeper capability makes possible — more capability raises the ceiling, never changes the expectation. A building without smart lockers still delivers every parcel to the right person: Required describes how, Recommended describes what lockers add. When a building lacks even the basic capabilities to meet Required, the gap itself is the finding. How capability and scope enter a claim is defined in Conformance.

The behavioral expectations are published as individual pages. Each domain opens with a brief introduction, then presents its expectations — one per quality. Begin with the six domains, or read how behavior is judged in the six qualities.

5. Principles in Practice

The qualities define what good behavior looks like. The domains define where it happens. This section is about how to make it real.

Communication Discipline

A building communicates constantly — notifications, alerts, updates, signs, screens, emails, messages. Most buildings communicate badly. Too much noise. Too little information. Wrong channel. Wrong time. No closure.

In practice, communication discipline comes down to three questions every message must survive before it is sent:

Does this message need to exist? A building that sends a push notification every time a neighbor books the gym has confused activity with information. Most building events are not resident events. The test: if a resident saw this message and shrugged, it should not have been sent. The exception: anything that affects the resident's access, safety, money, or plans always gets communicated — the cost of over-informing on critical matters is always lower than the cost of silence.

Does this message respect how the resident will receive it? A maintenance update at 11 PM is not urgent — it is intrusive. A planned outage warning sent two hours before the outage is not a warning — it is an ambush. Timing is not when the operator sends. Timing is when the resident receives. And tone matters: a robotic "Ticket #4829 has been updated" arriving on the same device where the resident texts their family is a failure of register, not just of warmth.

Does this message close the loop? The most corrosive communication pattern in buildings is the open loop: something was reported, something was acknowledged, and then... nothing. The resident does not know if it was fixed. Does not know if someone is coming. Does not know if their message was read. Every communication that opens a loop — a request, a report, a question — must eventually close it. Explicitly. "This is done. Here is what we did." Not silence that the resident is supposed to interpret as resolution.

Error Behavior

Things break. The question is not whether — it is how the building responds when they do.

No silent failures. If something fails — a door, a delivery, a request, a payment — someone knows. Either the building tells the resident, or the building tells the staff, or both. The only unacceptable outcome is that a failure happens and nobody is aware. Silent failure is the single most corrosive pattern in building operations. It is the source of the most common resident complaint: "Nobody told me."

The resident is never the messenger. When a system fails, the building detects it and communicates. The resident should not be the one who discovers the elevator is broken by walking up to it. The resident should not be the one who informs the front desk that the app is down. The building monitors itself.

Escalation is automatic, not heroic. When an issue exceeds its expected resolution time, it escalates. Not because someone remembered. Not because the resident complained again. Because the system has rules for what happens when time runs out.

Failure has a tone. When something goes wrong, the building's response carries emotional weight. "We are aware of the issue and working on it" is better than silence — but not by much. "The hot water system in Tower A is being repaired. Engineer is on site. We expect it back by 3 PM and will confirm when it is restored" — that is a building that treats you like an adult. Error messages, outage notifications, and delay updates are not afterthoughts. They are some of the most important words the building will ever send.

Behavioral Choreography

A resident does not experience "systems." They experience moments. Coming home. Receiving a guest. Booking a space. Reporting a problem. Moving in.

Each moment involves multiple systems, multiple people, and sometimes multiple physical spaces — all of which must behave as one coordinated flow.

One action, one outcome. When a resident books a space, the booking system confirms, the access system grants entry, and the notification system sends a reminder. This is not three separate events. It is one flow. If any link breaks — the booking confirms but access is not granted — the moment fails, regardless of which system "worked."

Context travels with the issue. When a maintenance request is handed from front desk to technician to follow-up, the full history travels with it. The resident never repeats themselves. The technician arrives knowing the name, the unit, the history, and what was tried before.

Transitions trigger everything. Move-in activates all credentials, all access, all services simultaneously. Move-out deactivates everything. No partial states. No "parking should be active by Monday." One event, one coordinated response across every system.

Brand Through Behavior

A building's brand is not its logo, its app skin, or its color palette. It is how the building behaves.

A luxury building that sends robotic ticket confirmations — "Your request ID is SR-2024-0847" — has contradicted its brand regardless of how beautiful the lobby is. A mid-market building that responds to a leak report with "Got it — sending someone now, expect them within the hour" has expressed more brand care than any marketing brochure.

Tone is behavior. The words the building uses in notifications, confirmations, error messages, and updates are brand decisions. They should be written once, with intention, and applied consistently — not generated by default system templates.

Timing is behavior. How quickly the building acknowledges, how far in advance it warns, how long it waits before following up — these express whether the building respects the resident's time and emotional state.

Discretion is behavior. What the building chooses not to send is as important as what it sends. A building that notifies you every time your guest accesses the gym has failed at discretion. A building that quietly handles routine operations and speaks only when it matters has understood that silence can be a form of respect — and noise is always a form of carelessness.

6. Governing Behavior Over Time

Your building worked perfectly on the day it launched. Six months later, a notification that used to arrive in minutes now takes hours. A booking confirmation that used to include the access code no longer does. The front desk started using a group chat for maintenance requests because the system felt slow. Nobody changed the design. Nobody made a decision. It just drifted.

This is what behavioral drift feels like to a resident: the building gets slightly worse in ways that are hard to name. Nothing is dramatically broken. But the experience that once felt whole now has small gaps. Small delays. Small contradictions. The resident does not file a complaint. They just trust the building a little less each month.

Behavioral drift happens when someone disables a notification rule to solve a complaint and never re-enables it, when a new staff member uses WhatsApp instead of the support channel because it is easier, when a vendor update changes a default setting that nobody notices, when a workaround becomes permanent because nobody remembers the original design.

Drift is not a people problem. It is a governance problem. Physical buildings have maintenance schedules — inspections, servicing, preventive repairs. Digital behavior needs the same discipline. Not because people are careless, but because systems are complex and complexity degrades without attention.

Principles of behavioral governance

Changes are intentional. When a flow changes, a notification is modified, or an integration is reconfigured — that is a behavioral change. It should happen because someone decided it should, not because someone toggled a setting during a busy shift and forgot to toggle it back. The question is simple: can you explain why this change was made? If not, it was not intentional.

The guideline is the reference. When a question arises — "should we send this notification?" or "what happens when a booking is abandoned?" — the answer lives in the behavioral design, not in someone's memory. People leave. Memory fades. The documented behavior endures.

Review is a rhythm. Behavioral integrity requires regular, deliberate review. Which flows are working? Where has friction increased? What signals are emerging? What has changed since the last review? Without a rhythm, drift is invisible until residents feel it. Quarterly is the rhythm most operations sustain; the rhythm chosen matters less than the rhythm kept.

Governance is an assigned responsibility. Someone owns the building's behavioral integrity by name — the role that approves behavioral changes, runs the review rhythm, and holds the documented design. Without an owner, governance is a shared intention, and shared intentions drift.

7. Measurement

These guidelines define what good building behavior looks like. Whether a building meets them is a question the standard answers itself — met or not met, demonstrated through each expectation's Test and defined in Conformance.

How well a building performs, how consistently, and how its behavior moves over time is measurement. The Living Experience Index (LEI) is the scoring methodology that reads buildings against the standard; a building's scored result is its behavioral profile, and scored buildings are published on the Benchmark. Standard and measurement are separate by design — the full relationship is described in the Methodology.