> ## 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.

# Ontology Operations

> The follow-on to Build Your Ontology, End to End: you’ve built a governed semantic layer — this workshop is about running it in production. Git sync and contribution workflows, …

The follow-on to [**Build Your Ontology, End to End**](https://github.com/TextQLLabs/ontology-workshop-guide): you've built a governed semantic layer — this workshop is about **running it in production**. Git sync and contribution workflows, folder-level access control, accuracy testing with golden datasets, the thread-driven improvement loop, and scaling one ontology across many teams.

Hands-on format: short modules, copy-paste prompts, checkpoints. **\~2 hours**.

<Warning>
  **Prerequisite: an ontology that exists.** Starting from zero? Run the build workshop first — this one assumes objects, metrics, and .tql surfaces are in place.
</Warning>

## What you'll be able to do

<CardGroup cols={2}>
  <Card title="Git-backed operations">Sync, contribution paths, review discipline, sync-failure drills.</Card>
  <Card title="Access control at scale">Folder-level restriction — invisible, verified, composed with RLS.</Card>
  <Card title="Accuracy testing">Golden datasets, pinned values, and a weekly drift alarm.</Card>
  <Card title="The improvement loop">Warnings + corrections → ranked backlog → small patches.</Card>
  <Card title="Scaling across teams">shared/ vs team folders, promotion, onboarding team N in days.</Card>
  <Card title="The runbook">Operations that survive vacations and departures.</Card>
</CardGroup>

<Note>
  Details follow current docs at [docs.textql.com/core/ontology](https://docs.textql.com/core/ontology/overview) — the editor's Files / Graph / Reviews / History tabs, GitHub sync, folder RBAC, and the .tql manual.
</Note>

<Accordion title="For facilitators — running this as a guided session">
  **T-minus-1-day pre-flight:** run the workshop's key prompts end-to-end in the session workspace — confirm logins, connectors, and the features this workshop touches are enabled for every attendee; have a fallback demo workspace ready in case a customer connector fails live. **Pacing:** when a long prompt is running (2–4 min), fire it first, then discuss the concept while Ana works — never watch a spinner in silence. If behind schedule, cut sections marked optional, never the checkpoints. **Group sessions:** attendees drive, you narrate; collect every miss or wrong answer in a shared doc — that list is the ontology backlog. With 10+ attendees on one warehouse, stagger the heavy prompts.
</Accordion>

<Note>
  **🤖 Prefer to have Ana run this workshop?** Open a thread with your data connected and paste the prompt below — Ana walks you through it on your own data, one step at a time. You run each prompt; she coaches. *(Air-gapped / VPC tenants where Ana can't reach the web: download [`ana-runner.md`](https://github.com/TextQLLabs/workshops/blob/main/ontology-operations/ana-runner.md) and paste its module list instead.)*
</Note>

```text Run with Ana theme={null}
Hey Ana — facilitate the "Ontology Operations" workshop with me on this workspace. It has steps I do in the console/CLI, so: first inspect the current state (connectors / roles / context / git, as relevant) and tell me where we're starting. Then go ONE step at a time — for analysis steps hand me the prompt to run; for console/setup steps tell me exactly what to do, then WAIT until I say "done" and re-check before moving on. If I leave and come back, re-inspect and resume. Start by telling me what you see.
```

[**▶ Open in Ana — prompt loaded**](https://app.textql.com/chat/new?prefill=Hey%20Ana%20%E2%80%94%20facilitate%20the%20%22Ontology%20Operations%22%20workshop%20with%20me%20on%20this%20workspace.%20It%20has%20steps%20I%20do%20in%20the%20console/CLI%2C%20so%3A%20first%20inspect%20the%20current%20state%20%28connectors%20/%20roles%20/%20context%20/%20git%2C%20as%20relevant%29%20and%20tell%20me%20where%20we%27re%20starting.%20Then%20go%20ONE%20step%20at%20a%20time%20%E2%80%94%20for%20analysis%20steps%20hand%20me%20the%20prompt%20to%20run%3B%20for%20console/setup%20steps%20tell%20me%20exactly%20what%20to%20do%2C%20then%20WAIT%20until%20I%20say%20%22done%22%20and%20re-check%20before%20moving%20on.%20If%20I%20leave%20and%20come%20back%2C%20re-inspect%20and%20resume.%20Start%20by%20telling%20me%20what%20you%20see.)

Ana gates on the setup steps and resumes if you step away. (Air-gapped / VPC tenants: download [ana-runner.md](https://github.com/TextQLLabs/workshops/blob/main/ontology-operations/ana-runner.md) and follow the steps.)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.