+
+ Benoit's v0.5 introduced the GraphDBBackend abstraction. The v0.6 roadmap is to land Neo4j as the first non-Lakebase backend, originally targeted at August 2026. This PR delivers it ahead of schedule with a complete user-visible path: pick the engine in Settings, build, query.
+
+
+
+
C1 OntoBricks controls the graph
+
Single canonical source of truth = the OntoBricks build pipeline. Mirror modes, dual-writes, etc., were explicitly ruled out in the 2026-05-20 sync.
+
+
+
C2 The ontology controls writes
+
No raw Cypher entry point exposed to users. execute_query raises NotImplementedError — all writes go through validated R2RML.
+
+
+
C3 No raw data in the graph
+
Only ontology-shaped triples land in Neo4j. The synthetic UC fact table stays in Unity Catalog; Neo4j receives the resolved entities.
+
+
+
+ - Customer value — Customers already on Neo4j (Ryan's contacts, EU manufacturing) get an OntoBricks deployment without forcing Lakebase.
+ - Architectural credibility — Proves the
GraphDBBackend abstraction is real and ships with two backends, not one and a placeholder.
+
+
+
+