Show HN: Turbo Flow v5.2

Adventure Wave Labs, led by Marcus Patman, released Turbo Flow v5.2 in October 2026, stripping the project's orchestration stack entirely so that Turbo Flow v5 is now only the rules layer, rig-lite, a bash-only governance kit for AI-written code. Earlier versions (1–4, 2025–2026) had packaged an agentic development environment around Claude Code and Ruflo with 215+ MCP tools and 60+ agents; the September 2026 pivot to a thinner governed approach removed that stack, and the integrated successor, Turbo Rig, runs in private beta. rig-lite ships a fail-closed cross-model review gate, a written constitution and git-versioned memory, installs nothing, and is demonstrated in a clean Codespace via a reproducible self-test suite and live gate run with the reviewer CLI stubbed.

v5.2 · THE RULES LAYER · OUT NOWv5.2 · LA CAPA DE REGLAS · DISPONIBLE YA TURBO FLOW Agents build. Humans merge.Los agentes construyen. Los humanos fusionan. One product lives here: rig-lite https://www.turboflow.online/rig-lite/ — the rules layer for AI-written code. A portable governance kit: a fail-closed cross-model review gate https://www.turboflow.online/cross-model-code-review/ , a written constitution, git-versioned memory. It ships no harness, installs nothing, and depends only on bash — drop it into any repo and your agents get laws with teeth. Un producto vive aquí: rig-lite https://www.turboflow.online/rig-lite/ — la capa de reglas para código escrito por IA. Un kit portátil de gobernanza: una compuerta de revisión entre modelos https://www.turboflow.online/cross-model-code-review/ que falla cerrada, una constitución escrita, memoria versionada en git. No trae harness, no instala nada, solo depende de bash — agrégalo a cualquier repo y tus agentes tienen reglas con dientes. The whole story, in one paragraph: Turbo Flow is an open-source project by Adventure Wave Labs https://www.adventurewavelabs.space/ Marcus Patman . Versions 1–4 2025–2026 packaged an agentic development environment around Claude Code and Ruflo — at its peak, 215+ MCP tools and 60+ agents. In September 2026 the project pivoted to a thinner, governed approach, and by v5.2 October 2026 the orchestration stack was fully removed: Turbo Flow v5 is now the rules layer rig-lite , and the integrated successor, Turbo Rig https://www.turboflow.online/turbo-flow-vs-turbo-rig/ , runs in private beta. The v4 era stays fully recoverable in the version tags https://www.turboflow.online/versions/ ; the full reasoning lives in why Turbo Flow became Turbo Rig https://www.turboflow.online/why-turbo-flow-became-turbo-rig/ . Toda la historia, en un párrafo: Turbo Flow es un proyecto open source de Adventure Wave Labs https://www.adventurewavelabs.space/ Marcus Patman . Las versiones 1–4 2025–2026 empaquetaban un entorno de desarrollo agéntico alrededor de Claude Code y Ruflo — en su punto más alto, 215+ herramientas MCP y 60+ agentes. En septiembre de 2026 el proyecto pivotó a un enfoque más delgado y gobernado, y para la v5.2 octubre de 2026 el stack de orquestación se eliminó por completo: Turbo Flow v5 es ahora la capa de reglas rig-lite , y el sucesor integrado, Turbo Rig https://www.turboflow.online/turbo-flow-vs-turbo-rig/ , corre en beta privada. La era v4 sigue recuperable en los tags de versiones https://www.turboflow.online/versions/ ; el razonamiento completo vive en por qué Turbo Flow se convirtió en Turbo Rig https://www.turboflow.online/why-turbo-flow-became-turbo-rig/ . ★ Star on GitHub★ Estrella en GitHub https://github.com/marcuspat/turbo-flow ▸ Open in a Codespace▸ Abrir en un Codespace https://github.com/codespaces/new?repo=marcuspat/turbo-flow ▸ Join the private beta▸ Únete a la beta privada https://turbo-rig-beta.vercel.app The real thing, not a mockup: a clean Codespace boots this repo's devcontainer and the kit proves itself in-container — the fail-closed self-test suite and a live gate run reviewer CLI stubbed; no API keys on the recording box . Reproducible via demo/record-rig-lite-demo.sh https://github.com/marcuspat/turbo-flow/blob/main/demo/record-rig-lite-demo.sh . La cosa real, no un mockup: un Codespace limpio arranca el devcontainer de este repo y el kit se demuestra dentro del contenedor — la suite de self-tests que falla cerrada y una corrida en vivo de la compuerta CLI revisor simulado; sin API keys en la máquina de grabación . Reproducible con demo/record-rig-lite-demo.sh https://github.com/marcuspat/turbo-flow/blob/main/demo/record-rig-lite-demo.sh . The daily driver: tf help shows every subcommand, tf status the at-a-glance view repo, gate verdict counts, tree health , tf gate fails closed without --builder , tf tokens the live dashboard, tf test the full suite. tf is installed automatically by the Codespace boot and by init-repo.sh . El comando del día a día: tf help muestra todos los subcomandos, tf status la vista de un vistazo repo, conteo de veredictos del gate, salud del árbol , tf gate falla cerrado sin --builder , tf tokens el tablero en vivo, tf test la suite completa. tf se instala automáticamente con el arranque del Codespace y con init-repo.sh . A fresh Codespace from main unauthenticated : the first shell triggers the boot — no menu, that's the point — Claude Code + Codex + Ruflo install visibly , then tmux fires with all 5 windows, each one landing inside its harness. The reviewer is whichever window has a different model family than the builder — cross-family review is the kit's law. Un Codespace nuevo desde main sin autenticar : el primer shell dispara el arranque — sin menú, ese es el punto — Claude Code + Codex + Ruflo se instalan a la vista , y tmux arranca con las 5 ventanas, cada una aterrizando dentro de su harness. El revisor es la ventana con una familia de modelos distinta a la del constructor — la revisión cruzada es la ley del kit. the evidence https://www.turboflow.online/cross-model-code-review/ veredictos REVISE 79%, gate activo del 16 al 21 — 141 PRs igualmente fusionados · la evidencia https://www.turboflow.online/cross-model-code-review/ v1.0.1 → v4.0 tags https://www.turboflow.online/versions/ archivos en el lean pivot v5.2 — la era v4 sigue recuperable en los tags v1.0.1 → v4.0 https://www.turboflow.online/versions/ inside the rig https://www.turboflow.online/research/ PRs fusionados · veredictos de la compuerta en una ventana de siete días 79% REVISE — dentro del rig https://www.turboflow.online/research/ Three doors — pick yoursTres puertas — elige la tuya rig-lite, standalonerig-lite, independiente Your agents have hundreds of tools. Nothing says no . Drop in gate.sh cross-model review , the constitution template, and the memory pattern — works in any repo, zero dependencies, self-test suite included. Tus agentes tienen cientos de herramientas. Nada dice no . Agrega gate.sh revisión entre modelos , la plantilla de constitución, y el patrón de memoria — funciona en cualquier repo, cero dependencias, suite de self-tests incluida. /rig-lite/ → https://www.turboflow.online/rig-lite/ Why it became Turbo RigPor qué se convirtió en Turbo Rig 215+ tools and 60+ agents — then almost all of it was deleted. What orchestration couldn't solve, governance did. The full version history https://www.turboflow.online/versions/ , the reasoning https://www.turboflow.online/why-turbo-flow-became-turbo-rig/ , and the research behind it https://www.turboflow.online/research/ . 215+ herramientas y 60+ agentes — y luego casi todo se borró. Lo que la orquestación no pudo resolver, lo resolvió la gobernanza. La historia completa de versiones https://www.turboflow.online/versions/ , el razonamiento https://www.turboflow.online/why-turbo-flow-became-turbo-rig/ , y la investigación detrás https://www.turboflow.online/research/ . the essay → https://www.turboflow.online/why-turbo-flow-became-turbo-rig/ Turbo Rig — private betaTurbo Rig — beta privada The kit as one always-on system: integrated gate, constitution, git-versioned memory, automations across your repos — the successor Turbo Flow is becoming. See exactly how it differs → https://www.turboflow.online/turbo-flow-vs-turbo-rig/ El kit como un solo sistema siempre activo: compuerta integrada, constitución, memoria versionada en git, automatizaciones entre tus repos — el sucesor en el que Turbo Flow se convierte. Mira exactamente en qué difiere → https://www.turboflow.online/turbo-flow-vs-turbo-rig/ Request access →Solicitar acceso → https://turbo-rig-beta.vercel.app 1 · onboard the repo writes a thin AGENTS.md, never clobbers bash /path/to/turbo-flow/rig-lite/init-repo.sh 2 · prove the kit on your machine fail-closed self-tests bash /path/to/turbo-flow/rig-lite/self-test.sh 3 · gate your first PR — builder = whichever CLI built it /path/to/turbo-flow/rig-lite/gate.sh --pr 1 --builder zcode want the 30-second container tour? open the repo in a Codespace — postCreate runs the self-test. that's the whole install surface. Go deeper — every page, one questionProfundiza — cada página, una pregunta The kit https://www.turboflow.online/rig-lite/ · Does cross-model review work? https://www.turboflow.online/cross-model-code-review/ · Agents build, humans merge https://www.turboflow.online/agents-build-humans-merge/ · The AGENTS.md template https://www.turboflow.online/agents-md/ · Is there an extension? https://www.turboflow.online/turboflow-extension/ · Agentic vs vibe coding https://www.turboflow.online/agentic-coding-vs-vibe-coding/ · What is an agentic development environment? https://www.turboflow.online/agentic-development-environment/ · Orchestration vs governance https://www.turboflow.online/agent-orchestration-vs-governance/ · Why Turbo Flow became Turbo Rig https://www.turboflow.online/why-turbo-flow-became-turbo-rig/ · Turbo Flow vs Turbo Rig https://www.turboflow.online/turbo-flow-vs-turbo-rig/ · Version history https://www.turboflow.online/versions/ · Research https://www.turboflow.online/research/ El kit https://www.turboflow.online/rig-lite/ · ¿Funciona la revisión entre modelos? https://www.turboflow.online/cross-model-code-review/ · Los agentes construyen, los humanos fusionan https://www.turboflow.online/agents-build-humans-merge/ · La plantilla AGENTS.md https://www.turboflow.online/agents-md/ · ¿Hay extensión? https://www.turboflow.online/turboflow-extension/ · Codificación agéntica vs vibe coding https://www.turboflow.online/agentic-coding-vs-vibe-coding/ · ¿Qué es un entorno de desarrollo agéntico? https://www.turboflow.online/agentic-development-environment/ · Orquestación vs gobernanza https://www.turboflow.online/agent-orchestration-vs-governance/ · Por qué Turbo Flow se convirtió en Turbo Rig https://www.turboflow.online/why-turbo-flow-became-turbo-rig/ · Turbo Flow vs Turbo Rig https://www.turboflow.online/turbo-flow-vs-turbo-rig/ · Historia de versiones https://www.turboflow.online/versions/ · Investigación https://www.turboflow.online/research/