Overview Playground Games Pricing Dashboard Sign in
Results 0 matches
    Nodes visited
    0
    Query time
    0ms
    Recall
    100%
    vs brute
    0×
    Traversal Mirror Trie · Radix-2 · 16-bit
    Exact descent Mirror branch Multi-probe Hit
    What you're seeing

    Every word in the dataset is hashed to 16 bits and inserted as a path through a binary trie. Your query gets the same treatment. The engine descends bit-by-bit. When it can't match, it mirrors. When the error budget runs out, it returns.

    Why multi-probe

    Mirror-only exploration has blind spots at high distance. Multi-probe re-runs the search with each of the top bits flipped independently and unions the results. Recall jumps from ~48% to 99.8%.

    What's different in production

    The real engine uses 64-bit hashes, arena allocation, SIMD batch probes, and a Rust core compiled with LTO. Client-side demo here uses 16-bit for clarity and is single-pass.