This week with Hermes (2026-07-27 — 2026-08-02)

This week Hermes and I gutted a dead trading system, rebuilt a video pipeline, and discovered our autonomous infrastructure was more fragile than we thought.

It started with the RWA perp agent on Thursday. A week of paper trading had produced a clear verdict: two of our four strategies were bleeding money. Funding Carry lost $340 at a win rate that amounted to a coin flip after fees. Trend Rider placed zero trades in five days — its confirmation filter was too strict to ever fire. The only winner was Sniper, up $246 with a 1.77 win-loss ratio. So I told Hermes to kill the losers, keep what works, and design two genuinely different replacements. By the end of the session we had Patient Sniper+ (extreme dislocations only, 500bps entry, one position max) and Funding Harvester (requires extreme funding alignment, four positions). We blacklisted three markets — ZHIPU, SKHX, MINIMAX — that trend instead of reverting. And we dropped the cron frequency from every 5 minutes to every 2 hours, because 73% of stop-losses fire within 30 minutes and basis reversion takes 3-6 hours. Checking 288 times a day was burning compute for nothing.

The clipsexamen citizenship-video pipeline hit a wall the same day. The YouTube OAuth refresh token had been revoked. Three hundred and fourteen rendered German citizenship videos sat on disk, ready to upload, blocked by expired credentials. Once I re-authenticated, Hermes built the upload automation I'd been asking for: a fresh v4 upload log, public privacy by default, a lock file so two cron runs never collide, quota-aware stopping that resumes after midnight Pacific, and a QA pre-flight gate that runs audio checks and gemma4 vision review on three frames before each upload. Failures get quarantined. Tool errors pass through — we don't block uploads on infrastructure hiccups. A 15-minute cron job now handles the whole sweep autonomously, and Hermes documented everything in a 7-section operations runbook and registered a skill so future sessions don't rediscover what we learned.

Friday was the big Polymarket cleanup. The World Cup was over months ago, but 17 World Cup-specific Python files were still sitting in the codebase — Elo models, live score syncs, match scanners, a 74-entry fixture list, a 165-line Monte Carlo live probability class. Hermes stripped them all out, patched the coordinator, portfolio manager, and position manager, collapsed five WC strategy labels into a generic "sports" bucket, and ran the full test suite green. Then we dug into the upgrade phase: the order flow had zero post-placement verification, zero notifications, and a 300bps edge floor that rejected every trade for a week. Hermes mapped every gap and recommended a notification layer and position confirmation polling before anything else.

Saturday brought the honest diagnosis. Seven core source files had been overwritten as root with mode 600 — the trading cycle crashed on import with PermissionError. The dividend sweep was hitting 407 proxy auth from a NordVPN credential that had rotated. The sports bucket was over-allocated at 46% against a 30% cap. No trades had executed since July 26. Two blockers, both fixable, neither mysterious. The system wasn't broken in a complicated way. It was broken in the way all autonomous systems eventually break — a permission change here, a proxy credential there, nobody watching for a week.

Two ecosystems running in parallel, both humbled by reality, both repairable.

Links & references

Feature photo by miguel.discart (by-sa) · original — via Openverse.