Practical overview
When it fits
Use Turbo Flow when an agentic coding workflow needs a documented environment, portable governance controls or evidence-oriented repository automation. Choose rig-lite for a standalone governance layer; choose the v4 path for the documented Codespace-oriented environment.
Who it is for
- Developers using agentic coding workflows
- Teams governing AI-written code
- Engineers building containerized or self-hosted developer tooling
- Users needing repository evidence, review gates or workflow automation
Documented uses
- Set up the documented Turbo Flow v4 development environment
- Add governance rules and review gates to an existing coding-agent installation
- Isolate parallel coding work with Git worktrees
- Collect repository health and coding-workflow evidence
- Adapt the project’s agentic coding rig concept into a self-hosted developer tool
Requirements & limits
The repository is publicly visible and specifies an MIT license.
- Whether you need the v4 environment or the standalone rig-lite governance kit
- Whether cross-model review and fail-closed behavior fit your workflow
- Whether isolated worktrees, repository-health reporting and scheduled automation are useful
- Whether you can work within the documented limits of the available setup evidence
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Add rig-lite governance to an existing repository
Set up the documented portable governance layer for an existing coding workflow.
Before you start
- A repository or development environment where the rig-lite files can be added.
- The Turbo Flow repository at https://github.com/marcuspat/turbo-flow.
Steps
Use the rig-lite directory as the portable governance kit.
Add the documented constitution, memory pattern, specification templates and automation pack as needed.
Use init-repo.sh for the documented repository onboarding files without clobbering existing files.
Run self-test.sh before relying on the kit's fail-closed behavior.
Expected outcome
The repository has the documented governance materials, onboarding pattern and self-test path available for its coding workflow.
Guide limitations
- Source-based guidance is not human verification.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 30 September 2026
- Original website title
- marcuspat/turbo-flow · Official homepage title · retained in its source language

