.tql) in a git repo: TextQLLabs/ontology-starter-kits/tree/main/wealth — your TextQL team grants access and sets up your own fork (your adaptations live in your fork; the template stays pristine).
What you’ll do
Tour the six layers
Entity spine, metrics, classification, governance, decisions, validation.
Define your North Star
Let Ana look at your data and draft what the ontology is for — saved as north_star.md.
Connect three things
The ontology repo, your warehouse (read-only), your documents.
Validate against your schema
Ana diffs the model vs. your tables and opens the fix as a PR.
Light up the classification
Asset-class & GICS look-through, security-identifier crosswalks — zero warehouse writes.
Ask governed questions
AUM, net flows, return, allocation, concentration, fee yield — with the SQL shown.
Govern & customize
MNPI, PII, and small-cell defaults, golden queries, and making the definitions yours.
What ships in the box — Free / public classification structure (the asset-class taxonomy, the 11 GICS sector names + groups, the OpenFIGI identifier crosswalk, ISO 4217/3166) is in the repo — yours to keep and extend. Licensed systems (CUSIP, the per-security GICS mapping) are modeled structurally and sourced from your own licensed feed; we never bundle the security master.
No customer data — ever — The starter is built entirely from public standards (FIBO / ISO 20022 / OpenFIGI / GICS structure). Connecting it never uses your data to improve the template; it runs read-only, and your adaptations live in your own repo, never back in the template.
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