When the meta level of an object type is changed after roles involving that type already exist, those roles keep the classification they were given when they were created.

Roles that cross a meta level should be treated as classification links rather than as ordinary fact roles. If the meta level is raised afterwards, the existing roles are still treated as fact roles, and reopening the project does not correct them, because the stored classification is kept as-is.

The result is a model that looks right but behaves inconsistently: the same relationship is a classification in one place and a fact role in another, which affects diagrams, reports and generated output.

Changing the type of a type (for example from concept to object type) already triggers a reclassification of the roles involved; changing the meta level should do the same.