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