EXACT is a lossless HDC strategy: atoms are encoded as one-hot BigInt bits, and a vector is a set of bitset-monomials. It is designed to explore the limits of fully deterministic, collision-free representations inside a session.
Each atom name gets a session-local appearance index i, and the atom vector is one-hot:
A vector is a sorted unique array of monomials, and each monomial is a BigInt bitset of included atoms:
There is no PRNG/hash identity for atoms. If the session sees the same declarations in the same order, atom identity is exact and reproducible. This trades “global name hashing” for a session-owned dictionary.
Lossless superposition: the KB is literally the set of all fact-monomials.
Monomial×monomial uses set-union over atoms (bitwise OR). Polynomial bind is the cross-product:
EXACT does not require UNBIND ≡ BIND. UNBIND extracts residual parts by subset matching:
This aligns with the “KB is a set of facts” model: it finds all facts that contain the query key, then removes the known part.
In XOR-based HDC, unbinding often returns a vector that can be compared directly by similarity. In EXACT, UNBIND is
quotient-like, so its output is a residual that frequently contains structural atoms (e.g., position markers and operator tags).
A raw similarity score can be misleading (e.g., many candidates appear as 0.000).
The EXACT strategy exposes an optional decoder hook (decodeUnboundCandidates()) that maps residual bitsets back to
likely entity atoms by counting witnesses and filtering structural residue. The holographic query engine uses this hook when present,
reducing unnecessary similarity scans and producing interpretable top-k candidates.
EXACT can operate in multiple UNBIND modes. In evaluation runners you may see EXACT(A) (existential quotient: “emit residuals for matches”) and EXACT(B) (residual intersection across component terms, stricter). Both preserve losslessness; they trade speed vs. strictness.