KARL Integration -- Evolution3 / Stage 2: COMPOUND

# KARL Integration -- Evolution3 / Stage 2: COMPOUND **Run:** karl-trajectory-intelligence **Generated:** 2026-03-10 **Method:** Evolution3 -- sequential compounding **Run Directory:** Desktop/evo-cube-output/karl-trajectory-intelligence/ Stage 0 established that the Cortex pipeline operates on **prompt text only** (Section 1, core limitation). It has zero visibility into tool sequences, exit codes, file diffs, or task outcomes. All five Stage 1 paths converged on the same foundational requirement: a structured trajectory record that captures what actually happened during a session, not just what the user asked for. Path A designed the `TrajectoryRecord` schema with 4 tap points in existing hooks. Path B discovered that `verbose-all.jsonl` already contains 3,249 entries with 157 multi-step tool sequences. Path D needs trajectory outcomes to weight its embedding space. Path C needs execution records to compute L4 fitness. Path E needs a place to store solver attempt trajectories. They all need the same thing: a unified trajectory store with outcome annotations. The unified data layer merges Path A's live recording with Path B's historical extraction into a single trajectory store at `[home-path]`. Two channels feed it: Four tap points in existing hooks, exactly as Path A specified: - **Tap A** (`ops_trigger.py`, after line 226): Initialize session buffer when skill is injected. Cost: ~5ms. - **Tap B** (`post_tool_hook.py`, after line 244): Append tool event metadata per tool call. Cost: ~8ms. - **Tap C** (`response_hook.py`, after line 838): Flush session buffer into a TrajectoryRecord at Stop. Cost: ~15ms. - **Tap D** (`ops_trigger.py`, beginning of main()): Annotate the previous record with cross-turn outcome signals at the next UserPromptSubmit. Cost: ~10ms.