# MemoryOps vs ContextOps

> MemoryOps operates durable AI-agent memory. ContextOps operates the broader context layer.

MemoryOps asks what the organisation remembers, who can use it, whether retrieval works, and what needs review.

ContextOps asks what sources feed the agent, what gets retrieved, what is placed in the prompt, how the agent cites it, and how the team measures or repairs the loop.

## The split

MemoryOps focuses on durable memories: decisions, conventions, skills, patterns, failures, and references. It asks whether these memories are current, scoped, source-linked, retrievable, and safe to use.

ContextOps focuses on the full context flow. It includes MemoryOps, but also covers source selection, runtime packaging, retrieval behavior, answer grounding, and repair when context is missing or wrong.

## Why Ambience owns the overlap

Ambience starts from governed memory because durable company context is where agent work compounds. That makes MemoryOps the first measurable layer.

From there, Ambience extends into ContextOps by delivering scoped start context through agent hooks, MCP, CLI, and app surfaces while preserving audit and value evidence.

## Related

- [MemoryOps](https://ambience.sh/company-context/memoryops)
- [ContextOps](https://ambience.sh/company-context/contextops)
- [How to manage context for AI agents](https://ambience.sh/answers/how-to-manage-context-for-ai-agents)
- [Context Readiness Score](https://ambience.sh/company-context/readiness-score)