Skip to main content

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

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

​
What you’ll be able to do

Git-backed operations

Sync, contribution paths, review discipline, sync-failure drills.

Access control at scale

Folder-level restriction — invisible, verified, composed with RLS.

Accuracy testing

Golden datasets, pinned values, and a weekly drift alarm.

The improvement loop

Warnings + corrections → ranked backlog → small patches.

Scaling across teams

shared/ vs team folders, promotion, onboarding team N in days.

The runbook

Operations that survive vacations and departures.
Details follow current docs at docs.textql.com/core/ontology — the editor’s Files / Graph / Reviews / History tabs, GitHub sync, folder RBAC, and the .tql manual.

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.