Updated November 16, 2026. Genie Ontology is now generally available: the Databricks release notes list it on November 9, 2026 for AWS, Azure, and Google Cloud. Pages became generally available on November 11, and domains had already done so on October 8. The ontology also has its own documentation page now. It calls the two halves modeled knowledge and learned knowledge, and it says Genie might ask you to clarify a conflict it cannot resolve. We updated the status labels, the conflict stage, the list of gaps, and the sources to match. External knowledge sources are still in Beta.
Databricks defines the Genie Ontology the same way on all three clouds: “the unified context layer that gives AI agents a business-aware map of your organization.” Accurate, and almost useless if you are deciding whether it matters to your company. Here is the plain version.
When someone asks a question of your company data in ordinary English, the system has to work out what the words mean. Which table holds revenue. Whether “active user” counts a person once or once per device. Which of the four dashboards named “Sales” is the one people trust. The Genie Ontology is where those answers live. It is the difference between a system that can read your data and one that understands your business.
The part worth a leader’s attention is not the technology. Half of this layer is defined on purpose. The other half assembles itself, from whatever your teams have already built. Databricks calls the first half modeled knowledge and the second learned knowledge. Click through the figure below to see both halves and what happens when they disagree.
The half somebody has to decide
Databricks calls this modeled knowledge: context that you “define, govern, and certify” through Unity Catalog semantics. The ontology page gives four tools as examples. The two that carried preview labels when we first published are both generally available now.
The half that assembles itself
Databricks describes this as a map of snippets that Genie “automatically extracts and maintains” from your existing assets and usage. The documented sources are metric views, dashboards, SQL queries, and Genie Agents. Each piece is called a snippet, and the docs name three kinds.
What happens when two definitions disagree
Each snippet carries an authority score, and Genie weighs the competing sources at the moment the question is asked. The documentation names three inputs to the score.
Genie then ranks the most relevant snippets and resolves conflicts by assessing the authority of each source. The docs give certification, popularity, and author as example signals, and they state the precedence rule two ways. One section says modeled knowledge takes precedence when the two conflict. The conflicts section says modeled knowledge, certified assets, and curated Genie Agents “generally take precedence” over learned knowledge on the same topic. Because of that word, generally, we still read this as prioritization rather than a guaranteed override. And if Genie cannot resolve a conflict, the docs say “it might ask you for clarification.”
Permissions still decide what anyone sees
Snippets are gated by Unity Catalog permissions. Databricks states that Genie answers “using only the sources you are permitted to see.” For assets inside Databricks, the ontology changes how well a question is understood, not what anyone can reach. The docs note one exception: snippets created from external knowledge sources, the Beta feature, are available to all users in the account.
What this actually changes for a business
The honest summary is that the Genie Ontology moves an argument, rather than settling it. Companies have always disagreed about what a metric means. Until now that disagreement was survivable, because each team ran its own report and the numbers only collided in a meeting once a quarter.
Put a system in front of everyone that answers in plain English, and the collision happens every day, in public, in front of whoever asked. So the work is not technical. Someone has to decide what “revenue” means and write it down where the system can read it. That is a leadership task wearing a data-tooling costume.
Four things the documentation does not promise
We read the primary sources rather than the launch material, and the gaps are as informative as the features.
- General availability covers the core, not everything around it. The release notes list Genie Ontology as generally available on November 9, 2026, on AWS, Azure, and Google Cloud. External knowledge sources are still Beta. Ontology Manager, the interface for curating the ontology, is not in the docs: the November 11 Databricks blog post calls it “coming soon in Beta.” On Genie Search the sources disagree. The AWS and Azure release notes list it as generally available on November 9, and the Google Cloud notes do not list it at all. The November 11 press release says Genie Search, Ontology Manager, and the always-on Genie are “coming soon to preview and beta programs.” We go by the docs, and we name the source each time.
- You cannot edit an individual learned snippet. The docs now say so directly. They do describe how to see them: click Genie Ontology under a response to open the snippets it used, each with its source asset, author, domains, and lineage. There is still no documented way to approve, downrank, or delete one. You steer it indirectly, by updating the source asset, by restricting access to stale assets, or by defining the concept as modeled knowledge.
- There is no documented off switch. The ontology was turned on by default on August 6, 2026, while it was still in preview, and the page that documents it today describes no setting to turn it off. The documented controls are narrower. Unity Catalog permissions keep an asset’s snippets away from people who cannot see the asset, and an account admin can turn off the external knowledge sources preview.
- The accuracy numbers are the vendor’s own. The June launch post footnoted its benchmark as an internal test of 28 questions. The November 11 post adds a second benchmark, built with Turing, in which Genie passed 91% of task runs. Databricks published it, the rival agents are anonymized, and the post says the results reflect a deployment where that knowledge had already built up. We have not found an independent measurement of the ontology’s contribution. Treat the figures as a vendor claim, because that is what they are.
What we would do about it this quarter
Nothing here requires a project. It requires a decision and an owner.
- Pick the five metrics your leadership actually argues about. Revenue, active user, qualified lead, churn, and whatever your industry adds. These are the ones worth defining first.
- Give each one a written definition and a name. Pages and metric views exist for this, and Pages left Beta on November 11. The tool matters less than the fact that a person decided.
- Name an owner per definition. Not a committee. When the definition needs to change, someone has to be allowed to change it.
- Assume it is already running. The learned half has been building itself from your dashboards and queries since August. The question is not whether to start, it is whether anyone is watching what it concluded. You can check now: open the snippets under an answer and read what it learned.
Here is the uncomfortable version. The system is already forming a view of what your business terms mean, assembled from whatever your teams happened to build. If nobody writes the real definitions down, that learned view becomes the definition by default.
Where these facts come from
Every claim above traces to Databricks documentation or an official post. When we first published in August, the ontology had no documentation page of its own, only a section inside the “Chat in Genie One” page. It has one now, last updated November 9, 2026, and most of the facts above sit there. The definition and the conflict rules read the same on AWS, Azure, and Google Cloud. The links below go to the AWS version.
- Genie Ontology, last updated November 9, 2026, where the definition, the two kinds of knowledge, the snippet types, the authority score, and conflict resolution are all documented.
- The November 2026 release notes, for general availability of Genie Ontology (November 9) and Pages (November 11), and the Beta of external knowledge sources (November 5). Domains are in the October notes (October 8).
- Unity Catalog semantics, covering metric views, domains, Pages, wikis, and certification.
- The 2026 AI/BI and Genie One release notes, for the August 6 entry that turned the ontology on by default.
- The general-availability post of November 11, 2026, which is where OntoRank, the Turing benchmark, and the status of Ontology Manager appear, and the press release of the same day, for its availability statement.
- The June launch post, which is where the PageRank comparison and the 28-question benchmark appear.
One correction to our own earlier reporting, and then a correction to the correction. In our July newsletter we wrote that steward certification feeds into the Genie Ontology. In August we said the documentation did not support that as written. It does now: the ontology page lists certification among the modeled knowledge features, and names it as a signal Genie weighs when sources conflict.



