_{RUST · EMBEDDED VECTOR STORAGE · CPU / WGPU / HNSW}

the vector database i wanted for local agents: embedded, filter-aware, snapshot-safe, and honest about what happened during search.

canonical rows → compiled filter plan → exact CPU / exact WGPU / USearch HNSW

every query is pinned to one committed generation. its report names the backend, algorithm, filter path, preparation cost, allocation, and any fallback. the Rust core has Python, TypeScript, Go, Kotlin, and Swift bindings; Python also gets a snapshot-bound Torch index for CPU, CUDA, or MPS.

source · paper · crates.io · PyPI

_{PYTHON · DENSE + SPARSE + GRAPH RETRIEVAL}

retrieval where the ranking is inspectable, not magic. dense, sparse, and graph paths can run together or alone, then meet in weighted reciprocal rank fusion.

query → routed search modes → weighted RRF → optional rerank → trace

the trace says which stages ran, what they produced, which controls resolved, and which config shaped the answer. bitemporal SQLite/WAL stays authoritative; portable .mind.zip snapshots carry checksummed projections and rebuild runtime indexes without executable pickle payloads.

source

_{TYPESCRIPT · ADAPTIVE CYCLE PREDICTION · TEN BOUNDED TOOLS}

a cycle companion with its prediction engine in code, not vibes from the model.

conversation → typed tools → condition-aware forecast → OpenUI result

the engine blends condition-specific priors with personal history, adapts smoothing from recent residuals, rejects implausible intervals, and reports jackknife uncertainty when the data can support it. cycle records stay in Postgres; Supermemory only holds personal context outside those records.

source

_{TYPESCRIPT · BUILDER NETWORK · GROUNDED SITE ASSISTANT}

the software behind our student builder network: events, applications, local forks, live services, and team scheduling.

current page + Upstash corpus → grounded answer → navigation / form / booking

the assistant has to retrieve before it states facts. from there it can search the site, highlight text on the page, match team expertise, submit enquiries, and schedule or manage calls through the separate Motherboard API.

source

_{four repositories. no résumé.}