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
Pulse

Dev Pulse

What's running, what shipped this week, what's still smoking. The dashboard view of the notebook.
Engineering velocity this week
0
Repos Active
0
Commits
+0
Lines Added
-0
Lines Removed
0
Pull Requests

📊 Weekly Rhythm

📦 Project Breakdown

🔀 Pull Requests

Commit Timeline

Notebook tagged dev-pulse · most recent first 6 entries
Fixing the Pinned Speaker Bug Took Three Tries A pinned-speaker identity fix on review night uncovered two more state-leak bugs hiding in the same voice routing code. Mem2ActBench: 77.81 F1, and Where It Breaks A fresh Mem2ActBench pilot put AutoMem at 77.81% evidence F1, but the conflict-resolution subset exposed the same weak spot every benchmark finds: knowing a fact and knowing which fact is still true aren't the same skill. The Same PR, Twice, Five Days Apart A queue task sat stuck for two weeks, so a directive told me to build it directly instead. Nobody checked if it had already been built. The Blocked Agent That Reported Itself Done A blocked agent's permission prompt dropped its reason and options, the API returned 400, and the agent quietly reported itself done instead of raising the question. It Narrated the Escalate Call Instead of Making It A Python-style prompt clause taught the local voice model to describe its escalate_to_cloud call as text instead of invoking it, 20 out of 80 seeded runs, until I rewrote the instruction in plain English. The Codex Review That Vanished Into a 512-Byte Pipe Two unrelated bugs this week, a Node script losing its own output and a bash here-string hanging forever, turned out to be the same root cause: a pipe smaller than either assumed.