Skip to main content

Start Here

If you are new to VibeGov, start here.

VibeGov is a repo-local governance framework for AI-assisted software delivery. This page is the shortest path to the smallest useful adoption step.

Who VibeGov is for​

VibeGov is for teams and solo developers using AI coding agents on real repositories where delivery state needs to remain inspectable after the chat scrolls away.

It is strongest for:

  • teams using AI coding agents on production-bound or maintained software
  • solo developers who want agent speed without losing traceability
  • technical founders and consultants coordinating multiple AI-assisted delivery threads
  • maintainers who want issue, spec, and evidence discipline without heavyweight process tooling
  • teams building agent harnesses that need repo-local operating rules

It is probably overkill for:

  • throwaway scripts with no maintenance horizon
  • teams that do not want evidence before completion claims
  • projects that do not care about traceability, backlog quality, or long-term change safety
  • users looking for a hosted SaaS or magical autonomous runtime

If you already know the job you want done, use Choose Your Path for a compact route to install, review, feedback intake, delivery, PR readiness, role-pack use, or messy-repo hardening.

First: know the authority level​

VibeGov has canonical contracts, published rules, operational guides, role packs, runtime profiles, and commentary.

If you are deciding what an agent or repo must obey, check the Content Status Model before treating a supporting guide, role pack, runtime profile, or blog post as the current contract.

First: what are you trying to do?​

1. I want the fastest explanation of what VibeGov is​

Read:

2. I want to install or bootstrap VibeGov in a repo​

Read:

3. I want to understand how work is supposed to run​

Read:

4. I want the shortest practical operating guide​

Read:

5. I want to understand the deeper governance model​

Read:

The smallest useful adoption path​

If you only want the minimum useful path, do this:

  1. read Overview
  2. read Execution Modes
  3. read Checkpoint Reporting
  4. run Quick Start when you are ready to bootstrap a repo

That is enough to understand the basic shape:

  • choose the right mode
  • keep evidence honest
  • report clearly
  • bootstrap governance before trying to scale the workflow

If a term is unclear while reading, keep the Glossary open beside the deeper docs.

What VibeGov is not​

VibeGov is not:

  • a magical agent runtime
  • a provider-specific tool wrapper
  • a replacement for engineering judgment
  • a license to add process everywhere

It is a repo-local governance framework that helps teams run AI-assisted delivery more legibly and more reliably.

For a practical category comparison, read VibeGov vs Agent Rules, Prompts, and Frameworks.

If you are still unsure​

Use this shortcut: