HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
vac-architector
VAC-Memory-System
Python2025–2026
vac-architector / VAC-Memory-System

VAC-Memory-System

From cell-tower climber & handyman to AI Architect in 4.5 months via Claude CLI. Built VAC Memory System: SOTA RAG (80.1% LoCoMo) on gpt-4o-mini. Proprietary MCA ranking, <$0.10/M cost, 100% isolation. Open to partnerships.

3Distinct people
12Mentions
0Explicit recommenders
33GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

From cell-tower climber & handyman to AI Architect in 4.5 months via Claude CLI. Built VAC Memory System: SOTA RAG (80.1% LoCoMo) on gpt-4o-mini. Proprietary MCA ranking, <$0.10/M cost, 100% isolation. Open to partnerships.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 11:34:28 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week12 dated mentions

Observed mentions: 2025-11-24 16:43:22 UTC to 2026-01-04 01:18:45 UTC. Weeks start Monday, UTC.

02462025-11-24 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 6 mentions; 5 submissions, 1 commentsNov 242025-12-01 00:00:00 UTC to 2025-12-08 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 comments2025-12-08 00:00:00 UTC to 2025-12-15 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsDec 82025-12-15 00:00:00 UTC to 2025-12-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-22 00:00:00 UTC to 2025-12-29 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2025-12-29 00:00:00 UTC to 2026-01-05 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsDec 29

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Nov 242025-11-24 00:00:00 UTC2025-12-01 00:00:00 UTC651
Dec 12025-12-01 00:00:00 UTC2025-12-08 00:00:00 UTC220
Dec 82025-12-08 00:00:00 UTC2025-12-15 00:00:00 UTC110
Dec 152025-12-15 00:00:00 UTC2025-12-22 00:00:00 UTC000
Dec 222025-12-22 00:00:00 UTC2025-12-29 00:00:00 UTC110
Dec 292025-12-29 00:00:00 UTC2026-01-05 00:00:00 UTC211

What Hacker News says

1 sources
ViktorKuz·Dec 23, 2025Submission

80.1 % on LoCoMo Long-Term Memory Benchmark with a pure open-source RAG pipeline

I just pushed the current SOTA on the LoCoMo long-term memory benchmark for agents: 80.1 % accuracy using only: -BGE-large-en-v1.5 (1024d) + FAISS -Custom “MCA” gravitational ranking (keyword coverage + importance + frequency) -BM25 sparse retrieval -Direct Cross-Encoder reranking (bge-reranker-v2-m3) on the full union (~120-150 docs) -Gpt-4o-mini only for final answer generation and judging (everything else is open weights or classic) Repo: https://github.com/vac-architector/VAC-Memory-System Key tricks that finally broke 80% : -MCA-first filter (coverage ≥ 0.1 → top-30) — catches exact-keyword questions early -Feeding the entire union straight into Cross-Encoder (112–135 documents) instead of pre-filtering -Proper query instruction for BGE-large (the classic “Represent this sentence for searching relevant passages”) The whole pipeline r
Read the rest
uns in < 3s per query on a single RTX 4090. LoCoMo is currently the hardest public long-term memory benchmark (5.880 real human–agent conversations, multi-hop, temporal, negation, etc.). Beating Mem0 official baseline by ~12–14 pp with fully open components feels pretty good. Would love feedback, especially from people who are also grinding on agent memory systems. My background: My path didn't start in an IT office, but in Columbus, Ohio, where I worked as a handyman after leaving my job on the cell towers. The decision came from necessity: I bought a powerful PC on installments and resolved to create something that would change my life. I had no experience, but I had an idea. Using Claude CLI as my sole mentor, I focused on architecture, not syntax. Over 4.5 months of work, I engineered and created the VAC Memory System. To prove its value, I tested it on the toughest RAG benchmark—LoCoMo. Today, my system shows an overall result of 80.1% and a phenomenal 87.78% in the "Commonsense" category. This is more than just code; it is the result of faith in an idea. I showed that by using modern tools, it is possible to achieve SOTA-level performance and create serious technology, regardless of your starting point. I highly anticipate your feedback.
1 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.