A new Entity "Consumer"

[ericallard-qc]

Hi @harshach and the team! Love your Open-Source model approach!
This question is related to : #24333
Did you encounter the needs to model the "Consumer" of a Data Product? (to keep usage lineage through OPX data "Demande")

Obj = consumer
Attr: { Type: Team, System }

{
"name": "Consumer",
"description": "A data mesh Consumer entity representing a person, team, or application that discovers, requests, and accesses data products.",
"category": "entity",
"nameSpace": "datamesh",
"fields": [
{
"name": "fullyQualifiedName",
"type": "string",
"doc": "Unique ID for the consumer"
},
{
"name": "description",
"type": ["null", "string"],
"default": null,
"doc": "Description of this consumer"
},
{
"name": "owner",
"type": ["null", "string"],
"default": null,
"doc": "Owning user/team"
},
{
"name": "type",
"type": "string",
"doc": "Type of consumer: team, user, service, data product"
},
{
"name": "domain",
"type": "string",
"doc": "Business domain (e.g., Sales, Finance)"
},
{
"name": "contactEmail",
"type": ["null", "string"],
"default": null,
"doc": "Contact email for consumer"
},
{
"name": "dataProductSubscriptions",
"type": {
"type": "array",
"items": "string"
},
"default": [],
"doc": "References to subscribed data products (by FQN or ID)"
},
{
"name": "dataContracts",
"type": {
"type": "array",
"items": "string"
},
"default": [],
"doc": "References to Data Contracts (by FQN or ID)"
},
{
"name": "accessStatus",
"type": {
"type": "enum",
"name": "AccessStatusEnum",
"symbols": ["requested", "approved", "denied", "revoked"]
},
"default": "requested",
"doc": "Status of consumer's access to each product"
},
{
"name": "usagePurpose",
"type": ["null", "string"],
"default": null,
"doc": "Intended use or legitimate interest"
},
{
"name": "consentDate",
"type": ["null", "string"],
"default": null,
"doc": "Date of access approval/consent"
},
{
"name": "tags",
"type": {
"type": "array",
"items": "string"
},
"default": [],
"doc": "Tags for classification/audit"
}
]
}