> ## 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 6 · Make It Smarter

> Remember the metric mismatch from Module 2? Make the right definition permanent. (~15 min)

## 6.1 · Fix a definition for everyone

Remember the metric mismatch from Module 2? Make the right definition permanent.

```text Prompt theme={null}
Our official definition of [metric] is: [definition — e.g., "active user = logged in AND took at least one action, excluding internal accounts"]. Save this to the ontology so it's used consistently from now on.
```

<Check>
  **You'll see:** a change proposal (patch) created for your org's context library — like a pull request for business logic. Once an admin approves, everyone's answers use your definition. *In most sessions no approver is present — that's normal. After approval lands (ask your admin), re-ask your Module 2 reconciliation question and watch it route through your definition.*
</Check>

<Note>
  **Governed by design** —

  You propose, an owner approves, every change is versioned and revertible. That's why teaching the platform is safe.
</Note>

## 6.2 · Teach it your vocabulary

```text Prompt theme={null}
Some vocabulary to remember: "NRR" means net revenue retention; "the big three" means our top 3 enterprise accounts: [names]; "EOQ crunch" means the last 2 weeks of a quarter. Save these to the ontology.
```

<Check>
  **You'll see:** a patch proposing the glossary additions. After approval, asking "how did the big three trend through EOQ crunch?" just works.
</Check>

## 6.3 · Set your personal preferences

```text Prompt theme={null}
Remember my preferences: I want concise answers with the headline number first; I work in [timezone]; when I say "my accounts" I mean accounts where I'm the owner; default time windows to the current quarter.
```

<Check>
  **You'll see:** your personal context file created/updated. Future threads pick it up automatically. (Personal vs. role vs. org context — and full role personas — get their own workshop: [**The Context Stack**](/workshops/context-stack/overview).)
</Check>

## 6.4 · Capture a recurring workflow

```text Prompt theme={null}
Save this as my "[name]" workflow: every month I (1) pull [metric] by segment, (2) compare to the plan numbers, (3) flag segments more than 10% off plan, (4) format as an email draft to [audience]. Next time I say "run my [name] workflow," do all of it.
```

<Check>
  **You'll see:** the workflow documented in your context. One sentence now replaces a 30-minute ritual.
</Check>

## 6.5 · Know the escalation path

<table>
  <tr><th>You want to…</th><th>Path</th></tr>
  <tr><td>Fix a metric definition</td><td>Propose a patch (6.1) — admin approves</td></tr>
  <tr><td>Add vocabulary / context docs</td><td>Propose a patch (6.2)</td></tr>
  <tr><td>Personal preferences and workflows</td><td>Your own context — immediate</td></tr>
  <tr><td>New data source connected</td><td>Ask your admin (Connectors page)</td></tr>
  <tr><td>New governed metric surface</td><td>Data team — see the [ontology workshop](https://github.com/TextQLLabs/ontology-workshop-guide)</td></tr>
</table>

<Note>
  **Save it findable** —

  When you save a definition or preference, give it the words people actually use — the metric's name *and its synonyms* ("NRR", "net revenue retention", "retention rate"). Future threads find saved knowledge by search, so the phrasing you save it under is the phrasing that gets it found — save it findable.
</Note>

### ✅ Checkpoint

* [ ] You proposed at least one definition or vocabulary patch
* [ ] You set personal preferences
* [ ] You know org-level (reviewed) vs personal (immediate) context
* [ ] You know where self-service ends and the data team's ontology work begins