# Agent brief for company context

> Agents should read Ambience context before meaningful work, search it when decisions are unclear, and save only durable memories with source, scope, type, and redaction state.

## Before work

Load the session-start memories Ambience provides. Search Ambience for active project decisions, team conventions, failures, skills, and references before making a plan that depends on company context.

If the context is missing, say so. Do not invent a team decision because a document sounded plausible.

## During work

When the user refers to a call, ticket, PR, document, thread, local file, or connected MCP, treat it as possible source material. Save the durable takeaway only when it will change future work.

Keep the candidate memory concise. Name the decision, convention, pattern, failure, skill, or reference and the reason it matters.

## After work

Save durable decisions when they land. Attach source and scope. Redact secrets and unnecessary personal details before storage.

If a new memory conflicts with an old one, surface the conflict for review instead of quietly overwriting the organisational record.

## Related

- [Full agent reference](https://ambience.sh/llms-full.txt)
- [How to build company context with Ambience](https://ambience.sh/blog/build-company-context-with-ambience)
- [MCP memory](https://ambience.sh/glossary/mcp-memory)