It could well be a Sparx-specific stereotype applied to metaclasses - https://sparxsystems.com/enterprise_architect_user_guide/17.0/modeling_frameworks/metaconstraint.html