Status and Resources

help edit space_dashboard

Last verified: 2026-06-01

Current Status

  • Operational: Triemap storage, ZAM execution, bidirectional pattern matching, MM2 language, PeTTa/MORK integration, mork_ffi for Prolog bridging
  • Under development: MORK-native PLN (backward chaining + factor graphs — paper/proposal/benchmark-only; a 2026 review of the MORK Rust source found no code-real FactorGraph PLN at this snapshot), WILLIAM trie instrumentation, and the IO/resource interface that retired the earlier ByteFlow GPU-offload and ShardZipper distributed-state experiments.
  • Recently shipped (2026-06; previously listed here as "under development"): the linalg tensor-logic crate (Einstein-notation sparse/dense kernels with an AVX JIT, ~290× over the interpreter) and a new asymptotically-optimal query-compilation path — MM2 queries lower to a fixed-memory, order-independent state machine that visits each trie location at most once, exposing a first-class stream set-algebra operator (intersection / union / subtraction; the operator itself was still landing as of mid-2026). This supersedes the earlier "streaming fusion (~10× slower)" status. (MORKification Weekly 2026-05-11 → 06-15.)
  • Proposed: Multi-machine distributed processing, QuantiMORK (neural tensor encoding), WASM edge deployment, native MeTTa-to-machine-code compiler

Implementation Findings (transcript-backed, MORKification Weekly Aug 2025–Apr 2026)

  • MM2 scale: ~350 grounded functions as of Jan 2026. One MM2 step triggers billions of parallel rewrites due to massive parallelization.
  • Sources/sinks architecture: Three-layer resource abstraction — resources, sources (readers), sinks (writers). This is the integration surface for ECAN weights, hypervectors, and external systems. Note: CountSink in the kernel is an MM2 query/reduction primitive (per-execution accumulator), not a persistent revision log — do not target it as a Decko card-history counter.
  • Compression benchmarks: PathMap uses seven levels of nested shared patterns to represent all 64-bit integers in 8 nodes. JSON import: 20× reduction (780 GB JSON → 40 GB ACT).
  • RAM scaling benchmark: PeTTa/MORK has been demonstrated up to 400M atoms in RAM (documented successful 100M/200M/300M/400M loads; 500M ran out of memory in the same benchmark). Earlier "500M+ atoms in RAM" wiki text treated the OOM ceiling as demonstrated capacity — corrected.
  • Streaming fusion investigation: Six implementations tested — all ~10× slower than binary operations due to branch traversal overhead. Active investigation with database-inspired query optimization.
  • Concurrency advantage: MORK surpasses ATRIUM (20,000 threads) on its own benchmarks due to sequential thread coordination rather than threads fighting over shared memory.
  • Applications: 4×4 Sudoku (~2 ms), CTL model checking, decision tree learning, Blocks World / PDDL planning.

Known Limitations (discussion-backed, MORK Mattermost)

  • Concurrency ceiling: MORK crashes at ~200 concurrent users (Rejuve.Bio load test, Mar 2026) rather than degrading gracefully.
  • No automatic persistence: Data lost on restart. Manual save/restore via paths_export() / paths_import().
  • Negative querying unsound: Removed from MM2. Use != or nested if/not/find instead.
  • Memory multiplier: ~64 bytes/atom. String-heavy datasets need interning (7 GB → 1.9 GB vs 31 GB default).
  • WASM deprecated: ~15× overhead. Pure Rust grounded functions now default.
  • Server-branch versioning: The mork-server deployment line is maintained on a separate server branch. As of last verification, three references were not reconciled: das-toolbox CLI defaults to image tags trueagi/das:mork-server-1.0.5 + mork-loader-1.0.5; das/src/docker/mork/Dockerfile.server pins MORK to a 2025-07 commit; and the live server branch has diverged substantially ahead of the DAS pin. Production deployment must reconcile all three references. Notable post-pin fixes in the gap include: server shutdown deadlock, user-status-map cleanup, a lock-held-too-long deadlock, UTF-8 validation for the symbol pathway, and edge-case/malformed-symbol test coverage.
  • Link/S-expression delete unsupported in DAS-MorkDB backend: The MorkDB implementation hard-fails on link delete. Node delete works (inherited from RedisMongoDB); link delete does not. flush_pattern + re_index_patterns provide batch-rebuild workarounds, NOT live mutable-store CRUD. See DAS Full.

Open Problems / Research Directions

  • Multi-machine distribution — scaling across clusters while preserving PathMap locality
  • QuantiMORK — wavelet/multiresolution DAG encoding for neural structures
  • GPU/TPU acceleration — dense/sparse numerical kernels shipped on CPU as the linalg crate (AVX JIT) behind the IO/resource interface (ByteFlow itself was retired); a GPU back end on the same interface remains open
  • Unifier correctness — the Vampire-derived unifier is now validated against SWI-Prolog over a ~100k-axiom oracle (PR #49), and a long-standing occurs-check / cyclic-term bug (issues #29/#43) was fixed and merged to main; a cascade of further unification edge-case bugs (two unification algorithms, both requiring cycle checks) was still being resolved as of mid-2026 (MORKification Weekly 2026-04-20 → 06-22)
  • Community and third-party package ecosystem
  • Formal verification of ZAM correctness properties
  • Decko-compatible mutable-backend semantics — link delete, transactional history, RichText/file/permission mappings; MORK alone does not provide them, an adapter layer is required

Primary Sources

  • Goertzel, B. (2025). Hyperon for AGI⇒ASI Whitepaper, §2.3, §3.6.
  • Peyton Jones, S. et al. Triemaps that Match.
  • Internal working papers: the July–October 2025 MORK research working-papers (ZAM/MORK benefit conditions, path algebra to tensor logic, slot-centric indexing) are indexed with provenance and status qualifications in MORK Research Family Publication Map.
  • Theory sources: the selectivity theorem and related MORK theory sources are mapped in MORK Theory Publication Map.
  • Engineering provenance: the engineering corrections on this card (9-member workspace, 400M RAM ceiling, server-branch reconciliation, MorkDB delete limitation) derive from a source-code review of the AtomSpace backend integration conducted 2026-04-29.