[Introduction](https://verity.md/docs) [Quickstart](https://verity.md/docs/quickstart) [Authentication](https://verity.md/docs/authentication) [How it works](https://verity.md/docs/how-it-works) [Moments](https://verity.md/docs/moments) [Formal verification](https://verity.md/docs/formal) [Findings & verdicts](https://verity.md/docs/findings) [The Standard](https://verity.md/docs/standard) [Memory](https://verity.md/docs/memory) [Org knowledge](https://verity.md/docs/org-knowledge) [Token telemetry & cost](https://verity.md/docs/cost) [The dashboard](https://verity.md/docs/dashboard) [CLI & commands](https://verity.md/docs/cli) [Files & configuration](https://verity.md/docs/files) [Security & privacy](https://verity.md/docs/security) [Troubleshooting](https://verity.md/docs/troubleshooting)

Concepts

# Org knowledge

Some of what one repository learns holds for every repository in its org. Org knowledge is that layer: claims lifted above a single repository, read by every review in the org and by your agents.

## Two scopes

|  | Repository knowledge | Org knowledge |
| --- | --- | --- |
| **What it is** | What one repository learned: its decisions, gotchas and patterns. | A claim that holds across the org, generalized from a repository's node. |
| **Where it lives** | `.verity/memory/` in the repository, and on the service. | On the service, linked to the repository nodes it came from. |
| **Who reads it** | Reviews and agents in that repository. | Reviews in every repository of the org, and any agent you connect. |

See [Memory](https://verity.md/docs/memory) for repository knowledge. The rest of this page is the org layer.

## What a claim carries

- **Its text**, written so it makes sense outside the repository it came from.
- **Why it's org knowledge**: several repositories learned it, or it is an org convention, or it is about a system every repository uses.
- **Where it came from**: the repositories that hold it, each with its own node.
- **Who disagrees**: repositories that said it doesn't apply to them, and why.

Prose only

Org text and every reason given about it are plain prose. The service refuses code, commands and markup in them, so nothing from your source ends up in the shared layer.

## Who sees what

Anyone with write access to a repository in the org reads its org knowledge. A claim from a repository you can't open still shows, because the claim is the org's, but that repository is only counted: “from 1 repository you can't open”. Its name, its nodes and its reasons are never shown to you.

## In reviews

When Verity reviews a change, it adds the org claims that bear on the goal and the files changed. A claim needs to share at least two meaningful words with the change, so a lone common word doesn't pull one in. A repository never gets back a claim it already holds, or one it disagrees with. The review report lists the org knowledge a review read, and each claim shows how many reviews used it in the last 90 days.

## Keeping it right

Open a claim on **All repositories › Knowledge**, or from a repository's Knowledge page. Every member can:

- **Say it doesn't apply here.** Your repository's reviews stop using it; every other repository still reads it. You can withdraw this later.
- **Demote it.** It leaves every review and agent in the org. A demoted claim can be restored.
- **Accept or dismiss a proposal.** Agents can propose a demotion; nothing changes until a member decides.

Every change needs a reason and is recorded: who, how, why and when. The org page shows the recent activity.

## For your agents, over MCP

Verity runs an MCP server for this knowledge, so an agent in any project, or none, can use it. Create a connection on **Account › Agents**. Each connection is its own login: it acts as you, sees only what you can open, and you revoke it there. The same page gives the command or file to paste for each popular agent, with your token filled in. In Claude Code, for example:

```
claude mcp add --transport http --scope user verity "<server address>" \
  --header "Authorization: Bearer <token>"
```

| Tool | What it does |
| --- | --- |
| `knowledge_for_task` | The org claims for a goal and its files, plus the repository's own knowledge. |
| `search_knowledge` | Search org and repository knowledge. Every result says which it is. |
| `get_org_claim`, `get_repo_node` | Read one claim or node in full. |
| `list_orgs` | The orgs you can read, and your repositories in each. |
| `mark_claim_not_applicable` | Say a claim doesn't apply to one repository, with a reason. |
| `propose_claim_demotion` | Propose that a claim is wrong for everyone. |

Read-only connections

Choose **Read only** when you create a connection to hide the last two tools. The server takes a token in a header; a connector that can only sign in with OAuth can't connect yet.

[Previous Memory](https://verity.md/docs/memory) [Next Token telemetry & cost](https://verity.md/docs/cost)

Source: https://verity.md/docs/org-knowledge