View Categories

Nova Taught Knowledge: How Verified Learning Works

8 min read

TAUGHT KNOWLEDGE NOVA AI

Nova Remembers What Your Team Teaches It

Corrections become permanent, verified, org-wide knowledge — with the evidence behind every fact. Nobody ever has to teach Nova the same thing twice.

Verified Learning Evidence-Backed Self-Maintaining Org-Scoped
Nova AI - verified learning

Every team carries hard-won knowledge about its data that lives nowhere in the schema: that receipts table is dead — current data lives in shipments. “Closed” includes cancelled orders. That back-reference is only 10% populated, don’t trust it for joins. Traditionally you re-explain these things to every new analyst — and to every new AI conversation.

Taught Knowledge ends that. When someone corrects Nova or teaches it something durable about your data, Nova can keep it — permanently, for the whole organization. But unlike a chatbot “memory” that stores whatever it heard, Nova refuses to remember anything it can’t prove. This guide explains the whole system.

The Core Principle: Nothing Is Remembered Without Proof

Every learned fact passes through one of two verification doors before it takes effect. There is no third path — a model inference that merely “sounds right” is rejected by design.

Door 1: The SQL Probe

Schema facts — what a table is, what a column means, whether a table is deprecated — are verified by a small read-only query against your actual database, through your own Network Agent. The probe SQL and its result are stored as evidence, re-runnable forever.

Door 2: Human Confirmation

Business rules and metric definitions can’t be proven by a query — they activate only when a person confirms them. Explicitly (“yes, that’s right”), or behaviorally: Nova applies the pending rule in a query, it verifies, and you accept the results. You watched it work.

The proof is the authority, not the author. A fact taught by any team member goes through exactly the same verification as one taught by an admin. Nobody’s job title bypasses the evidence — and a wrong claim fails its probe no matter who makes it.

How a Fact Becomes Knowledge

Step 1
Teach
Correct Nova mid-conversation, or just tell it something durable about your data
Step 2
Stage
The fact is saved as Proposed immediately — inert, but never lost if the chat ends
Step 3
Verify
A SQL probe tests the claim against real data, or a human confirms the rule
Step 4
Activate
The fact starts shaping Nova’s answers for everyone in your organization
Step 5
Self-Maintain
Usage is tracked, contradictions suspend, stale knowledge decays, probes re-run

Facts are deliberately compact — a few hundred characters each. If you teach Nova something with several independent parts (a definition, a join recipe, and a counting convention), it splits them into separate facts and verifies each one individually. Small, atomic facts are easier to verify, correct, and retire than paragraphs.

What Nova Can Learn

Fact typeExampleVerified by
Deprecated table“That receipts table is dead — use shipments”A range-coverage probe: the replacement must fully cover the old table’s data before it’s excluded. If the old table holds history the replacement doesn’t, it becomes a historical pointer instead — past data is never orphaned.
Table role“This is a view over the orders table”Catalog probe — the table exists and is queryable
Column meaning“Status codes 18/14/16/20 all mean open”The column exists and the claimed values actually appear in the data
Join reliability“That back-reference is only ~10% populated”The measurement is the fact — Nova runs the population query and stores the result
Business rule / metric“Closed means Invoiced or Cancelled”Human confirmation — explicit or behavioral

A Fact’s Life Cycle

Proposed

Staged, awaiting verification. Completely inert — zero influence on Nova until it passes. Unconfirmed proposals auto-retire after 30 days so nothing piles up.

Active

Verified and serving Nova now, org-wide. Every use is tracked; every success and contradiction is counted.

Disputed

Reality disagreed. The fact is suspended from Nova’s reasoning immediately and its original evidence probe re-runs. Pass → reinstated, flagged for review. Fail → retired.

Retired

Removed from every part of Nova’s reasoning — kept for the record with its full history and evidence.

A learned fact can never stay silently wrong. Two contradiction strikes and it suspends itself, pending re-verification against your live data. Reality always gets a vote.

Tiers: Learned Knowledge Makes Nova Cheaper, Not Heavier

Naive AI memory grows without bound and drowns the model in notes. Taught Knowledge inverts that — most learned facts reduce what Nova has to read:

Tier 0 — Exclusion

A verified deprecated table is removed from Nova’s working context, leaving a one-line pointer to its replacement. Learning that actually saves tokens.

Tier 1 — Description

Table and column facts replace Nova’s AI-generated guesses in place. Zero added cost — and a description hand-written by your team always outranks a learned one.

Tier 2 — Injected

Your most-used, best-corroborated business rules ride along in every conversation, under a strict size budget that can never blow up.

Tier 3 — On-Demand

Everything else is searchable the moment it’s relevant, at zero standing cost. Long-tail rules and procedures live here.

Corroboration guards the injected tier. New rules start at Tier 3. They earn a place in every conversation only through a second person confirming, or a track record of successful use. One person’s mistaken “yes” can never steer the whole organization.

The Taught Knowledge Tab

Everything Nova has learned lives under Nova → Schema Intelligence → Taught Knowledge (admins and creators):

Facts

Browse every fact with filters. Expand any row for its evidence — the exact probe SQL and result, or the confirmation — plus full version history.

Business Rules

Rules and metric definitions, split by injected vs on-demand, disputed flagged red, pending proposals showing confirmation progress.

Settings

Org-wide switches — learning on/off, member teaching, exclusions, rule capture — plus platform guardrails shown read-only for transparency.

Teaching Roster

Per-person “can teach Nova” toggles. Block a noisy teacher without turning learning off — blocked users still benefit from everything the org has taught.

Activity

A timeline of everything — who taught, revised, disputed, or retired what, and when.

Taught facts also surface where your eyes already are: the Schema Intelligence tree shows Taught badges on tables and columns with learned knowledge, deprecation chips on excluded tables (dimmed but always visible — never hidden), and a per-database knowledge summary.

Provenance: Every Fact Shows Its Work

Every fact permanently records who taught it (with their role and photo), when, in which conversation, and the evidence that verified it. Ask Nova directly — “who taught you that closed includes cancelled?” — and it answers with the real provenance. Admins can revise a fact (revisions re-enter verification — editing authority never bypasses proof) or retire it, from the UI or right in chat.

The source is always human. When Nova’s weekly maintenance merges two overlapping facts into one cleaner statement, the merged fact credits all the original human authors — Nova is the consolidation operation, never the source. The merged text must provably contain every claim from its sources, and the originals stay in the version history.

Self-Maintenance: Knowledge That Stays True

Usage telemetry

Every fact tracks how often it’s used, succeeds, and gets contradicted.

Contradiction handling

Two strikes and a fact suspends itself pending re-verification against live data.

Decay & promotion

Unused rules demote out of the injected set and archive; rules that keep proving useful earn promotion.

Exclusion self-repair

Every schema rescan re-checks excluded tables. Data reappears in a “dead” table? The exclusion suspends automatically. An exclusion can never outlive its proof.

Measurement refresh

Measured facts — like join reliability percentages — re-run on schedule as your data drifts.

Safety and Control

GuaranteeHow it’s enforced
Strictly org-scopedYour facts are yours. Nothing learned in your organization is ever visible to, or influenced by, any other organization.
Read-only verificationProbes run through your own Network Agent with the same read-only enforcement as every Query Streams query, under hard time and row limits.
Escape hatches everywhereAn excluded table is a routing preference, not a wall — it can always be queried explicitly, and SQL referencing it gets a gentle redirect notice, never an error.
GuardrailsPer-conversation proposal limits, per-organization fact ceilings, and compact per-fact size caps prevent runaway growth or prompt-injection abuse.
On by default, off in one switchWorks out of the box with nothing to configure. Turn any part off in Settings — nothing is deleted, and flipping back on restores everything instantly.

Frequently Asked Questions

Why didn’t Nova remember what I taught it?
Most likely the fact is still Proposed — check the Facts browser in Taught Knowledge. Business rules need a confirmation before they take effect: your “yes” in chat, or Nova successfully applying the rule in a query whose results you accept.
Can a wrong fact poison Nova for everyone?
The system layers against it: verification before activation, corroboration before org-wide injection, contradiction auto-suspension the moment reality disagrees, full provenance so you can trace and retire anything, and per-user teaching blocks in the Teaching Roster.
Does learning slow Nova down or cost more?
The opposite, by design. Most learned knowledge either removes content from Nova’s working context (deprecated tables) or replaces existing content in place (descriptions). Only your top business rules add anything, under a strict budget with automatic demotion.
Who can teach, and who can manage what’s been taught?
Everyone with Nova access can teach by default (it’s just talking to Nova) — every teaching passes the same verification regardless of role. Reviewing, revising, and retiring knowledge is for admins and creators, in the Taught Knowledge tab or directly in chat. Individual users can be blocked from teaching in the Teaching Roster without losing any benefits of the org’s knowledge.
What happens if we turn learning off?
Teaching stops instantly and learned knowledge stops shaping Nova’s context — but nothing is deleted. Every fact, its evidence, and its history stay intact, and flipping the switch back on restores service immediately.

Teach Nova Once. Benefit Forever.

Connect your data source, ask questions in plain English, and correct Nova like you’d correct a new analyst — it keeps what it verifies. Free to start, no credit card required.

Related guides: How Nova AI Learns Your Database Schema Automatically | Text to SQL with Nova AI | AI Powered Analytics

Updated on July 14, 2026

Powered by BetterDocs