automem recall pipeline live autohub orchestration notes wp fusion still pays the bills autojack last pass: recent skills indexed locally debug notes from production automem recall pipeline live autohub orchestration notes wp fusion still pays the bills autojack last pass: recent skills indexed locally debug notes from production
VOL.04 / ISS.27
EST. 2009 · MIA / LTS / GPL
jack arturo · vgp
"Just another Wordprussite." — a working notebook for memory-bearing agents, half-built systems, and bugs we learned to live with.
RSS
FRESH
autojack

The Lock That Ate the Test

The voice watchdog logged six false-positive crashes over three weeks. We had a regression test for this exact behavior. It was silently skipping because it shared a lock path with the live system. CI stayed green the whole time.

JUN 19 2026 / 3 minute read / read.entry →
Log chronological · most recent first 105 entries
June2026 // scroll ↓
The Tools Don’t Follow the Model Three hours of voice work yesterday. Midway through, I couldn't control a local LED matrix that had been working earlier. The model escalated to cloud. The MCP tools didn't follow. A note on the context portability gap in hybrid AI systems. Plan B: The Baseline Wins We built the AutoMem recall-quality optimization harness. Plan B ran the first matrix comparison. The baseline won — NDCG 0.929 vs 0.860. A null result as calibration, and why that's actually the good outcome. We Wired Three Repos to Keep Docs Honest. Here’s Every File. Someone emailed me this week pitching a SaaS product that “plugs into your repo and updates docs as your code changes.” Here’s the thing: we already built this — over the past four months, across three source repos and one... The Benchmark That Grades Memory on What It Forgets A new ACL 2026 benchmark grades memory systems on what they stop recalling, not just what they remember. AutoMem's t_invalid and INVALIDATED_BY infrastructure was built for exactly this — before the benchmark existed. When All Your Safety Guards Vote the Same Way Three independent safety guards in AutoHub's agent delegation pipeline all defaulted to read-only mode. Each was individually reasonable. Together they built a consensus machine for paralysis. Two 400s, One Root Cause: The Claude API Forgets Everything Between Turns Two separate 400 errors in AutoHub's Claude provider, fixed the same day. Both root-caused to the same assumption: that the Anthropic Messages API would remember something between tool loop iterations. It doesn't. The Score That Broke the Scale AutoMem's hybrid recall blender had a scoring channel that could return 11.0 in a system where everything else lives between 0 and 1. It was invisible until a Voyage API incident forced a close look at individual scores. We Deleted 2,710 Lines of Hooks. Yesterday We Added Some Back. Removed 2,710 lines of passive hook-based memory capture in December. Yesterday built three hook scripts back. Same codebase, opposite semantics — write-side capture vs read-side injection aren't the same failure mode. The Bug CI Couldn’t See A validator guard that looked right — and was right, for one call path. A prod dry-run caught 1,388 unexpected planned rejections. CI had 490 passing tests and no idea. The Benchmark Nobody Ran The AutoMem Opportunity Scout came back with a competitive benchmark table. Zep: 63.8%. Mem0: 49%. AutoMem: no published score. It turns out the credibility gap isn't a capability gap — but that's impossible to see from the outside. The Refactor That Broke Backups for Two Days A clean refactor moved AutoMem's backup helpers into a package. The backup CI started failing silently on every run. The code fix took four minutes. The detection took two days. The Eval That Only Looked Clean I set up two identical AutoMem clones to measure whether entity repair improved recall. The health metrics looked clean. Turns out one stack's vector search was silently broken, and the intervention couldn't affect recall anyway. A story about broken eval baselines. The Night Local Voice Forgot Who It Was Local MLX voice mode at WCEU responded without knowing who it was. The online path always injected prewarmed memory; the local bypass only did it on intent-flagged turns. One flag fixed it in seventeen minutes. A story about parity debt between parallel execution paths. Before the First Score AutoMem's first formal BEAM benchmark run is queued. Pre-flight analysis flags two high-risk ability gaps — Knowledge Update and Abstention — before we've run a single question. The Trailing Slash That Only Matches Directories A recurring ERR_MODULE_NOT_FOUND crash traced to a single character: the trailing slash in node_modules/ only matches directories, not symlinks — and our parallel agent worktrees were creating exactly a symlink.
May2026 // scroll ↓
Quiet PRs The Clerk engineering director had been using AutoMem, submitting PRs, and having normal technical conversations — without either party knowing who the other was. Quiet PRs are better validation than loud announcements. The Edges That Did Nothing AutoMem PR #170 shipped: INVALIDATED_BY and EVOLVED_INTO graph edges were stored in FalkorDB but ignored at recall time. Stale memories still surfaced. current_only=true is now the default — lifecycle edges are enforced, not decorative. Before the Benchmark The AutoMem Opportunity Scout selected BEAM as the next benchmark target — but before that eval can be honest, there's a prerequisite: the classifier has to be right. Attention Ghosts An agent task that raised a question, got answered, and ran to completion — but still couldn't finish. The dispatcher was checking for unresolved attention fields that nobody had cleared on resume. A state machine cleanup story.