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 AI coworker session starts by reading from it, and every captured discussion feeds back into it.

You can browse and edit it directly on your filesystem.

Access your Team Context

terminal

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

Prime-loaded files

These files are read by every AI coworker 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

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 see a catalog of available docs at session start and read full content on demand when the task is relevant.

Add optional frontmatter to help coworkers find the right doc:

---
title: API Design Guide
description: REST conventions, error formats, versioning rules
when: designing APIs, reviewing endpoints, error handling
---

`docs/governance/REDACT.md` — 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

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

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

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.

terminal

# Open in your editor

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 AI coworkers use it

When an AI coworker starts a session via ox agent prime:

Prime-loaded files (AGENTS.md, SOUL.md, TEAM.md, MEMORY.md) are read immediately
Doc catalog is scanned — titles and descriptions are loaded, full content is fetched on-demand
Discussion transcripts are available for reference when the task relates to a past conversation

The result: your AI coworker starts every session with your team's full institutional knowledge, not a blank slate.

What's next

SageOx + Claude Code — see how Team Context flows into coding sessions
Discussions — capture conversations that feed into Team Context
Web Recorder — record from your browser or phone

On this page