Company Context Map.
Updated 2026-06-07 · Agent-readable markdown available
The Ambience map of sources, memories, scopes, freshness, conflicts, and agent runs.
A company context map lets a team see what agents know, where it came from, who can use it, and what needs review.
- The map starts with sources agents already reach: calls, tickets, PRs, docs, threads, files, and sessions.
- It separates source artifacts from durable Ambience memories so teams do not save noise.
- It makes context health visible through freshness, conflict state, scope, and audit.
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.
The context map makes over-broad scopes easy to spot before a memory spreads into the wrong work.
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.
Freshness does not mean deleting history. It means making the current instruction clear enough that agents do not improvise.
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.
A team can ask why an agent acted a certain way and see the context packet that shaped the answer.