Back to corpus
proposalexperiment writeup candidatescore 22

KARL Integration -- Evolution3 / Stage 0: RESEARCH

**This is exactly the trajectory data KARL needs.** The data exists but flows into storage (unified.jsonl, verbose-all.jsonl) without any feedback loop to skill improvement. The unified store has 3,909 entries with tool_calls arrays -- this is a goldmine of trajectory data that currently goes unused for learning.

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

# KARL Integration -- Evolution3 / Stage 0: RESEARCH **Run:** karl-trajectory-intelligence **Generated:** 2026-03-10 **Method:** Evolution3 -- four-stage recursive evoflow (research-grounded) **Run Directory:** Desktop/evo-cube-output/karl-trajectory-intelligence/ ## Noosphere Context No prior dreams or patterns found on this topic. Fresh ground. ### Architecture Overview The Cortex is a self-improving behavioral intelligence system at `[home-path]` with 7 phases, 17 Python files, 29 tests, and 3 hooks. Its data store is `[home-path]` (currently 399 entries: 324 invocation_records + 75 decay_flags). #### 1a. Extractor (`[home-path]`, 287 lines) - **Pipeline**: 4-pass -- Load+Filter, Tokenize+N-gram, Cluster (Jaccard >0.6), Enrich - **Input**: `[home-path]` (currently 903 entries) - **Output**: `CortexEntry(type="skill_candidate")` objects - **Filtering**: Lines 41-67 define SKIP_PATTERNS (automated prompts, trivial inputs like "yes", "ok", "continue") - **Tokenization**: Line 96-98 -- lowercase, strip punctuation, remove stop words, 2-4 word n-grams - **Clustering**: Line 157 -- requires `min_count=15` for meaningful clusters. Jaccard threshold 0.6 at line 192 - **Domain detection**: Lines 70-81 -- 10 operational domains (ios, deploy, supabase, docker, git, prefect, monitoring, mesh, debug, asc) - **Cap**: 30 candidates maximum (line 224) - **Critical gap**: Only extracts intent *labels* from prompts. Does NOT capture tool-use sequences, file paths touched, success/failure signals, or the full trajectory of how a task was accomplished. #### 1b. Generator (`[home-path]`, 178 lines) - **Input**: `CortexEntry` skill candidate - **Output**: Static SKILL.md file with frontmatter (YAML) + markdown body - **Template variables**: Lines 19-59 define DOMAIN_TOOLS, DOMAIN_MACHINES, DOMAIN_TRIGGERS per domain - **Content**: Generic 4-step workflow (check state, execute, verify, report) at lines 112-127 - **Critical gap**: Generated skills are *static templates*, not learned procedures. The "Workflow" section is the same 4 generic steps for every skill. No tool sequences, no gotcha accumulation from actual failures, no reward signal integration.

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.