Glossary

Terms used across the Apareé Digital Architecture Guidelines. Organized alphabetically.


Allocation parameters. Published rules governing how bookable spaces are distributed: maximum bookings per unit, advance booking window, consecutive booking policy, and no-show policy. (Spaces)

Alternative method. A secondary means of performing an action — entry, retrieval, booking, reporting, lifecycle management — when the primary method is unavailable or unusable by the resident. Every domain requires at least one alternative method for its core actions. (All domains)

Buffer. The scheduled gap between consecutive bookings, during which the building resets the space to its published readiness standard for the next resident. (Spaces)

Chain of custody. The unbroken record of a delivery from the point of receipt through storage to retrieval or documented disposition. (Deliveries)

Credential. A digital or physical token — phone, card, fob, PIN, biometric — that grants a person entry to designated areas of the building. Credentials are activated at move-in and deactivated at move-out as coordinated events across all building systems. (Access, Lifecycle)

Cross-domain reference. An annotation within a domain expectation that identifies a behavioral dependency on another domain. Informative, not normative — it aids implementation by making coordination requirements visible. (All domains)

Disposition. The documented removal of an unclaimed delivery from the building's custody — return to carrier, transfer to management, or disposal after the published retention period. (Deliveries)

Domain. An area of daily life where building behavior is observed. There are six: Access, Deliveries, Spaces, Support, Lifecycle, and Environment. Domains define where behavior happens. (Framework)

Entry point. Any door, gate, elevator, or barrier controlled by the building's access system through which a person passes to reach their destination. (Access)

Expectation. A single sentence defining the behavioral requirement at the intersection of one domain and one quality. Each of the thirty-six expectations is specific, testable, and universal. (Framework)

Failure mode. A specific, named pattern of failure describing how the building breaks an expectation and how the resident experiences that failure. Failure modes are diagnostic — they identify the recognizable moment where trust breaks. (All domains)

Fallback communication method. A published alternative channel for reaching residents when the building's primary digital communication is unavailable — ensuring residents can be informed during connectivity outages. (Environment)

Grace period. The published window after a booking's start time during which the building waits for the resident to arrive before releasing the reservation to others. (Spaces)

Household member. A person associated with a resident's unit who holds their own credential and can independently access the building, retrieve deliveries, manage bookings, and perform lifecycle actions within the scope published by the building. (Access, Deliveries, Spaces, Lifecycle)

Invoice dispute. A mechanism through which a resident can flag a specific charge on an invoice. The flagged item enters the building's support system for financial reconciliation. (Lifecycle, Support)

Monitoring disclosure. The building's published list of which infrastructure systems it monitors and which it does not — enabling the resident to understand where digital detection exists and where the building relies on resident reports or manual inspection. (Environment)

Onboarding. The coordinated activation of all building systems associated with a resident's account — entry credentials, parking, mailbox, amenity access, payment portal, delivery management — on or before the resident's first day of occupancy. (Lifecycle)

Outage communication. Proactive notification to affected residents when a building infrastructure system fails — including what failed, the affected area, expected duration or next update time, and resolution when the failure is corrected. (Environment)

Override. A building-initiated change to a resident's environmental control — thermostat adjustment, climate limitation, lighting schedule change — for operational reasons such as energy management, system protection, or load balancing. Overrides require communication to the resident with reason, duration, and available adjustment. (Environment)

Post-move-out access. Read-only access to a resident's account record — payment history, documents, deposit status — that persists after building-access credentials are deactivated, for a published period sufficient to complete the departure process. (Lifecycle)

Primary interface. The building's designated digital channel — typically a single app or portal — through which residents manage access, deliveries, spaces, support, lifecycle actions, and view building status. (All domains)

Published standards. The building's stated commitments for common area conditions and building-managed systems — including comfort ranges, air quality thresholds, maintenance schedules, and data retention policies — accessible through the resident interface. (Environment, Lifecycle, Spaces)

Quality. A behavioral lens applied across all domains. There are six: Reliability, Clarity, Control, Harmony, Grace, and Care. Qualities form a hierarchy — each level depends on the one below it. (Framework)

Readiness standard. The building's published baseline condition for a bookable space — clean, lit, climate-appropriate, and equipped as described — guaranteed at the start of every booking. (Spaces)

Required. The minimum set of behaviors the building must demonstrate to meet a behavioral expectation. Required statements are testable requirements, not aspirations. (Framework)

Recommended. Behaviors that strengthen a behavioral expectation but are not mandatory. Recommended statements represent what becomes possible with deeper integration or greater capability. (Framework)

Resolution. The documented completion of a support request, describing what was done, when, and by whom. A resident can dispute a resolution to reopen the request. (Support)

Retention period. The building's published maximum duration for holding an unclaimed delivery before disposition. Residents are notified no fewer than 48 hours before it expires. (Deliveries)

Stale notice. An outage communication that has persisted for longer than 48 hours without an update. The standard requires all outage notices to be updated or removed within this window. (Environment)

State transition. A change in a support request's status — received, acknowledged, assigned, in progress, resolved — each of which triggers a notification to the resident. (Support)

Zone. A defined area of the building — floor, wing, amenity, or service area — subject to specific access authorization, notification scope, or service boundaries. Used for targeted disruption notifications in the Environment domain. (Access, Environment)