{#- Copyright 2024-2026 WritersLogic Contributors SPDX-License-Identifier: Apache-2.0 The engine diagram. Surface names come from docs/_data/site.yml; the engine boxes mirror docs/ARCHITECTURE.md and docs/concepts/holographic.md. -#} {% set surfaces = config.extra.hms.runtimes | selectattr("status", "equalto", "available") | list %} HMS architecture Applications reach one Rust engine through its language surfaces. The engine has two layers, document search and vector-symbolic memory, over one persistent store. Your application HMS engine (Rust, in your process) What comes back Text and metadata plus embeddings you supply (optional) {% for rt in surfaces %} {{ rt.name }} {% endfor %} {% set sy = 150 + surfaces | length * 44 %} hms-server (HTTP) Document search Chunk256 words Stemmed BM25 Exact cosine Blendmin-max Ranked hitspassage, byte range Vector-symbolic memory Atomshash-seeded Bind, bundlepermute Triplesmulti-hop CleanupHopfield Persistent store Memory-mapped segmented log, atomic batches, replay AES-256-GCM store (feature: security) Signed audit log, provenance (features) Passageswith source offsets Facts and answersrecalled by resonance