close fullscreen

About Hyperon+OpenCog Legacy+OpenCog Legacy Full+Why Hyperon Replaced OpenCog

help edit space_dashboard

The transition was motivated by five architectural limitations identified over a decade of experience with OpenCog Classic:

1. Integration depth was insufficient. Building Better Minds (2012) identified cognitive synergy as the "secret sauce" but acknowledged that OpenCog implemented "perhaps one third to one half of the key ideas." Component boundaries created brittle semantic bottlenecks. The AtomSpace was designed as a blackboard for inter-subsystem communication, but this "doesn't work in practice" because subsystems (MOSES, RelEx, etc.) maintained their own internal representations with no shared ontology. MOSES in particular was "rather isolated from the rest of OpenCog" (Nil Geisweiller, 2017).

2. Language limitations. Atomese required manual encoding in Scheme and lacked self-modification. The rule engine suffered from fragmentation: URE, Pattern Matcher, Scheme/Python scripting, and GroundedSchemaNodes each handled different aspects of inference with no unified execution model. MeTTa provides homoiconicity, a formal type system, and native nondeterminism.

3. Performance architecture. The C++ AtomSpace used flat hypergraph storage with \(O(N)\) scan costs. MORK's prefix-tree provides near-constant-time lookups, lock-free concurrent access, and memory layouts supporting both symbolic and dense numeric operations.

4. Mathematical foundations were missing. OpenCog's components were "loosely integrated" without shared formal controls. The 2025 whitepaper introduces quantale-based weakness theory, geodesic inference control, and TransWeave as unifying mathematical principles.

5. No decentralization. OpenCog ran on single machines or small clusters. Hyperon targets decentralized execution via ASI Chain with cryptographic provenance and capability-secured processes.