FR: ownership metadata — route governance findings to a human (evaluate vs attr.properties first)

[dmealing]

Gap

No first-class ownership metadata. There is no way to answer "who owns this entity" from the model, which is what lets governance findings route to a human rather than to a build log.

Prior art (open source)

dbt — groups carry an owner, and models belong to groups; ownership and access are deliberately separate concerns (groups define responsibility, access modifiers define visibility). https://docs.getdbt.com/docs/mesh/govern/about-model-governance

Notes

• The attr.properties bag can hold an owner string today, which is the ADR-0023-sanctioned escape hatch and may be sufficient. The question is whether verify reporting against ownership justifies making it first-class.
• Run ADR-0037's decision procedure before adding vocabulary: if this is inert data that nothing dispatches on, the properties bag is the correct answer and no registry addition is warranted.
• Pairs naturally with producer-side access control, where a group is the natural unit of both ownership and visibility.