# Company Context Maturity Model

> Teams get leverage from agents when useful work becomes reusable context with source, scope, review, and reuse.

## The model

### Level 0: cold starts

Agents begin every session as if the company has no memory. Humans paste context, repeat decisions, and hope the agent notices what matters.

### Level 1: personal recall

One person has prompts, notes, local files, or private memory that helps their agent. The context is useful, but it does not travel safely to teammates.

### Level 2: project memory

Important decisions and conventions are attached to a project. Agents can retrieve current implementation constraints before they edit, plan, or respond.

### Level 3: source-linked team memory

Calls, tickets, PRs, docs, threads, and agent sessions become approved source material. The memory is the durable takeaway, not the whole artifact.

### Level 4: governed company context

Context is shared across the organisation with scopes, redaction, conflict review, access changes, and audit.

### Level 5: context operations

Teams run lightweight context ops: weekly reviews, source sweeps, stale-memory cleanup, skill promotion, and readiness checks before large agent rollouts.

## Why Ambience

Ambience gives teams a path from first memories to context operations without forcing a large connector project first. It captures typed memories, links sources, applies scopes, redacts before storage, reviews conflicts, and audits agent use.

## Related

- [Context Readiness Score](https://ambience.sh/company-context/readiness-score)
- [Company Context Map](https://ambience.sh/company-context/company-context-map)
- [How to build company context with Ambience](https://ambience.sh/blog/build-company-context-with-ambience)