Inside the operating layer.
Eight layers. From the people who live in the building to the cloud infrastructure that runs it. This is how the operating layer is composed.
People and place.
Everything starts here. The people who live in and operate the building. The physical spaces they move through. The environmental conditions they experience. This layer is not designed — it is the reality the operating layer responds to.
Role in the system. Input layer. Every decision the operating layer makes references this layer — who is being served, what spaces they occupy, what conditions exist.
Apareé's role. Apareé does not control this layer. It reads it, serves it, and designs around it.
Building behavior.
This is where the building's behavior is defined. Not software yet — behavioral principles, expectations, rules, and categories that specify how the building should act across every domain a resident touches. This is the behavioral standard applied to a specific building.
Role in the system. Definition layer. Everything downstream performs to what is defined here. This is the output of the Behavioral Blueprint engagement.
Apareé's role. Apareé defines this layer. This is where Apareé becomes the author of the building's behavior.
Operational logic.
This is where behavioral principles become executable workflows. Every interaction the building handles — an access request, a maintenance issue, a delivery, a booking — is designed as a structured sequence: what triggers it, what decisions are made, what happens next, what the resident experiences, and what happens when something goes wrong.
Role in the system. Logic layer. Translates behavior into state machines, workflow sequences, rules, conditions, and fallback paths. This is the layer that differentiates Apareé from tenant portals — those assemble screens, this defines the logic of the building.
Apareé's role. Apareé designs this layer. Pure intellectual property — the codified logic of the building.
The experience surface.
This is what residents, staff, guests, and operators actually see and use. The resident app, the operations console, the guest portal, and the operating logic that runs behind all of them. This layer is the face of the building's behavior — but it does not define the behavior. It presents and executes what Layers 1 and 2 designed.
Role in the system. Interaction layer. The unified surface through which every person interacts with the building.
The unified surface every resident touches. One app, every interaction with the building.
Operations command surface. Routing, escalations, identities, devices, alerts — at one glance.
A short-lived, focused surface for visitors and service providers.
Apareé's role. This layer is 100% Apareé. Designed to the building's brand identity — the interface, tone, and interaction quality reflect the brand's intent, not Apareé's brand.
The engines.
The engines are the capability providers behind the experience surface. Some are built by Apareé. Others are external systems wrapped through Apareé integrations. The resident does not know or care which engine handles their booking or their access request — the experience surface is unified. Behind it, the engines do the actual work.
Role in the system. Capability layer. Provides the functional modules that Layer 3 draws on. This is the middleware that makes Apareé infrastructure rather than SaaS.
Apareé's role. Apareé builds its own engines AND wraps external ones. The wrapping layer normalizes external capabilities so Layer 3 sees a unified interface regardless of which vendor provides the underlying capability. This is co-owned: Apareé engines are owned by Apareé, external engines are integrated and normalized.
Physical systems.
The hardware in the building. Door controllers, sensors, HVAC machines, lockers, locks, intercom devices, parking gates, readers, elevators, EV chargers. Apareé does not own this hardware. It orchestrates it — the way an operating system orchestrates peripherals without owning them.
Role in the system. Hardware layer. Provides the physical capabilities that the engines and experience surface depend on. Hardware follows the logic defined in Layers 1 and 2, not the other way around.
Apareé's role. Apareé orchestrates this layer. It does not own the hardware. It connects to it through vendor APIs (via Layer 4 wrappers) and the edge gateway. The hardware follows logic defined above it.
Intelligence.
This is how the building learns. Every interaction the operating layer handles generates signals. The intelligence layer captures those signals, transforms them into metrics and insights, and feeds improvements back into the behavioral definition. The intelligence layer is where the building's experience compounds over time.
Role in the system. Learning layer. Converts operational reality into actionable knowledge. Identifies friction, inconsistency, and behavioral improvement opportunities. Updates the behavioral specification based on evidence.
Layer 6 → Layer 1: intelligence feeds back into the behavioral specification. This is the closed loop. The Intelligence layer exposes systemic gaps, friction patterns, and reliability trends that shape the next version of the standard.
Apareé's role. Apareé transforms signals into intelligence. This is Apareé's moat — the compound-intelligence corpus that grows with every building and every quarter of operation.
Cloud and ownership.
Where the system lives and who owns it. The operating layer runs on cloud infrastructure controlled by the building owner. Apareé defines the architecture and operates within it, but the infrastructure — hosting, data, identity, security — is owned by the building.
Role in the system. Infrastructure and governance layer. Provides hosting, security, compliance, data storage, and multi-building identity for the operating layer.
| What | Owned by |
|---|---|
| Cloud infrastructure | Building owner |
| Data | Building owner |
| Behavioral specification | Building (authored by Apareé) |
| Apareé engine code | Apareé (licensed to building) |
| Intelligence corpus | Building (processed by Apareé) |
| Edge gateway hardware | Building owner |
Apareé's role. The building owns the infrastructure. Apareé warrants the behavioral standard it commissioned, operating within scoped service accounts the owner can revoke. The system is owner-hosted, owner-controlled, with no lock-in to Apareé's cloud — the infrastructure belongs to the building.
How external systems connect.
Apareé wraps external systems through vendor-specific integrations. The wrapping layer normalizes capabilities so the experience surface sees a unified interface — regardless of which vendor sits behind it. New integrations are added as buildings are commissioned. The integration library grows with the portfolio.
The building owns the stack.
The operating layer runs on infrastructure controlled by the building owner. Apareé defines the architecture and operates within it, but the cloud, the data, and the identity belong to the building. The system is owner-hosted, owner-controlled, with no lock-in.
| What | Owned by |
|---|---|
| Cloud infrastructure | Building owner |
| Data | Building owner |
| Behavioral specification | Building (authored by Apareé) |
| Apareé engine code | Apareé (licensed to building) |
| Intelligence corpus | Building (processed by Apareé) |
| Edge gateway hardware | Building owner |
The building owns the infrastructure. Apareé warrants the behavioral standard it commissioned. The ownership model means the building is never locked in — and the warranty means the bureau stands behind the standard for as long as the agreement runs.
Frequently asked questions
From architecture to commissioning.
The architecture is what gets installed. Commissioning is how it gets there — building by building, domain by domain, with a behavioral warranty attached.