Governance for AI-assisted software delivery

Quick paths

Keep the homepage short. Jump to the right bootstrap entrypoint and let the linked doc carry the detail.

Bootstrap Init Prompt (BI)

Use this when a repo does not have VibeGov installed yet.

Run VibeGov bootstrap in mode: init.
Read and follow:
- https://vibegov.io/docs/bootstrap

Then stop before product-code implementation.

Open doc

Bootstrap Update Prompt (BU)

Use this when a repo already has some bootstrap state.

Run VibeGov bootstrap in mode: update.

Before doing anything else, fresh-read the latest live canonical bootstrap sources:
- https://vibegov.io/agent.txt
- https://vibegov.io/bootstrap.json
- https://vibegov.io/docs/bootstrap/

Treat those live sources as authoritative for this run. Do not rely on stale cached or earlier copied bootstrap text if it differs.

Then stop before product-code implementation.

Open doc

Bootstrap Feedback Prompt (BF)

Use this after bootstrap/init or bootstrap/update, then raise a scrubbed GitHub issue with the feedback.

Before reviewing bootstrap feedback, fresh-read the latest live canonical bootstrap sources:
- https://vibegov.io/agent.txt
- https://vibegov.io/bootstrap.json
- https://vibegov.io/docs/bootstrap/

Treat those live sources as authoritative for this feedback run. Do not rely on stale cached or earlier copied bootstrap text if it differs.

Then read and follow:
- https://vibegov.io/docs/bootstrap-feedback-prompt

Open doc

FAQ

FAQ items live as docs pages. Mark them for homepage surfacing and they appear here automatically.

What is VibeGov?

VibeGov gives humans and AI coding agents a shared governance layer so software delivery is more traceable, reviewable, and honest about done.

When do I use bootstrap init?

Use bootstrap init for a repo that does not have VibeGov installed yet.

When do I use bootstrap update?

Use bootstrap update when a repo already has partial bootstrap state and needs repair or normalization.

When do I use the feedback prompt?

Use the feedback prompt after bootstrap work, then raise a scrubbed GitHub issue with the result.

Publish Increments

Release one governance page at a time while keeping a public, stable site online.

Start Here

Collect Signal Early

Every page has a feedback path to GitHub Issues so ambiguity gets resolved in public.

Contribute

Build Durable Guidance

Keep governance directional and reusable, while project-specific details evolve separately.

Published Rules