A building that keeps its promises.

A requirement written at schematic design is a promise about a condition. Dark at the pillow. Quiet when the systems start. Fresh air at hour four with the door closed. Construction delivers that condition once, on the day it's tested. The building has to keep delivering it for years, through seasons, filter changes, new occupants, and equipment that ages. That's what the infrastructure is for.

Most building technology is bought as a set of features. A control system, a lighting system, shades, sensors, a network. Each one works. What they rarely do is hold a space to a stated condition over time, because nobody wrote the condition down and nothing was set up to check it.

We think of the infrastructure as three jobs.

Sense

A sensor is only useful if the project can say why it's there and what decision its data supports. A CO2 reading, a particle count, a light level at the eye, a sound level at the bed, a humidity trend, a leak sensor under a water heater: each one exists to answer a specific question about a specific requirement. Placed at the position that matters, under the conditions that matter, with a clear difference between a reading and a fault. A dashboard of numbers with no question behind them is decoration.

Sensing is also how the building tells you it has drifted. A filter that's loading shows up as a fan working harder and airflow falling. A shade that's failed shows up as light at the eye at nine at night. A mechanical transition that was quiet at commissioning and isn't anymore shows up in the overnight log. None of that needs a person to notice and complain first.

Act

Automatic control is the part that goes wrong most often, because it's usually written as a list of triggers. Motion, time, temperature. The space reacts, and the person in it gets surprised. The alternative is to write the sequence around the conditions the space is supposed to hold. The evening scene lowers light at the eye on a schedule the household set. Ventilation ramps ahead of a full dining table rather than after it. A heat pump's starts, stops, and speed changes are defined so the change heard at the bed stays inside the limit that was tested. When two systems conflict, more outside air against fan noise, filtration against airflow, daylight against glare, the priority was decided at design, not left to whichever device won.

And the person is always allowed to say otherwise. A keypad by the door, a switch by the bed, a control that does the obvious thing without a phone. The automation is there so the space works without attention. It isn't there to take the space away from the people in it.

Last

The last job is the one nobody budgets for. Conditions drift. Seasons change what the mechanical system has to do. Filters load, lamps age, firmware updates, a family grows, a hotel changes its room mix. A building that delivered its requirements at handover and was never checked again is a building running on hope.

So the infrastructure carries the requirement schedule forward. Each condition has a maintenance item, a retest interval, a fault behavior, and a name attached to correcting it. Seasonal items that couldn't be tested at handover stay open with a date. The overnight logs, the airflow checks, and the light readings are repeated, not once, but as part of how the building is cared for. When something falls outside its limit, it's corrected and tested again.

What that gives an owner

Not a smarter building in the sense of more screens. A building that was designed to a set of stated conditions, verified against them when it was built, and kept to them afterward. That's the difference between technology that was installed and infrastructure that does a job. The job is holding the space to what it was built for, for as long as people live in it.

That's what we mean by Building Intelligence.