> ## Documentation Index
> Fetch the complete documentation index at: https://docs.textql.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Module 7 · Validate Numbers & Make It Yours

> The starter ships a measured proof: validation/ab-test-vanilla-vs-ontology.md — seven questions asked in two threads against the same connector, one with the ontology repo conne… (~20 min)

## 6.1 · Run the A/B test — vanilla vs. ontology

The starter ships a measured proof: `validation/ab-test-vanilla-vs-ontology.md` — seven questions asked in two threads against the **same connector**, one with the ontology repo connected and one without, scored on **correct / consistent / traceable**. The governed answers are pre-filled from validated golden values.

```text Prompt theme={null}
Run the A/B test from validation/ab-test-vanilla-vs-ontology.md: I'll ask the seven questions in this thread (ontology connected). Answer each, cite the governed surface, and show the SQL — I'm scoring you on correct, consistent, and traceable.
```

<Check>
  **You'll see:** the coded, multi-definition, and risk questions land exactly on the governed values, while the control question ("how many members total?") shows it's not magic — it's governance where governance matters. The headline: *correct on the hard ones, consistent across phrasings, traceable every time.*
</Check>

## 6.2 · Run the golden queries

The starter's golden values are already **pinned and verified** against the demo dataset (see `validation/golden-queries.md` and the end-to-end script in `validation/run-golden-queries.md`). Against **your** warehouse, re-pin them to numbers you trust:

```text Prompt theme={null}
Run the golden queries from validation/ against my warehouse. For each, compare to a reference number I trust and flag any drift. Where we differ, explain whether it's data, definition, or time-window.
```

<Check>
  **You'll see:** accuracy checked, not asserted — and a triage of any mismatch into data vs. definition vs. window.
</Check>

## 6.3 · Customize a definition

Your organization inevitably defines something differently — a readmission exclusion, a line-of-business filter, a different risk-model year.

```text Prompt theme={null}
Our official definition of [metric] differs from the starter: [your definition]. Update the governed surface in our repo, record the decision and the rejected default in a notes file, and open a PR. Add a golden-query test pinning a known value.
```

<Check>
  **You'll see:** the change land as a reviewable PR **in your repo** — the template stays pristine upstream; your adaptations are yours.
</Check>

## 6.4 · Localize the vocabulary

`ontology/notes/glossary.md` holds the canonical claims terms — member, member-month, claim, encounter, charge vs allowed vs paid, denial — each with a **line-of-business variance column** flagging where commercial, Medicare, and Medicaid deployments diverge (retroactive Medicaid eligibility, MA encounter completeness, HHS-HCC/CDPS instead of CMS-HCC…).

```text Prompt theme={null}
Walk the glossary's LOB-variance column for our line of business ([commercial / Medicare / Medicaid]). For each term that differs at our org, propose the override in glossary.md — keep the term → definition → source pattern — and open it as one PR.
```

<Check>
  **You'll see:** the vocabulary localized in one reviewable pass — so "member month" and "allowed amount" mean *your* org's thing, everywhere, from now on.
</Check>

<Note>
  **Two habits as you make it yours** —

  **1 · Write for the search box.** As you extend the kit, keep a short README per folder and repeat the phrases your teams actually use (metric names, synonyms, team names) in the prose — future threads find context by *search*, not browsing.<br /><br />
  **2 · Let usage drive the roadmap.** Stand up a weekly gap-review playbook: mine repeated questions, manual SQL, and mid-thread corrections; have Ana draft small reviewable patches; a named owner approves. The kit is the seed — usage is what grows it. (See [Ontology Operations](/workshops/ontology-operations/overview) Module 4.)
</Note>

### ✅ Checkpoint

* [ ] Golden queries ran; any drift was triaged (data / definition / window)
* [ ] One definition is now yours — PR'd, noted, and pinned with a test