Current behavior: Ownership is defined via the ownership property on a blueprint. It is optional, and even when configured as Direct or Inherited, the “Owning teams” field is not enforceable as required at entity creation time.

Requested change: Add the ability to configure the “Owning teams” (ownership) field as required per blueprint, so that when creating or registering an entity of that blueprint, the operation can be rejected if no owning team is set.

Why this is needed: To enforce clear ownership and accountability for every Service.