# kernel-memory - Doramagic AI Context Pack

> Purpose: pre-work context for the user's host AI. This pack does not prove that the project has been installed, run, or validated.

## Project

- canonical_name: `microsoft/kernel-memory`
- capability: Research project. A Memory solution for users, teams, and applications.
- expected_user_outcome: Research project. A Memory solution for users, teams, and applications.

## Operating Boundaries

- Do not claim that the project has been installed, run, called through an API, or used on local files unless separate evidence proves it.
- Project facts must come from repo evidence, Claim Graph, or explicit source references.
- When a capability is not verified, mark it as unverified instead of completing it as fact.
- publish_status: `publishable`
- blocking_gaps: none

---

## Doramagic Context Augmentation

The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints.

## Human Manual Outline

Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph.

Host AI hard rules:
- Do not treat page titles, section order, summaries, or importance values as factual project evidence.
- When explaining the Human Manual outline, state that it is only a reading route or salience signal.
- Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph.

- **Overview & Core Architecture**: importance `high`
  - source_paths: README.md, service/Abstractions/IKernelMemory.cs, service/Abstractions/IKernelMemoryBuilder.cs, service/Abstractions/KernelMemoryBuilderExtensions.cs, service/Abstractions/KernelMemoryBuilderBuildOptions.cs
- **Ingestion Pipeline & Retrieval (RAG)**: importance `high`
  - source_paths: service/Abstractions/Pipeline/IPipelineStepHandler.cs, service/Core/Handlers/TextExtractionHandler.cs, service/Core/Handlers/TextPartitioningHandler.cs, service/Core/Handlers/GenerateEmbeddingsHandler.cs, service/Core/Handlers/GenerateEmbeddingsParallelHandler.cs
- **Extensions, Connectors & Client Integrations**: importance `high`
  - source_paths: extensions/AzureOpenAI/AzureOpenAI/AzureOpenAIConfig.cs, extensions/AzureOpenAI/AzureOpenAI/AzureOpenAITextGenerator.cs, extensions/AzureOpenAI/AzureOpenAI/AzureOpenAITextEmbeddingGenerator.cs, extensions/OpenAI/OpenAI/OpenAITextGenerator.cs, extensions/OpenAI/OpenAI/OpenAITextEmbeddingGenerator.cs
- **Deployment, Configuration & Customization**: importance `high`
  - source_paths: Dockerfile, service/Service/Program.cs, service/Service/appsettings.json, service/Service/README.md, service/Service/Internals/OpenAPI.cs

## Repo Inspection Evidence

- repo_clone_verified: true
- repo_inspection_verified: true
- repo_commit: `8fc4e16f31257faa34c5e368f8e99b45df7e4049`
- inspected_files: `Dockerfile`, `README.md`, `examples/000-notebooks/appsettings.json`, `examples/001-dotnet-WebClient/Properties/launchSettings.json`, `examples/001-dotnet-WebClient/README.md`, `examples/001-dotnet-WebClient/appsettings.json`, `examples/001-dotnet-WebClient/file9-settings.json`, `examples/002-dotnet-Serverless/Properties/launchSettings.json`, `examples/002-dotnet-Serverless/README.md`, `examples/002-dotnet-Serverless/appsettings.json`, `examples/002-dotnet-Serverless/file9-settings.json`, `examples/003-dotnet-SemanticKernel-plugin/Properties/launchSettings.json`, `examples/004-dotnet-serverless-custom-pipeline/Properties/launchSettings.json`, `examples/004-dotnet-serverless-custom-pipeline/README.md`, `examples/004-dotnet-serverless-custom-pipeline/appsettings.json`, `examples/005-dotnet-async-memory-custom-pipeline/Properties/launchSettings.json`, `examples/005-dotnet-async-memory-custom-pipeline/README.md`, `examples/005-dotnet-async-memory-custom-pipeline/appsettings.json`, `examples/006-curl-calling-webservice/README.md`, `examples/007-dotnet-serverless-azure/Properties/launchSettings.json`

Host AI hard rules:
- Without repo_clone_verified=true, do not claim that the source code has been read.
- Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts.
- Without quick_start_verified=true, do not claim that the Quick Start path has run successfully.

## Doramagic Pitfall Constraints

These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes.

### Constraint 1: Installation risk requires verification

- Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow.
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: identity.distribution | https://github.com/microsoft/kernel-memory
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 2: Capability evidence risk requires verification

- Trigger: README/documentation is current enough for a first validation pass.
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: capability.assumptions | https://github.com/microsoft/kernel-memory
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 3: Maintenance risk requires verification

- Trigger: Project evidence flags a maintenance risk. Review the linked source before relying on this workflow.
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: evidence.maintainer_signals | https://github.com/microsoft/kernel-memory
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 4: Security or permission risk requires verification

- Trigger: no_demo
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: downstream_validation.risk_items | https://github.com/microsoft/kernel-memory
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 5: Security or permission risk requires verification

- Trigger: no_demo
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: risks.scoring_risks | https://github.com/microsoft/kernel-memory
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 6: Maintenance risk requires verification

- Trigger: issue_or_pr_quality=unknown。
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: evidence.maintainer_signals | https://github.com/microsoft/kernel-memory
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 7: Maintenance risk requires verification

- Trigger: release_recency=unknown。
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: evidence.maintainer_signals | https://github.com/microsoft/kernel-memory
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.
