# Company Context Map

> A company context map lets a team see what agents know, where it came from, who can use it, and what needs review.

## Sources

Sources are the work artifacts where context is born: a Granola call, Linear ticket, GitHub PR, Slack thread, Google Doc, Notion page, local repository, or agent session.

Ambience does not need every direct connector before it can help. If an approved agent can already read a source, Ambience can ask permission and propose source-linked memories from it.

## Memories

Memories are the selected takeaways future agents should reuse: decisions, conventions, patterns, skills, failures, and references.

The memory is smaller than the source and more accountable than a summary. It names the durable claim and links back to evidence.

## Scopes

Scopes decide who can use the memory. Personal, team, project, org, and sensitive scopes keep retrieval aligned with permissions instead of pure relevance.

## Freshness and conflicts

Context goes stale. Ambience treats conflicts as a product surface: review, keep both, accept a newer memory, or dismiss a false conflict with evidence.

## Agent runs

The map closes the loop by showing which agent runs read context, wrote memories, or changed access. This is what makes shared memory auditable.

## Related

- [Source-linked decision example](https://ambience.sh/examples/source-linked-decision)
- [Security and permissions](https://ambience.sh/company-context/security-and-permissions)
- [Context Readiness Score](https://ambience.sh/company-context/readiness-score)