update: v0.6.2 - Restored Clustering, Fixed Build, and Refactored SCE Core

Author: sasus-dev

App.tsx

@@ -5,7 +5,7 @@ import {
   ChatMessage, SystemPrompt, SecurityRuleResult, ApiCall, ExtractionRule, EngineConfig, Dataset, GlobalConfig, Identity
 } from './types';
 import { INITIAL_GRAPH, INITIAL_SECURITY_RULES, INITIAL_SYSTEM_PROMPTS, INITIAL_EXTRACTION_RULES, INITIAL_IDENTITIES } from './constants';
-import { SCEEngine } from './lib/sceCore';
+import { SCEEngine } from './lib/sce/engine/SCEEngine';
 import { extractEntities, queryJointly } from './services/llmService';
 import { ShieldAlert, X } from 'lucide-react';
 import ReactMarkdown from 'react-markdown';
@@ -58,7 +58,10 @@ const DEFAULT_CONFIG: EngineConfig = {
   enableMemoryExpansion: true,
   enablePruning: true,
   enableSpreadingActivation: true,
+  enableHyperedges: true,
   safeMode: true,
+  enableFirewall: true, // v0.6.3 default
+  globalEnergyBudget: 10.0, // v0.6.3 default
   repulsionStrength: -1200,
   hybridRules: true,
   extractionProvider: 'groq',
@@ -182,7 +185,7 @@ const App: React.FC = () => {
   const config: EngineConfig = {
     ...DEFAULT_CONFIG,
     ...(globalConfig.engineConfig || {}), // Merge preserved logic/tuning
-    memoryWindow: globalConfig.engineConfig?.memoryWindow || 6 // Ensure explicit override matches
+    memoryWindow: globalConfig.engineConfig?.memoryWindow ?? 6 // Ensure explicit override matches
   };
   const securityRules = globalConfig.securityRules;
   const extractionRules = globalConfig.extractionRules;
@@ -956,6 +959,7 @@ const App: React.FC = () => {
                 addAuditLog('system', `User Updated Node: ${id}`, 'success');
               }}
               graph={graph}
+              onSelectNode={setSelectedNodeId}
             />
           </div>
         </div>

README.md

@@ -50,11 +50,12 @@ The result is memory that is:
 | Algorithmic Mesh Wiring | ✅ Implemented |
 | Data Hygiene (Strict Garbage Collection) | ✅ Implemented |
 | Accurate Telemetry (Performance metrics) | ✅ Implemented |
-| Node Connections (Natural Expansion) | ⚠️ In progress |
+| Node Connections (Natural Expansion) | ⚠️ Partly Implemented |
 | Hierarchical Auto-Clustering | ⚠️ In progress |
 | Prompt Optimization | ⚠️ In progress |
-| Production Ready | ⚠️ Research system |
-| Benchmarks | ❌ Community-needed |
+| Production Ready | ⚠️ Architecture Preview / Research system |
+| Optimization | ❌ Community-driven (once core is solidified) |
+| Benchmarks | ❌ Community-driven (once core is solidified) |
 
 **License:** Apache 2.0 • **Maintainer:** [Sasu](https://www.sasus.dev) • **Updates:** [docs/updates/](docs/updates/)
 
@@ -197,10 +198,6 @@ Failure modes become visible instead of implicit.
 
 ## 🖥️ The Core Engine (UI & Orchestration)
 
-The engine consists of two main components:
-- **[`lib/sce/`](lib/sce/)** - Modular Cognitive Engine (Orchestrator, Physics, Learning, Structure)
-- **[`components/CoreEngine.tsx`](components/CoreEngine.tsx)** - UI orchestration and visualization
-
 ### Engine Layout (v0.6+)
 - **Orchestrator**: [`lib/sce/engine/SCEEngine.ts`](lib/sce/engine/SCEEngine.ts) (Thin wrapper, manages subsystems)
 - **Graph**: `lib/sce/graph/` (Adjacency Index)
@@ -231,7 +228,7 @@ Think of it as **mission control for context assembly**—designed for debugging
   <p><sub><em>Security rules block harmful queries before LLM inference</em></sub></p>
 </div>
 
-SCE is **not** a silver bullet—but it reshapes the threat landscape:
+SCE is **not** a silver bullet for all security concerns— but it reshapes the threat landscape:
 
 | Attack Vector | RAG Systems | SCE |
 |--------------|-------------|-----|
@@ -395,7 +392,7 @@ This project is developed by a single independent dev, not a software company, n
 
 **Project Status:** The core architecture is functional, but it needs more testing, tweaking and optimization. The current challenge is how the system creates connections / evolves / flows naturally (how the graph expands naturally and learns along the way). This require a deep dive / experimentations on hypergraphs, graph theory and cognitive architecture research.
 
-**Why Open-Sourced:** While SCE was built to solve memory architecture challenges in games and digital twin systems, it was open-sourced specifically because of its potential to address many security concerns in current AI systems and perhaps even enable safer alignment. If this were purely about better memory optimization, it would have remained proprietary.
+**Why Open-Sourced:** While SCE was built to solve memory architecture challenges in games and digital twin systems, it was open-sourced specifically because of its potential to address many security concerns in current AI systems and perhaps enable safer alignment. If this were purely about better memory optimization, it would have remained proprietary.
 
 **What's Needed from the Community:**