promote-ontology-relationship

Promoting provider-specific edges to a canonical ontology edge standardizes cross-provider graph schemas. It applies to migrations where ontology labels exist on both endpoints, handling direct edges and those derived via binding nodes.

You enforce relationship constraints during a graph schema migration by registering a RelConstraint via a CI guard. This updates the ONTOLOGY_REL_CONSTRAINTS registry to validate collisions and enforce canonical edges across ontology-labeled nodes.

Yes, you can retain original provider edges while adding parallel canonical ontology edges. This approach ensures backward compatibility while enabling consistent graph queries across platforms during migration.

The best way to unify divergent relationship mappings across providers is to promote them to a single canonical ontology edge. This reduces divergence and aligns provider-specific relationships for consistent graph queries.

To handle graph migrations involving binding nodes and ontology labels, promote the provider-specific relationships to canonical edges. This requires ontology labels on both endpoints and supports edges derived via binding nodes with migration guardrails.

You need to update the CartographyRelSchema definitions to implement the promotion of provider-specific relationships to canonical edges. This ensures the schema changes are validated with tests for collisions and backward compatibility.