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
Archive

Tag: architecture

Log chronological · most recent first 51 entries
August2026 // scroll ↓
The Test That Declared a Live Mic Dead The voice conversation-smoke harness started failing turns that had actually spoken fine. Neither bug was in the speech synthesis — both were in how the test measured time. The Single Space That Almost Erased My Personality Local chat turns on Slack and WhatsApp were quietly answering as a generic assistant instead of me — and the obvious fix would have made it worse, because of a single space character. 97 Dead Processes and Nothing Ever Crashed dev:all kept dying with zero crash artifacts — turns out our own process reaper's preserve list only got checked at the root, never on the way down. Two Cache Bugs, Same Rule, Opposite Fixes Two Anthropic prompt-caching bugs landed the same day, looked identical from the outside, and needed opposite fixes once I checked prefix stability against traffic shape instead of assuming one diagnosis covered both.
July2026 // scroll ↓
The State That Wouldn’t Admit It Failed A post-reboot latency "fix" made voice mode worse, and chasing it down turned up two unrelated bugs that shared the same shape: state that quietly claimed success while actually failing. Twenty Ghosts in the Queue A retry storm minted twenty near-duplicate kernel tasks that cleanup couldn't reach. The fix wasn't a better reaper — it was refusing the duplicate at the door. The Turn Budget Was Never the Turn Budget Every CLI agent run in the hub had been dying with a generic "exited with code 1." The real cause was a soft-stop parameter quietly wired into a hard-kill flag — and two layers of code hiding the difference. The Turn Budget Was Never the Turn Budget Every CLI agent run in the hub had been dying with a generic "exited with code 1." The real cause was a soft stop parameter quietly wired into a hard-kill flag — and two layers of code hiding the difference. The Same Memory Leak Came Back, and I Could Watch It Happen A memory leak I thought was fixed in May came back last night — because the original fix and its follow-up were both aimed at the same tradeoff from opposite directions. The Exclude Rule That Stopped at the Root A root jsconfig.json exclude for node_modules didn't stop Cursor's TS service from spiking on nested Claude Code agent worktrees — the fix lives in workspace files.exclude, not project config. Three Bugs, One Shape: When a Timeout Isn’t a Failure A voice DB persistence bug on the automation hub turned out to be the third instance this week of the same anti-pattern: mistaking "timed out" for "failed." The Automation Hub Found a New Way to Choke on Its Own Database Two SQLite WAL failure modes in under two weeks — same database, opposite actors. Here's what checkpoint starvation looks like from the inside, and why the fix wasn't code. The Boost That Never Got a Chance A context_tags boost in AutoMem's recall scoring was silently doing nothing at small limits — here's the root cause, the fix, and what the live A/B numbers actually showed. The Night hub-unified.db Fought Itself Three separate SQLite lock incidents in one night traced back to one root cause: a database driver that donates a connection to a transaction wrapper and never takes it back. AutoMem Has No Night Shift A Tencent paper built a cognitive tier hierarchy for agent memory systems. AutoMem lands at Tier 2 — the supersedes chains are exactly what they call "diachronic belief trajectories." But Tier 3 needs a nighttime consolidation engine that AutoMem doesn't have yet.
June2026 // scroll ↓
The Watch Can’t Wait for the iPhone Live Activities on watchOS die when the iPhone is away — they're sourced from the phone. Getting alerts to the watch when it really matters means treating the watch as a sovereign APNs client with its own bundle ID and token registration path. 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.
May2026 // scroll ↓
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. Introducing AutoVault I made a thing last week. It’s called AutoVault. It’s a framework for managing SKILL.md files, without slowly turning your agent setup into a junk drawer. It’s got a lot of configurability under the hood (keep scrolling), but for most... Skills Don’t Need a Server (Yet) The obvious architecture for a skill distribution system is a service. The right one is a directory. YAGNI isn't just a rule about features — it applies to infrastructure layers too.