Ownership and stewardship
Why does ownership decay fastest, and what should it be derived from?
Ownership is asserted metadata about people, and people change roles faster than schemas change. With ordinary departures plus internal moves of perhaps 20–30% a year, an ownership field left alone for three years is more likely wrong than right.
It has the highest decay rate of anything here and, critically, no signal when it becomes false. The field still renders.
The fix is the same as everywhere else: derive it from a fact that is already load-bearing. Examples: who owns the code repository, which deploy identity runs the job, which service principal (a non-human account) writes the table. These are maintained because something breaks if they are wrong, so they stay true as a by-product.
A second structural point: ownership must resolve to a group, never to a person, because a person is a single point of failure with a guaranteed eventual failure. Use an indirection: the asset points to a team, and the team resolves to its members at query time. This is late binding again (as with asset IDs): a stable handle plus a deferred lookup.
Ownership decays faster than anything else you store. Derive it from something that already has to be right.