Auto-Arch Tournament vs Honker

Auto-Arch Tournament is an autonomous research system where an AI agent iteratively proposes, implements, and validates microarchitectural improvements to a RISC-V CPU. Starting from a standard 5-stage pipeline, the loop runs hypotheses in parallel, each going through formal verification (53 symbolic checks), cycle-accurate simulation, multi-seed FPGA place-and-route, and CoreMark CRC validation. Only hypotheses that beat the current champion get merged; everything else gets discarded. Starting from 301 iterations/second, the system hit 577 iter/s (+92%) across 73 attempts in 9.8 hours — producing a design 26% faster and 40% smaller in LUTs than the baseline. The insight the author drives home is that the real innovation isn't the AI agent — it's the verifier. The orchestrator is hardcoded to prevent agents from manipulating their own evaluation gates, a simple but critical design constraint that turns a creative process into a trustworthy one. Without a rigorous verification harness, agent-driven optimization becomes a confidence trick. This is early but fascinating proof that AI-driven hardware design loops can produce commercially meaningful gains. The repo uses Claude Code or Codex as the coding agent, SystemVerilog for the RTL, and standard open-source EDA tooling (Yosys, nextpnr, Verilator). It's a compelling template for anyone building agentic optimization loops where correctness matters.

Honker is a Rust-built SQLite extension that brings Postgres-style NOTIFY/LISTEN semantics to SQLite without any external broker. It adds cross-process notifications, durable pub/sub channels, task queues with retries and priority, and crontab-style scheduling — all living inside your existing SQLite file. Single-digit millisecond delivery via WAL-file watching instead of polling. The core trick: rather than polling the database on an interval, Honker watches SQLite's Write-Ahead Log (WAL) file with stat(2) calls. When a write lands, listeners wake up immediately. This gives push semantics without Redis, RabbitMQ, or any additional infrastructure. Business logic writes and task enqueues are atomic because they're in the same database. Honker ships as a loadable SQLite extension plus language packages for Python, Node.js, Rust, Go, Ruby, Bun, Elixir, and C++. It's experimental and the API may change, but it's addressing a real pain point: SQLite projects that outgrow simple reads/writes inevitably reach for external messaging, and Honker defers that moment significantly.