Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Epic: ToCS-based agent evaluation framework for ADF

Abierto
#691 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
rust
Área
ai, testing

Línea de trabajo

Start with cto-executive-system/plans/tocs-terraphim-ai-evaluation-plan.md, cto-executive-system/plans/adf-architecture-improvements.md, and the referenced ToCS paper and repository; review dependency #689 before planning hook-based work. Done requires the design to be split into scoped sub-issues covering the baseline, probe collection, scoring, belief monitoring, NightwatchMonitor integration, and later KG enrichment.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement

Context

No existing ADF mechanism measures whether agents genuinely understand the codebases they operate on, or merely execute surface-level patterns. Theory of Code Space (ToCS, arXiv:2603.00601) provides a 4-dimension evaluation framework for exactly this.

Proposal

Implement ToCS-inspired evaluation to measure ADF agent effectiveness across four dimensions:

Evaluation Dimensions
Dimension What It Measures Metric
Construct Does the agent build an accurate dependency map? Edge F1 by type (IMPORTS, CALLS_API, REGISTRY_WIRES, DATA_FLOWS_TO)
Revise Does the agent update beliefs when code changes? Belief revision score (delta accuracy after code change)
Exploit Can the agent predict impact of changes? Counterfactual probe accuracy
Constraints Does the agent discover architectural rules? Invariant discovery F1 vs CLAUDE.md/domain model rules
Implementation Phases
  1. Phase 0: Run ToCS benchmark against terraphim-ai workspace with current agents (baseline)
  2. Phase 1: Add periodic cognitive map probing -- every N tool calls, externalise understanding as structured JSON
  3. Phase 2: Compare probes against ground truth (KG-derived dependency graph) to compute scores
  4. Phase 3: Feed scores to NightwatchMonitor as new signal type (alert on degradation)
Cognitive Map Probing
  • Injected via PreToolUse hooks (Agent SDK) or system messages (subprocess)
  • Agent outputs structured JSON: nodes (modules), edges (dependencies, typed), confidence scores
  • Compared against ground truth from terraphim KG + tree-sitter analysis
Key Insight from ToCS Research
  • Aho-Corasick automata cover ~67% of edges (IMPORTS level)
  • CALLS_API (~17%) and DATA_FLOWS_TO (~7%) require semantic understanding
  • Some models show "catastrophic belief collapse" -- losing knowledge between probes
  • Evaluation framework should be built BEFORE KG enrichment (measure first, improve later)
Sub-issues (to be created during design phase)
  • Run ToCS baseline against terraphim-ai workspace
  • Implement cognitive map probe injection and collection
  • Implement belief stability monitoring (successive probe comparison)
  • Integrate evaluation scores with NightwatchMonitor
  • KG enrichment with tree-sitter call graph (after baseline confirms gap)

References

  • ToCS paper: https://arxiv.org/abs/2603.00601
  • ToCS repo: https://github.com/che-shr-cat/tocs
  • KB article: cto-executive-system/knowledge/external/context-engineering/tocs-theory-of-code-space-benchmark.md
  • Expansion plan: cto-executive-system/plans/tocs-terraphim-ai-evaluation-plan.md
  • ADF plan: cto-executive-system/plans/adf-architecture-improvements.md (item 3.1)
  • Depends on: #689 (Agent SDK migration for hook-based probe injection)
  • Related: #682 (Pi eval epic), #687 (steering queues)
Lenguaje dominante
Rust
Estrellas
62
Forks
5
Merge medio
2 h 27 min
PR fusionados (30 d)
1

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de terraphim/terraphim-ai

Todos los issues de terraphim/terraphim-ai

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.