Back to corpus
proposalexperiment writeup candidatescore 22

Evolution³ — Stage 0: Research Brief (V4)

**V2 (Technical Substrate)** decided: - Centralized TypeScript daemon with hot standby on Mac4 - TOML declarative manifests for service/flow/skill definitions - WebSocket pub/sub event bus for inter-service messaging - 43-task master plan, 264 hours, 10-16 weeks

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

# Evolution³ — Stage 0: Research Brief (V4) ## NUMU FARE — Rust Core + Native Thread Intelligence + openclaw Library Integration ### Generated: 2026-03-05 | Method: 3 parallel research agents + 2 prior evo-cube runs (V2 substrate, V3 personal OS) **V2 (Technical Substrate)** decided: - Centralized TypeScript daemon with hot standby on Mac4 - TOML declarative manifests for service/flow/skill definitions - WebSocket pub/sub event bus for inter-service messaging - 43-task master plan, 264 hours, 10-16 weeks **V3 (Personal Integration)** decided: - Name: **NUMU FARE** (ߒߎߡߎ ߝߊ߬) — "The Forge That Crosses" - CLI: `numu`, Fleet: `numu fleet`, Intelligence: "The Weave" - 147 skills with heat tracking + memory spines (40 active, 107 cold storage) - Adaptive enrichment curriculum (MASTER/CRAFTSMAN/JOURNEYMAN depth) - ADI personas as forge temperatures - 7-wave implementation plan (~7 weeks, score target 7.6→9.2) **V4 introduces three new dimensions that reshape the architecture:** 1. The openclaw/openclaw library patterns — proven at scale, directly adoptable 2. Rust as the daemon language — performance, safety, deployment characteristics 3. Native Discord thread management — threads as first-class workspaces, not afterthoughts ### What It Is A TypeScript/Node.js personal AI assistant platform (263K+ GitHub stars). It solves many of the same problems NUMU FARE faces: multi-model orchestration, skill/tool management, context enrichment, memory search, session management.

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.