Auto-sync: 2026-04-28 12:03
This commit is contained in:
52
wiki/concepts/Context-Cores.md
Normal file
52
wiki/concepts/Context-Cores.md
Normal file
@@ -0,0 +1,52 @@
|
||||
---
|
||||
title: "Context-Cores"
|
||||
type: concept
|
||||
tags: [AI-Memory, Context-Substrate, Version-Control, Portable-Context, Software-Engineering]
|
||||
sources: [ai-memory-tools-two-camps]
|
||||
last_updated: 2026-04-15
|
||||
---
|
||||
|
||||
## Definition
|
||||
由 [[TrustGraph]] 引入的概念——便携、带版本的上下文容器,包含领域 schema、知识图谱、向量嵌入、证据来源和检索策略。将上下文视为代码工程制品。
|
||||
|
||||
## Core Components
|
||||
一个 Context Core 包含:
|
||||
- **领域 Schema**:定义上下文中有什么类型的实体和关系
|
||||
- **知识图谱**:实体和关系的结构化表示
|
||||
- **向量嵌入**:语义检索支持
|
||||
- **证据来源**:每条上下文可追溯到原始来源
|
||||
- **检索策略**:如何查询和组合上下文
|
||||
|
||||
## Version Control Semantics
|
||||
Context Cores 的核心类比是**将上下文视为代码**:
|
||||
- **版本化(versioning)**:追踪上下文的演变历史
|
||||
- **测试(testing)**:验证上下文质量
|
||||
- **推动(promoting)**:将上下文从开发环境推入生产
|
||||
- **回滚(rolling back)**:恢复到之前状态
|
||||
|
||||
## Operational Value
|
||||
|
||||
### Agent 交接
|
||||
将 Context Core 交给新 Agent → 继承完整运营上下文
|
||||
```
|
||||
New Agent + Context Core → Full operational context
|
||||
```
|
||||
|
||||
### 实验分叉
|
||||
分叉一个 Context Core 做实验 → 合并回主分支
|
||||
```
|
||||
Main Context Core → Experiment Branch → Merge Back
|
||||
```
|
||||
|
||||
## Conceptual Significance
|
||||
TrustGraph 的 Context Cores 是整个 AI 记忆工具领域最接近**可部署的上下文单元**的概念。每个 Camp 1 工具将记忆视为对话的副作用。TrustGraph 将上下文视为有身份、版本和生命周期的第一等制品。
|
||||
|
||||
## Implementation Note
|
||||
TrustGraph 的实际实现较重(Cassandra + Qdrant),但概念模型是正确的方向——Context Core 的设计允许:
|
||||
- 团队成员间共享上下文
|
||||
- 在不同 Agent 间迁移
|
||||
- 对上下文变更进行 code review
|
||||
|
||||
## Connections
|
||||
- [[TrustGraph]] ← 引入 ← Context-Cores 由 TrustGraph 引入
|
||||
- [[ai-memory-tools-two-camps]] ← 来源 ← Context-Cores 是 @witcheer 识别的最接近"可部署上下文单元"的概念
|
||||
Reference in New Issue
Block a user