The operating model — 8 of 8
Unified data layer
The shared foundation everything else sits on, so the six domains above are reasoning from the same facts rather than six competing versions of them.
One set of facts, not six
Most housing organisations already hold asset data in one system, resident data in another, HR in a third, and repairs in a fourth — each internally consistent, and none of them agreeing with each other at the edges. The unified data layer isn't a single new database replacing all of those; it's the discipline of making sure a resident record, an asset record, and a case record can all point at the same address without three different answers for who lives there.
Where it feeds the model
Every domain above this one — asset, resident, people, process, and boundary — is only as trustworthy as the data layer beneath it. When the Governance Hub asks a cross-domain question — did the person who approved this repair have the training the policy requires — the answer depends on people and process records agreeing about who that person was in the first place. Fragmented data doesn't just weaken one domain; it silently weakens the governance conclusions drawn from all of them at once.