Back to corpus
architecturetechnical paper candidatescore 62

DEP Integration Report — Skill Entity Architecture (SEA)

**Date:** 2026-02-18 **Evaluator:** Subagent DEP (Deep Evaluation Pass) **Scope:** Full 4-layer integration verification **Overall Verdict:** ⚠️ **PARTIALLY INTEGRATED**

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

**Date:** 2026-02-18 **Evaluator:** Subagent DEP (Deep Evaluation Pass) **Scope:** Full 4-layer integration verification **Overall Verdict:** ⚠️ **PARTIALLY INTEGRATED** The SEA system is architecturally sound and functionally operational. All 13 skill entities exist with valid metadata, the scoring pipeline works end-to-end, and enriched dispatch integration is live. However, **Tier 1 embedding-based routing is underperforming** (only 6/10 queries pass the 0.4 threshold), the keyword fallback is silently compensating, and there are minor gaps in documentation alignment and plan tracking. ### Skill-Memory Entities (13/13) | Entity | state.json | hot_topics | cold_topics | versions.json | snapshots | activation-log | |--------|-----------|------------|-------------|--------------|-----------|----------------| | art:convergent | ✅ | 5 | 2 | ✅ | ✅ | ✅ | | art:creative | ✅ | 5 | 2 | ✅ | ✅ | ✅ | | art:divergent | ✅ | 5 | 2 | ✅ | ✅ | ✅ | | art:dj | ✅ | 5 | 2 | ✅ | ✅ | ✅ | | art:movement | ✅ | 5 | 2 | ✅ | ✅ | ✅ | | art:snark | ✅ | 5 | 2 | ✅ | ✅ | ✅ | | art:synthesis | ✅ | 5 | 2 | ✅ | ✅ | ✅ | | nav:nonlinear | ✅ | 5 | 2 | ✅ | ✅ | ✅ | | nav:organic | ✅ | 5 | 2 | ✅ | ✅ | ✅ | | nav:perspective | ✅ | 5 | 2 | ✅ | ✅ | ✅ | | phi:metaphysical | ✅ | 5 | 2 | ✅ | ✅ | ✅ | | phi:paradox | ✅ | 5 | 2 | ✅ | ✅ | ✅ | | phi:veritas | ✅ | 5 | 2 | ✅ | ✅ | ✅ | ### ⚠️ Finding: Missing `confidence` field All 13 entities use `confidence_calibration` (value: 0.73) instead of `confidence` in state.json. The enriched_spawn.py `_load_skill_entity()` correctly reads `confidence_calibration` and maps it to `confidence` in the returned dict, so this is a naming inconsistency but NOT a functional bug. ### Embedding Cache - **File:** `[home-path]` — ✅ EXISTS (64.8 KB) - **Shape:** `(13, 384)` float32 — ✅ correct dimensions - **Model:** `all-minilm` (all-MiniLM-L6-v2 via Ollama on Mac4) - **Keys:** embeddings, skill_names, texts, model, dim, timestamp — all valid - **Skill names:** 13 entries, dtype `<U16` — ✅

Promotion decision

What has to happen next

Promote into a technical note or architecture paper with implementation anchors.

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.