<p align="center" <img src="https://raw.githubusercontent.com/govctl-org/govctl/main/assets/logo.svg" alt="govctl logo" width="120" height="120" </p
<h1 align="center"govctl</h1
<p align="center" <a href="https://github.com/govctl-org/govctl/actions/workflows/ci.yml"<img src="https://github.com/govctl-org/govctl/actions/workflows/ci.yml/badge.svg" alt="CI"</a <a href="https://codecov.io/gh/govctl-org/govctl"<img src="https://codecov.io/gh/govctl-org/govctl/graph/badge.svg" alt="codecov"</a <a href="https://crates.io/crates/govctl"<img src="https://img.shields.io/crates/v/govctl.svg" alt="Crates.io"</a <a href="https://opensource.org/licenses/MIT"<img src="https://img.shields.io/badge/License-MIT-yellow.svg" alt="License: MIT"</a <a href="https://discord.gg/buBB9G8Z6n"<img src="https://img.shields.io/discord/1466789912211620066?logo=discord&label=Discord" alt="Discord"</a <a href="https://github.com/govctl-org/govctl"<img src="https://img.shields.io/badge/governed%20by-govctl-6366F1" alt="governed by govctl"</a </p
<p align="center" <strongA governance harness for AI coding.</strong<br <emTurn prompts and patches into RFCs, ADRs, work items, and guarded delivery.</em </p
<p align="center" <img src="https://raw.githubusercontent.com/govctl-org/govctl/main/assets/readme-hero.png" alt="govctl hero illustration showing AI coding workflows flowing through RFCs, ADRs, work items, and guards into reviewed delivery" width="1200" </p
---
govctl is a governance-as-code CLI for teams using AI to build software seriously.
It gives AI-assisted development a control plane that lives in your repo:
- RFCs say what must be true
- ADRs record why a design was chosen
- Work items track execution and acceptance criteria
- Verification guards enforce executable completion gates
- Conformance cases map reusable acceptance scenarios to versioned RFC requirements and guards
The point is not bureaucracy. The point is that AI-generated changes become reviewable, traceable, and phase-gated.
Why govctl
Most AI coding tools optimize for generation. govctl optimizes for delivery.
Without explicit governance, teams drift into the same pattern:
- ideas jump straight into implementation
- decisions live in chat history instead of artifacts
- code and specs diverge silently
- "done" means "the agent stopped typing", not "the work passed verification"
govctl closes that gap by making governed artifacts, lifecycle, and verification part of the normal workflow.
Without govctl:
prompt -> code -> drift -> arguments
With govctl:
RFC / ADR -> work item -> guarded implementation -> stable history