Ask your project anything. It already knows.

Oracle is the AI inside Hawzu. You ask a question about your project in plain English and it answers with the matching records, a chart, an answer drawn from your own documents, or — if you were not asking a question at all — the right form, open and ready.

No. You type the question the way you would say it. If it is ambiguous you get a short question back with one-click answers, and if your data cannot answer it you are told so rather than handed a plausible-looking table.

No record does. Oracle is shown what is queryable in your project — field names, the values they hold, your folder and label names — together with your question. It never receives a test case title, a defect description or a comment. Answers drawn from your Canon documents are the exception: there, the passages it cites are what it read.

Yes, and it can never be more permissive than the screen for the same records. Oracle reads its permissions from the same rules that guard each page, so if your role cannot open Defects it cannot ask about them — nor reach them through a condition that would have read them.

No. The query is built from your live project, so a field that does not exist cannot be expressed, and every value is checked against what your project actually uses. Names — people, folders, releases — are looked up rather than guessed, and an unknown one comes back as a refusal instead of an empty result.

Yes, from a fixed set of chart types and daily trends. Change the chart type or the time window afterwards and it redraws immediately, without using AI again. Saved dashboards, curated insights and the project health score are Observatory.

Test cases, requirements, tasks, defects, releases, test runs and executions, plus settings records such as labels, shared steps, parameters and custom fields — and the ways they connect, like coverage, execution history, defect links and flakiness. Your own custom fields, folders, labels, releases and team members work in questions too.

Oracle returns records, counts them, or counts them per group — “defects by severity”, “failures per requirement”. What it will not do is sum or average a column, which is Observatory's job: the mean of five releases' pass rates is not the pass rate across them. It groups by one category at a time, conditions combine with “and” rather than “or”, and results are capped at five hundred rows, a hundred by default. Charts come from a fixed set rather than being drawn freely. When a question falls outside any of these, it says so instead of returning something that looks close.

The full Oracle page is not: it answers one question at a time, and every answer stands on its own with its conditions printed above it. The floating assistant in the header does hold a short conversation, and hands anything that needs room — a chart, a form, a long table — to the page.