Back to corpus
research noteexperiment writeup candidatescore 52

EVO-CUBE REPORT: CognitiveTwin Pipeline

**Date:** 2025-07-18 **Codebase:** `Desktop/Comp-Core/packages/cognitive-twin/` (93 Python files, ~47K LOC) **Data:** 43K records across 8 expansion stages + combined_v5_v8 final dataset **Target Model:** Kimi-K2-Thinking (MoE-1T, 32B active params)

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

# EVO-CUBE REPORT: CognitiveTwin Pipeline ### CEF + DEP-2 + Evolution — Full Audit **Date:** 2025-07-18 **Codebase:** `Desktop/Comp-Core/packages/cognitive-twin/` (93 Python files, ~47K LOC) **Data:** 43K records across 8 expansion stages + combined_v5_v8 final dataset **Target Model:** Kimi-K2-Thinking (MoE-1T, 32B active params) 1. [Phase 1 — CEF (Critique–Evil–Find)](#phase-1--cef) - [Meta-Evil: Pipeline-Level Attacks](#11-meta-evil-pipeline-level-attacks) - [Chunk-Evil: Per-Module Attacks](#12-chunk-evil-per-module-attacks) - [Synthesis-Evil: Cross-Stage Data Quality](#13-synthesis-evil-cross-stage-data-quality) 2. [Phase 2 — DEP-2 (6-Level RTD + Fixes)](#phase-2--dep-2) 3. [Phase 3 — Evolution](#phase-3--evolution) 4. [Issue Tracker](#issue-tracker) 5. [Verdict](#verdict) The comment says "only caught 5/2177" so the threshold was weakened. But lowering to 1 means **any message ending with a question mark (stall_score=1) triggers UNJUSTIFIED classification** — even messages like "Here is the implementation. Does this approach work?" which scored exec=3 but would now hit stall≥1. The only protection is the `exec_score == 0` check in `is_unjustified()`, but the secondary rule bypasses exec: This secondary rule has **no exec_score gate** — a response that contains "should we" (strong permission phrase) PLUS code PLUS question mark will be classified UNJUSTIFIED even though it executed. This corrupts the corpus surgery stage by flagging legitimate clarifications-after-execution as unjustified.

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.