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.
For facilitators — running this as a guided session
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.
🤖 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 and paste its module list instead.)Run with Ana