> ## 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 8 · Track B: The N+1 Document

> Then close the loop: re-ask your Module 1 baseline with the ontology attached. (~15 min)

## 8.1 · Add the next document

```text Prompt theme={null}
Here's one new document. Figure out where it fits in the existing ontology, make a targeted edit to the right metric/entity/notes — not a rebuild — and open a focused change describing exactly what changed and why. Don't touch unrelated files.
```

<Check>
  **You'll see:** the new document slot in via a small, reviewable change. The model evolves continuously; every change is diff-able and auditable.
</Check>

## 8.2 · Consume & maintain

```text Prompt theme={null}
Expose these metrics as a stable surface callable from BI or via API/MCP, and describe an agent that watches for new documents or schema changes and proposes an ontology update automatically.
```

<Check>
  **You'll see:** the ontology become a reusable, self-maintaining layer other tools can build on.
</Check>

Then close the loop: re-ask your **Module 1 baseline** with the ontology attached.

```text Prompt theme={null}
[Your Module 1 baseline question, exactly as you asked it cold.] Note which definition you used and show the SQL.
```

### ✅ Checkpoint

* [ ] Document N+1 produced a targeted edit, not a rebuild — and unrelated files were untouched
* [ ] You know how the metrics get consumed downstream (BI, API/MCP) and watched for staleness