Epic: Ouroboros-inspired agent infrastructure patterns
还没有人认领这个 Issue。
评估
调研方向
Start with the existing agent areas named in the issue—supervisor, registry, messaging, evolution, goal_alignment, task_decomposition, kg_agents, and kg_orchestration—and read plans/terraphim-ouroboros-rebuild-assessment.md plus the referenced knowledge files. Work through subissues #596–#602 in dependency order; completion is the set of exit criteria covering guardrails, event logging, budgets, learning capture, verdicts, EIDOS tracking, and KG promotion.
由索引模型根据 Issue 内容生成。
描述
Summary
Absorb operational patterns from joi-lab/ouroboros and vibeship-spark-intelligence into terraphim's existing Rust architecture. Not a rebuild -- selective pattern adoption to close gaps in the agent layer and complete terraphim_agent_evolution.
Context
Ouroboros and Spark Intelligence demonstrate infrastructure patterns that terraphim's agent system (supervisor, registry, messaging, evolution, goal_alignment, task_decomposition, kg_agents, kg_orchestration) currently lacks. The foundation layer (types, automata, rolegraph, persistence, middleware, hooks, MCP) is solid; the agent layer is incomplete.
Ouroboros Patterns
- #596 Constitutional Guardrails (CONSTITUTION.md) -- ~2 hours
- #597 Event Sourcing for Agent Decisions -- ~1 day
- #598 Budget-Aware Multi-Model Routing -- ~4 hours
Spark Intelligence Patterns
- #599 Enhanced Learning Capture (multi-hook pipeline + importance scoring) -- ~1 day
- #600 Dimensional Verdict Scoring / Meta-Ralph (6-dimension judge scores) -- ~4 hours
- #601 EIDOS Episodic Reasoning (prediction-outcome tracking) -- ~1 day
- #602 Confidence-Driven KG Promotion (EIDOS threshold gates KG entry creation) -- ~1 day
Execution Order
#596 Constitutional Guardrails ─────────────────────────────────┐
│
#597 Event Sourcing ────┬──── #598 Budget-Aware Routing │
│ │
├──── #599 Enhanced Learning Capture │
│ | │
│ v │
├──── #600 Dimensional Verdict Scoring │
│ | │
│ v │
└──── #601 EIDOS Episodic Reasoning │
| │
v │
#602 Confidence-Driven KG Promotion│
#596 and #597 have no prerequisites and can start in parallel.
#602 is the capstone: Event Capture -> Event Store -> EIDOS -> Promotion -> KG Entry -> Aho-Corasick Automata.
Patterns NOT Adopted (and why)
| Pattern | Reason |
|---|---|
| Self-modifying source code | Rust compilation latency makes rapid evolution cycles impractical. Compound engineering (knowledge mutation via AGENTS.md/MEMORY.md) achieves continuous improvement without code mutation. |
| Background consciousness loop | Premature -- agent system needs to work before adding always-on thinking. v2.0 pattern. |
| LLM-first philosophy | Contradicts terraphim's deterministic-first philosophy. Aho-Corasick for deterministic matching, LLM only for reasoning. |
| Task deduplication via LLM | Use Aho-Corasick automata for semantic dedup. Faster, deterministic, cheaper. |
Design Principle
Terraphim's identity is Aho-Corasick + local-first data sovereignty. Agent evolution is not about self-modifying code (Ouroboros) -- it's about self-improving knowledge quality (Spark). The evolution happens in confidence-gated KG promotion, not in source code mutation. The Aho-Corasick engine stays constant; the knowledge graph grows autonomously when confidence thresholds are met.
Reference
- Analysis:
plans/terraphim-ouroboros-rebuild-assessment.md(in cto-executive-system) - KB entries:
knowledge/ouroboros-self-modifying-agent.md,knowledge/spark-intelligence-self-evolving-companion.md
Exit Criteria
- Constitutional guardrails enforced by agent_supervisor before execution
- Agent decisions logged as immutable event stream with drift detection
- LLM calls tracked per-task with budget limits and fallback chains
- Learning capture covers all three hook types with importance scoring
- Judge verdicts use 6-dimensional scoring with feedback loops
- EIDOS prediction-outcome loop tracks advisory accuracy
- High-confidence insights auto-promote to KG entries via Aho-Corasick indexing
- 主要语言
- Rust
- 星标
- 62
- 派生
- 5
- 平均合并
- 2 小时 27 分钟
- 30 天内合并 PR
- 1
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
terraphim/terraphim-ai 的其他 Issue
-
难度 5/5 一周以上 新手友好度 25/100
terraphim/terraphim-ai#885 ·
-
难度 4/5 3-5 天 新手友好度 55/100
terraphim/terraphim-ai#871 ·
-
enhancement
难度 5/5 一周以上 新手友好度 25/100
terraphim/terraphim-ai#810 · 2 条评论 ·
-
enhancement
难度 5/5 一周以上 新手友好度 35/100
terraphim/terraphim-ai#729 ·
-
enhancement
难度 5/5 一周以上 新手友好度 35/100
terraphim/terraphim-ai#728 ·
查看 terraphim/terraphim-ai 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
BurntSushi/jiff#653 ·
-
难度 2/5 1-3 小时 新手友好度 72/100
ZcashFoundation/zeeder#106 ·
-
难度 2/5 1-3 小时 新手友好度 76/100
oxidize-rb/rb-sys#807 ·
-
难度 2/5 1-3 小时 新手友好度 88/100
-
todo:ticket
难度 2/5 1-2 天 新手友好度 74/100