Govctl
A governance harness for AI coding.
Last verified:
What is Govctl?
govctl is an opinionated CLI tool for RFC-driven software development that enforces phase discipline on AI-assisted coding. It provides a governance-as-code CLI for teams using AI to build software seriously, giving AI-assisted development a control plane that lives in your repo. The tool enforces a strict lifecycle: spec → impl → test → stable, where phases cannot be skipped and gates are checked, not suggested.
govctl manages three artifact types: RFCs (Requests for Comments) which are normative specifications that must exist before implementation, ADRs (Architectural Decision Records) documenting architectural decisions with explicit consequences, and Work Items which are tracked tasks tied to governance artifacts. All documents are stored as structured data (JSON/TOML) in the gov/ directory and rendered to human-readable Markdown with SHA-256 signatures for tampering detection.
The tool is designed for teams frustrated by AI
Govctl pricing
Pricing model: Freemium
govctl is free and open source under MIT license. Install via cargo: 'cargo install govctl' or with TUI dashboard: 'cargo install govctl --features tui'. No paid tiers or subscription plans mentioned.
Govctl pros
- Enforces phase discipline so phases cannot be skipped
- RFC is the single source of truth—no implementation without specification
- Governance is executable—rules are checked, not suggested
- Work is traceable—tasks link back to specs that authorized them
- Creates audit trails for AI-generated code
- Prevents spec drift from implementation
- AI-native with embedded Claude commands for governed workflow
- CLI is universal interface—all AI coding agents speak shell
- Optional TUI dashboard for visual governance monitoring
- Written in Rust for correctness and speed
- MIT licensed and open source
- Dogfooding proves the model works—tool governs itself
- Structured data storage (JSON/TOML) ensures machine readability
- SHA-256 signatures detect document tampering
- Constrained autonomous AI agents that respect governance rules
- Force thinking through edge cases before coding begins
- Gives reviewers something to review before thousands of lines exist
Govctl cons
- Not for
- workflows
- Not for projects without review processes
- Not a code generator—doesn't write code itself
- Not a documentation editor—enforces structure not style
- Not about faster coding—focused on correct coding
- Not a framework—it is a constraint system
- Not a general issue tracker—doesn't replace Jira
- Opinionated approach may feel restrictive to some teams
- Requires discipline and process change to adopt
- Learning curve for RFC/ADR/work item workflow
Frequently asked questions about Govctl
What is govctl?
govctl is an opinionated governance CLI for RFC-driven AI-assisted software development. It enforces phase discipline on software development with a lifecycle of spec → impl → test → stable where phases cannot be skipped and gates are checked, not suggested.
What artifact types does govctl manage?
govctl manages three artifact types: RFCs (normative specifications that must exist before implementation), ADRs (Architectural Decision Records documenting why decisions were made with explicit consequences), and Work Items (tracked tasks tied to governance artifacts with acceptance criteria).
How do I install govctl?
Install govctl using Cargo: 'cargo install govctl' for the basic CLI, or 'cargo install govctl --features tui' to include the optional TUI dashboard. Then initialize your project with 'govctl init'.
Why is govctl a CLI instead of a web app or IDE extension?
Every AI coding agent already speaks shell. Claude, Cursor, Codex, Copilot can all run commands. The CLI is the universal interface requiring no JSON-RPC negotiation or custom protocols, avoiding complexity while preserving capability.
What is the embedded Claude command feature?
govctl ships with a built-in Claude command accessible via '/gov add user authentication' or '/gov implement caching with Redis'. This teaches AI agents the complete governed workflow including creating RFCs with proper clauses, asking permission before advancing phases, implementing features, running tests, and marking work items done.
Where are governance artifacts stored?
All governance artifacts have a Single Source of Truth (SSOT) in the gov/ directory containing config.toml, rfc/ folder with RFC-NNNN/rfc.json and clauses/, adr/ folder with ADR-NNNN-.toml files, and work/ folder with WI-YYYY-MM-DD-NNN-.toml files. Markdown files are rendered projections generated by 'govctl render'.
Does govctl write code?
No, govctl is not a code generator. It doesn't write code; it ensures code follows specs. It is a constraint system that enforces governance, not a framework or documentation editor.
How does govctl prove its model works?
govctl dogfoods its own governance—every feature in the CLI was specified in an RFC before any code was written. RFC-0000 defines the Governance Framework and RFC-0001 defines Lifecycle State Machines. You can trace any line of code back to its specification, proving the model works.