Back to corpus
architecturetechnical paper candidatescore 48

DEP + Evo-Cubed: Skill Entity Architecture (SEA)

> **Deprecation note (2026-05-13):** Mac3 was the Tier 2 worker host at the time this phase shipped. Mac3 has since been retired. References in this document reflect the Feb-2026 architecture and are kept for historical accuracy. The current home for Tier 2 scoring is Mac4:8100 (cognitive twin). See SOOP-2 launch memory for migration plan.

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

> **Deprecation note (2026-05-13):** Mac3 was the Tier 2 worker host at the time this phase shipped. Mac3 has since been retired. References in this document reflect the Feb-2026 architecture and are kept for historical accuracy. The current home for Tier 2 scoring is Mac4:8100 (cognitive twin). See SOOP-2 launch memory for migration plan. An inverted skill system where creative/philosophical skills become autonomous daemon entities. ### Current Problem - 105+ skills in [home-path] — most are static files loaded on-demand - Creative/philosophical skills (phi:*, art:*, nav:*) are powerful but interfere with normal operations - Skills have no memory of when they've been useful before ### Proposed Architecture 1. Discord Category: Skill Entities — each skill gets its own channel 2. Each channel has the skill SKILL.md as system prompt + rolling conversation history 3. Router middleware intercepts every prompt/response in main channels 4. Relevance scoring — broadcasts to each skill-entity: Score 0-1 how relevant are you 5. Threshold activation — any skill above threshold (0.7) gets full context and generates injection 6. Injection gets appended as skill perspective before final response ### Model Strategy - Scorer (hot path): MiniMax-3B-v0.1 local model at localhost:18080 (free, fast) for relevance classification - Activator (cold path): Heavier model only when threshold crossed - Each skill evolves its own activation patterns based on accumulated history

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.