Auto-Arch Tournament vs marimo pair

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.

marimo pair is an open-source agent skill that lets AI agents operate directly inside a live marimo notebook session. Rather than editing files from the outside, agents can execute code incrementally, inspect live variables, and manipulate visualizations — the same interactive environment that data scientists already prefer. The system works through a reactive REPL architecture that eliminates hidden state. Because marimo's reactive design enforces deterministic execution order, agents stay on track and produce replayable Python programs instead of the chaotic half-executed notebooks that plague traditional LLM-notebook integrations. It's installed via a single npx command and activated with a one-liner slash command. The core insight is that research is exploratory, not deterministic — and most agent frameworks optimize for software engineering patterns that don't fit data work. marimo pair bridges this gap, enabling things like multi-agent experiment sweeps, paper-to-notebook generation, and collaborative EDA sessions where a human and an agent share the same canvas.