close fullscreen

Implementation Families

help edit space_dashboard
Draft — This content has not been approved for publication.

Implementation family cards map the actual repositories in the Hyperon ecosystem — what code exists, how it's structured, and how to get started. They complement the Technical Companions layer, which covers mathematical foundations and formal definitions.

Each family groups related repositories by functional domain, documenting build commands, maturity levels, dependency relationships, and consolidation opportunities.

Families

  • MeTTa Implementations — Compilers, interpreters, and formal specs across Rust, Prolog, JVM, Scheme, and Scala
  • Knowledge Substrates — AtomSpace, MORK, DAS, and their storage backends, parsers, and tooling
  • Reasoning and Search — PLN, chaining, MOSES, and pattern mining implementations
  • Attention and Motivation — ECAN attention allocation and MetaMo/OpenPsi motivational frameworks
  • NARS Ecosystem — Non-Axiomatic Reasoning implementations across C, MeTTa, and Prolog
  • Game Worlds and Simulated Environments — Minecraft integration, autonomous agent architectures, and RL benchmarks
  • Robotics and Embodiment — Physical robotics, ROS integration, and abstract sensory/motor primitives
  • Bio-AI and Cheminformatics — Biological data pipelines, molecular chemistry, and biomedical knowledge graphs
  • Neural-Symbolic and LLM Integration — LLM agent libraries, RAG, semantic search, and MCP integration
  • Infrastructure and Developer Surfaces — Packaging, deployment, testing, developer tooling, and governance


Tags

help edit space_dashboard
ai generated
more_horiz
open_in_full page
fullscreen modal
edit edit
space_dashboard advanced


Discussion