For Owners and Acquirers

A building's behavior is a property of the asset — not of the management contract. Credentials that work, records that survive migrations, parameters that are published and honored: these persist or decay independently of who operates the building, and they are examinable before you buy, refinance, or change operators. The standard gives that examination a protocol.

Examining a building

The standard's Tests are a behavioral due-diligence protocol: observable steps, binary outcomes, no relationship with Apareé required. Run in this order, they reveal structural health fastest:

• The Reliability row first. Access, Deliveries, Support, Lifecycle, Environment — reliability failures are systemic, and everything else is built on top of them.
• The migration questions. Each Reliability Test includes a platform-change probe: did records survive the last system migration? A building that lost its delivery records or payment history at the last vendor change will lose yours at the next one.
• Recurrence in Support. Pull the request history (Support × Harmony): the same fault resolved three times is a maintenance reality no marketing deck discloses.
• Data residue in Lifecycle. A previous occupant's name on the intercom (Lifecycle × Reliability) is a small failure that reveals how move-outs actually propagate.

Reading a scope statement

A conforming building publishes its scope statement: active domains, primary interface, and published parameters. At diligence, the scope statement is the honesty document. Red flags: parameters that exist in an operations manual but not where residents can read them (a commitment that is not published is not a commitment); a scope narrower than the building's capability suggests avoided expectations; no scope statement at all means behavior is improvised, whatever the brochure says.

At operator transition

A building run to the standard hands its next operator a defined inheritance: the scope statement, the published parameters, the records (delivery, support, booking, account), and the expectations the previous operator was held to. The transition tests continuity expectations directly — and an incoming operator who receives no such inheritance is not taking over a standard; they are starting one.

Putting it in instruments

Conformance obligations belong in the documents that govern the relationship — the management agreement above all. Model language, including examination rights, is in Specifying the Standard; what a conformance claim does and does not promise is in Status of the Standard.