> ## 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 3 · Org Context

> Goal: the shared dictionary — propose a definition, a glossary entry, and a context-library document through the review loop, and see why org context is how two people asking th… (~15 minutes)

**Goal:** the shared dictionary — propose a definition, a glossary entry, and a context-library document through the review loop, and see why org context is how two people asking the same question get the same answer.

## 3.1 · What lives at the org layer

Org context applies to **every user, every thread**: business rules ("revenue is recognized at shipment, not order"), the fiscal calendar, the glossary, data-quality knowledge ("\[table] is the source of truth, not \[other table]"), and the context library's shared documents (policies, metric docs, onboarding guides). It's the layer that makes answers *consistent* — the same question from two people routes through the same dictionary.

## 3.2 · Propose a definition patch

Pick a term your org actually argues about:

```text Prompt theme={null}
Propose an org context patch: our official definition of [active member] is [logged in AND completed at least one action in the trailing 30 days, excluding internal and test accounts]. Save it to the org context so every user gets this definition — and open it for review.
```

<Check>
  **You'll see:** a **patch created, not an immediate change** — the governance distinction from Module 0 in action. The patch shows the proposed diff; a reviewer (an admin or designated owner) approves or declines it. Until approval, nothing changes for anyone.
</Check>

## 3.3 · Propose a glossary addition

```text Prompt theme={null}
Propose a glossary patch with three entries: "[PMPM]" means per-member-per-month; "[panel]" means the set of members assigned to a care team; "[the morning report]" refers to the daily operations playbook output. Open for review.
```

<Check>
  **You'll see:** vocabulary becoming shared infrastructure. After approval, anyone can say "PMPM by panel" and be understood — including new hires on day one.
</Check>

## 3.4 · Contribute a document to the context library

Definitions are atoms; documents are molecules. Upload or point at a real document — a metrics policy, an SOP, a data dictionary:

```text Prompt theme={null}
Add this document to the org context library: [attach or name it]. Summarize what knowledge it contributes, propose where it should live in the library structure, and open the addition for review.
```

<Check>
  **You'll see:** the document staged with a placement proposal. The context library is browsable by your colleagues *and* readable by Ana — one artifact serving both audiences.
</Check>

## 3.5 · The review loop, from the reviewer's side

If you hold review rights, open the pending patches (the Reviews surface in the Ontology/context area) and apply the three-question bar from the [**Admin & Governance**](/workshops/admin-governance/overview) workshop: Correct? Conflicting with an existing definition? Scoped right (org-wide truth vs one team's shorthand)? Approve, or decline **with a reason** — declines without reasons teach proposers to stop proposing.

<Note>
  Reviewer notifications (patch submitted/approved/denied) are configurable under Settings → Notifications → Ontology — set them up now if you're a reviewer, or this loop silently stalls.
</Note>

<Note>
  **Write for the search box** —

  Future threads find org context by **searching**, not browsing. So: searchable headings and filenames, a short README in each folder saying what lives there and which files are canonical, and — deliberately — the phrases people will actually ask for repeated in the prose (metric names, synonyms, team and role names). Exact-match search is often a future agent's fastest retrieval path.
</Note>

### ✅ Checkpoint

* [ ] A definition patch, a glossary patch, and a document addition are proposed (not directly applied)
* [ ] You watched a patch go through review — approved or declined-with-reason
* [ ] You can explain why the same question from two users now returns the same definition
* [ ] Reviewers have notifications routed somewhere they actually look