# Team Context (/docs/features/team-context)
Team Context [#team-context]
Team Context is a git repo that holds your team's shared knowledge: conventions, decisions, domain terminology, and distilled insights from discussions. Every captured discussion feeds back into it, and coworkers read it back from assistant-mode, code-mode, and the web.
You can browse and edit it directly on your filesystem.
Access your Team Context [#access-your-team-context]
cd my-project/.sageox/teams/primary
ls
AGENTS.md MEMORY.md SOUL.md TEAM.md discussions/ docs/ memory/
This is a real git repo. You can open it in your editor, commit changes, and push — SageOx syncs it automatically.
What's inside [#whats-inside]
Prime-loaded files [#prime-loaded-files]
These files are the most direct part of Team Context in code-mode. When a repo-based AI coworker starts via `ox`, they are read at session start. Keep them concise — every token costs context window space across every session.
| File | Purpose | Budget |
| ----------- | ------------------------------------------------------ | ------------ |
| `AGENTS.md` | Team norms, repo layout, conventions, coding standards | \< 200 lines |
| `SOUL.md` | Team identity — purpose, values, decision principles | \< 100 lines |
| `TEAM.md` | Team roster, roles, working patterns, current focus | \< 100 lines |
| `MEMORY.md` | Auto-generated index of distilled team wisdom | \< 200 lines |
Prime-loaded files are auto-loaded into context. Bloat here directly degrades AI coworker performance. Prefer links and pointers over inline content.
docs/ — Team documents [#docs--team-documents]
Add markdown files for anything your AI coworkers should know: architecture guides, API conventions, domain knowledge, engineering principles. Each file covers one topic.
| Example doc | What it covers |
| ---------------------------- | ----------------------------------------------- |
| `docs/architecture.md` | How your systems fit together |
| `docs/glossary.md` | Domain-specific terms and definitions |
| `docs/coding-conventions.md` | Style guides, naming rules, structural patterns |
| `docs/api-conventions.md` | REST conventions, error formats, versioning |
Files are indexed automatically. AI coworkers in code-mode see a catalog of available docs at session start and read full content on demand when the task is relevant. In assistant-mode, SageOx can still search and retrieve the same underlying knowledge through MCP.
Add optional frontmatter to help coworkers find the right doc:
```yaml
---
title: API Design Guide
description: REST conventions, error formats, versioning rules
when: designing APIs, reviewing endpoints, error handling
---
```
docs/governance/REDACT.md — Redaction rules [#docsgovernanceredactmd--redaction-rules]
SageOx applies built-in redaction before storing observations. This file lets your team add domain-specific overrides — additional terms, patterns, or categories to redact.
memory/ — Layered memory [#memory--layered-memory]
Team memory is organized in time-based layers, built automatically from recorded discussions and observations.
| Location | Contains | When to read |
| ----------------- | ------------------------------------------- | ----------------- |
| `memory/daily/` | Recent observations and daily distillations | Recent context |
| `memory/weekly/` | Weekly pattern summaries | Broader trends |
| `memory/monthly/` | Monthly themes and strategic direction | Long-term context |
You don't need to write memory files by hand — the distillation pipeline generates them from captured discussions.
discussions/ — Recorded conversations [#discussions--recorded-conversations]
Transcripts and artifacts from captured discussions land here. Each discussion gets its own directory with the transcript, summary, and extracted insights.
Edit your Team Context [#edit-your-team-context]
Open the files in your editor and make changes. The most impactful edits:
**`AGENTS.md`** — This is the file AI coworkers read first. Add your team's coding conventions, architectural decisions, and domain rules here.
Open in your editor
code my-project/.sageox/teams/primary/AGENTS.md
**`SOUL.md`** — Define your team's values and decision principles. When an AI coworker faces an ambiguous choice, this is what guides the decision.
**`docs/glossary.md`** — Add domain-specific terms. If "parcel" means a geographic land unit in your domain (not a shipping package), define it here so AI coworkers don't guess wrong.
How coworkers use it [#how-coworkers-use-it]
In code-mode [#in-code-mode]
When an AI coworker starts a repo-based session via `ox agent prime`:
1. **Prime-loaded files** (`AGENTS.md`, `SOUL.md`, `TEAM.md`, `MEMORY.md`) are read immediately
2. **Doc catalog** is scanned — titles and descriptions are loaded, full content is fetched on-demand
3. **Discussion transcripts** are available for reference when the task relates to a past conversation
The result: your AI coworker starts the coding session with your team's institutional knowledge, not a blank slate.
In assistant-mode [#in-assistant-mode]
When a coworker uses SageOx through MCP, the assistant can search Team Context, read relevant documents, and cite prior discussions without needing a checked-out repo first.
In the web app [#in-the-web-app]
Humans can browse recordings, transcripts, summaries, and related artifacts directly when they want the original material rather than an assistant-mediated answer.
What's next [#whats-next]
* [SageOx + Claude Code](/docs/developers/claude-code) — see how Team Context flows into coding sessions
* [Discussions](/docs/context-capture/discussions) — capture conversations that feed into Team Context
* [Console Recorder](/docs/context-capture/console) — record from your browser or phone