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

# Module 0 · The Context Stack

> Goal: understand the three context layers, how Ana composes them at question time, and the governance distinction that everything else in this workshop rests on. (~10 minutes)

**Goal:** understand the three context layers, how Ana composes them at question time, and the governance distinction that everything else in this workshop rests on.

## 0.1 · Three layers, one answer

When a user asks Ana a question, she composes context from three layers before answering:

<table><tr><th>Layer</th><th>Scope</th><th>Contains</th><th>Examples</th></tr><tr><td>**ORG context**</td><td>Everyone in the organization</td><td>The company dictionary: business rules, glossary, fiscal calendar, the context library's shared documents</td><td>"Revenue means recognized revenue, GL accounts 4000–4999" · "FY starts Feb 1"</td></tr><tr><td>**ROLE / behavioral context**</td><td>A team or persona</td><td>Scope + voice: which data surfaces this role may use, how to handle ambiguity, response style, hard limits</td><td>"Program managers see the care-management surfaces only, plain language, no SQL"</td></tr><tr><td>**PERSONAL context**</td><td>One individual</td><td>Preferences, personal vocabulary, saved workflows</td><td>"Concise answers, US/Eastern, 'my accounts' = accounts I own"</td></tr></table>

The layers compose: an analyst asking about revenue gets the org definition of revenue, through their role's analyst behavior, in their personally preferred level of detail. Context can additionally be scoped to **connectors** (loaded only when querying a specific source) — useful for source-specific quirks, and worth knowing, but the three people-layers are this workshop's subject.

## 0.2 · The governance distinction — learn it now, hear it repeated

The single most important operational fact about the stack:

<table><tr><th>Layer</th><th>How changes happen</th><th>Why</th></tr><tr><td>**Personal**</td><td>**Immediately** — your context, your call</td><td>It affects only you</td></tr><tr><td>**Org and Role**</td><td>**Proposed patches with review** — like a pull request for business logic</td><td>They change what *everyone* (or a whole team) is told; that power gets a gate</td></tr></table>

This is why the stack is safe: an individual can't redefine revenue for the company by saving a preference, and a team's behavior can't drift without a reviewable change trail. You'll feel this distinction in every module that follows.

## 0.3 · The routing table

For any "I want Ana to..." request, the layer is determined by **who should be affected**:

<table><tr><th>"I want Ana to..."</th><th>Layer</th><th>Why</th></tr><tr><td>...give me shorter answers</td><td>Personal</td><td>Your taste, nobody else's</td></tr><tr><td>...know that when I say "my book" I mean accounts where I'm the CSM</td><td>Personal</td><td>Your shorthand</td></tr><tr><td>...run my Monday prep when I ask</td><td>Personal</td><td>Your workflow</td></tr><tr><td>...use our fiscal calendar for everyone</td><td>Org</td><td>Company-wide truth</td></tr><tr><td>...define "active member" the official way</td><td>Org</td><td>Two people asking must get the same answer</td></tr><tr><td>...never show SQL to the operations team</td><td>Role</td><td>A team's response style</td></tr><tr><td>...keep \[clinical/care] data away from the program-management persona</td><td>Role</td><td>A persona's data scope</td></tr><tr><td>...decline off-scope requests politely and redirect</td><td>Role</td><td>A persona's hard limits</td></tr><tr><td>...know that the staging tables in \[warehouse] are unreliable</td><td>Org (or connector-scoped)</td><td>Everyone querying that source needs it</td></tr></table>

**The misrouting that matters most:** a team definition saved into personal context. It *works* — for that one person — and now the truth is forked: their answers silently disagree with everyone else's. Module 2 ends with the hygiene rule for exactly this.

**The layers generalize.** Roles and people are two axes of the same idea — *identity-based structure*. As you scale, the same pattern serves `teams/`, `customers/`, and `business-units/`: a folder per identity that **routes** its questions to the shared, governed definitions. One truth, many doors.

### ✅ Checkpoint

* [ ] You can name the three layers and what kind of knowledge belongs in each
* [ ] You can state the governance distinction in one sentence: personal is immediate, org/role is reviewed
* [ ] Given five "I want Ana to..." requests from your own org, you routed each to the right layer