Current Status
-
Operational: Classical C++ AtomSpace (mature, production-grade); Hyperon Experimental Rust reference (active development, Python packages available); Space API abstraction with multiple backends
-
Under development: MORK as primary high-performance Space backend; MeTTa-4 semantic model alignment; Windows Python packages for Hyperon Experimental
-
Proposed: Neural Spaces (DNNs as queryable AtomSpaces); Rholang AtomSpace for decentralized execution; native MeTTa-to-machine-code compilation
Open Problems / Research Directions
- Convergence of the classical C++ type hierarchy and Hyperon's minimal 4-variant system — which atom types should be primitive vs. user-defined?
- Space API standardization across implementations (MORK, DAS, hyperon-experimental, JeTTa)
- Neural Space design — defining meaningful match/bind/rewrite semantics for embedding-backed AtomSpaces
- Formal metagraph theory — extending the sheaf-theoretic foundations to cover the full Hyperon Space API
Primary Sources