Facility management & maintenance
Every building has a thousand quirks. Make the building remember them.
The fire door that sticks in humid weather. The valve that needs a quarter turn past the stop. The crack that has looked like that for years. Today this knowledge lives in the head of one caretaker — and leaves when they do.
Kin gives the building its own memory. Robots, sensors and staff all read from it and write to it. The knowledge belongs to the building owner — not to a contractor, not to a robot manufacturer, and not to one irreplaceable person.
Last updated: July 2026
How this looks in practice
Five kinds of knowledge no manual contains
These are scenarios — how it looks when a building keeps its own knowledge instead of borrowing it from whoever happens to be on shift.
The door that sticks
Without Kin
The fire door on the third floor sticks in humid weather. You push low, not at the handle. The caretaker knows this. Nobody else does — not the weekend crew, not the inspection robot, not the new hire who files a repair ticket every August.
With Kin
The building's Kin knows. Every robot that patrols that corridor knows. Every new hire inherits it on day one, the same way they inherit the keys.
The valve with a quarter turn
Without Kin
Heating valve B12 needs a quarter turn past the stop, or the far wing stays cold. It has worked this way for fifteen years. It is documented nowhere. Every new contractor rediscovers it the hard way, in winter, with tenants complaining.
With Kin
Captured once, kept forever. A maintenance robot sent to B12 knows the quarter-turn rule before it touches the valve. So does the contractor who takes over next year.
Inspection judgment
Without Kin
This crack in the parking deck has looked like this for years — stable. That one is new — escalate. Generic inspection AI has no history with your building, so it flags both, or neither. Either way, a human has to re-check everything.
With Kin
The building's Kin holds the history: what this crack looked like last year, and the year before. The inspection robot compares against the building's own baseline — and escalates only what actually changed.
The caretaker retires
Without Kin
Twenty-five years of building knowledge walks out the door on a Friday afternoon. The handover document is four pages. The knowledge was four thousand details.
With Kin
The handover happened gradually, over years of normal work — every quirk told to the building's Kin as it came up. By the farewell party, the handover is already complete.
Night rounds
Without Kin
The motion sensor by the loading dock false-alarms in wind. The corridor light on two flickers but is fine. A generic patrol robot escalates all of it — and after the tenth false call, nobody reads the alerts anymore.
With Kin
The patrol robot knows which sensors cry wolf, which flicker is harmless, and what actually needs a human at 3 a.m. Alerts get rare — and get read.
The model
The building is the unit of knowledge
One Kin per building. Robots, sensors and staff all read from it and write to it. A cleaning robot notes the leak stain that was not there yesterday; the inspection drone checks it against the deck's crack history; the caretaker adds context no sensor has. The knowledge compounds.
Most robot AI is trained on synthetic data — the average of every building. Kin is the opposite: field-learned knowledge about this specific building, at the detail level of the person who knows it best. And because the Kin belongs to the owner, changing service contractors no longer means losing the building's memory. The contractor changes; the knowledge stays.
How field-learned knowledge works under the hood: our primer on physical AI.
Questions
Frequently asked
Who owns the building Kin — the owner or the service company?
The building owner. That is the point. When you change service contractors, the knowledge stays with the building. The new contractor inherits fifteen years of quirks on day one instead of rediscovering them.
Does it work with our existing BMS?
Yes — they answer different questions. The BMS holds setpoints, schedules and sensor readings. Kin holds the knowledge around them: which sensor false-alarms in wind, which valve needs a quarter turn past the stop, which alarm actually needs a human.
Which robots does this apply to?
Any machine working in the building: cleaning robots, inspection robots and drones, security patrols, and — as they arrive — humanoid maintenance robots. Kin is the shared memory they all use, regardless of manufacturer.
How is staff knowledge captured?
Conversationally, during normal work. A caretaker tells the building Kin what they know the way they would tell a new colleague. No forms, no documentation project — the knowledge is captured as it comes up.
Your buildings already know things. Start keeping it.
One building or a whole portfolio — the knowledge should belong to the owner.