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

<p>The follow-on to <a href="https://github.com/TextQLLabs/ontology-workshop-guide" target="_blank"><b>Build Your Ontology, End to End</b></a>: you've built a governed semantic layer — this workshop is about <b>running it in production</b>. 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.</p>
<p>Hands-on format: short modules, copy-paste prompts, checkpoints. <b>\~2 hours</b>.</p>

<Warning>
  <b>Prerequisite: an ontology that exists.</b> 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 <a href="https://docs.textql.com/core/ontology/overview" target="_blank">docs.textql.com/core/ontology</a> — 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">
  <p><b>T-minus-1-day pre-flight:</b> 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. <b>Pacing:</b> 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. <b>Group sessions:</b> 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.</p>
</Accordion>