Teammately Docs
Docs menu

reference

Project Context

Maintain the Project Agent Brief that gives Teammately agents stable, project-wide understanding.

Project Context

Definition

Project Context is the Agent Setup surface that edits the Project Agent Brief. The brief gives Teammately agents stable project-wide understanding: what the specialist AI is for, which behavior matters, important constraints, terminology, and other context that should carry across coverage, contribution preparation, case construction, and improvement work.

The Project Agent Brief is different from the Project Memo in General settings. The memo is administrative project text and explicitly is not used as prompt or agent context. Put agent-relevant project understanding in Project Context.

Fields, states, or lifecycle rules

  • The brief is scoped to the project and reused across benchmark workspaces.
  • Editing the brief changes future agent context; it does not rewrite completed Contributions, Runs, or Improvement Session history.
  • The brief provides orientation and constraints, not governed correctness authority. Policies and rubrics remain in Correctness Governance.
  • Controlling source material belongs in Reference Materials. Summarize stable project intent in the brief and keep source-backed detail in the indexed material.
  • The brief should state product-specific meaning directly. Avoid copying transient benchmark goals, one expert's unconfirmed opinion, or a temporary candidate hypothesis into permanent project context.

Writing a useful brief

Describe the specialist AI's purpose, users, important domain vocabulary, expected interaction shape, and constraints that affect many workflows. Include explicit boundaries where agents might otherwise make unsafe assumptions. Name controlling authorities without duplicating entire manuals.

Review the brief when the product purpose, domain, input architecture, or correctness boundary changes materially. If only one benchmark needs a special objective, put it in that benchmark's setup or Contribution. If only one Improvement Session needs a constraint, put it in the Goal Contract.

Worked example

Example: project context boundary

The brief states that a procurement assistant supports internal buyers, must distinguish current agreements from expired ones, and should expose uncertainty rather than invent an exception. The current agreements themselves remain indexed Reference Materials. The exact evaluation target for expired-agreement cases belongs to the benchmark and Improvement Session, not the brief.

Source confidence

Code-backed: the active Agent Setup Project Context route renders the Project Agent Brief editor. The distinction from General settings is supported by the current project settings UI.

Related task pages

Quickstart / Learning ManualProduct quickstartConfigure one project foundation, one benchmark slice, one expert contribution, one evaluation, and one evidence-backed improvement.Reference / Agent SetupReference MaterialsConnect project knowledge, inspect indexing state, and verify the blocks available to Teammately agents.Task / Expert ContributionsRequest an Expert ContributionCreate a focused benchmark contribution with an accountable expert, clear objectives, selected cases, attachments, and appropriate task components.

Found something unclear?

Report outdated, unsupported, or confusing docs so we can fix the source page.

Report a docs issue

Continue learning

Related docs

Agent Setup Agent Setup Configure Project Context and Reference Materials so Teammately agents have reusable project understanding before contribution work. Agent Setup Reference Materials Connect project knowledge, inspect indexing state, and verify the blocks available to Teammately agents. Project Settings Project Input Schema Define the canonical input architecture, case-material fields, and accepted artifact formats for project cases.
AI context