---
id: agent-setup.overview
title: Agent Setup
summary: Maintain the Project Agent Brief and Reference Materials used by Teammately agents across benchmark work.
kind: concept
product_area: agent_setup
status: stable
updated: 2026-11-06
canonical: /docs/agent-setup
---

# Agent Setup

Give agents the project understanding they need before they prepare coverage, expert work or candidate improvements. Keep the project's stable purpose separate from its source materials and governed standards.

## Definition

Project understanding has two parts: **Project Context**, which edits the Project Agent Brief, and **Reference Materials**, which connects source material and exposes Indexed Reference. Open these reusable project foundations through **Project Settings**.

The brief explains purpose, users, important terminology and constraints. Reference Materials supplies the documents and source content agents retrieve. A source refresh does not silently rewrite the brief.

## Decision checkpoint

| Need | Open | Scope |
| --- | --- | --- |
| Explain stable project purpose | Project Settings → Project Context | Project Agent Brief |
| Connect and inspect source material | Project Settings → Reference Materials | Project sources and indexed blocks |
| Edit guidance for configured Lemon activities | Project Settings → Lemon instructions | Project override or inherited guidance |
| Guide response alternatives | Assets → Comparison Directions | Reusable comparison guidance |
| Design expert presentation | Assets → Review Screens | A selectable review asset |
| Ask one specialist question | Expert Contributions | One Benchmark request |

## Keep context and authority distinct

A source document can inform an agent without becoming an approved Policy. The brief or Lemon instructions cannot supply expert approval. Comparison Directions can vary responses without deciding which response is correct.

Put a one-time objective in its Contribution or Lemon Goal. Put a stable project-wide expectation in the brief or the appropriate Lemon instruction. This keeps an earlier accepted request interpretable after settings change.

## Maintain project understanding

Review the brief when product purpose, terminology or domain boundaries change. Verify that controlling material is actually present in Indexed Reference after source processing. A connected account alone does not establish that its intended documents are retrievable.

Keep disagreements between sources visible. Use a scoped Expert Contribution when a qualified person must decide which rule controls, then maintain the accepted standard in Correctness Governance.

The Project Memo in General settings remains descriptive text for people. It is not injected as agent context.
## Related reference pages

{% related-card-grid title="Related reference pages" %}
- [Project Context](/docs/agent-setup/project-context)
- [Reference Materials](/docs/agent-setup/reference-materials)
- [Lemon Instructions](/docs/project-settings/lemon-instructions)
- [Comparison Directions](/docs/assets/comparison-directions)
- [Review Screens](/docs/assets/review-screens)
{% /related-card-grid %}
