goverComposable governance CLI for Go projects

Version determination, release notes, cross-compilation, pre-publish staging, dev-state sync. For single-module and multi-module projects. No YAML DSL. No monolithic pipeline. Unix-way subcommands, structured stdout, every step replaceable.

Getting Started

Reference

GitHub

🚧

Work In Progress

Architecture under active RFC development — stress-tested through adversarial review. Previously multimod — renamed to gover after scope expansion.

Read the RFC →

🔍

Zero Configuration

Directory structure is the config. A go.mod in a subdirectory = a sub-module. No YAML, no TOML, no config files. Discovery is automatic, deterministic, and auditable.

🔄

Always Synced

Every invocation guarantees the filesystem matches the desired state. go.work, replace directives, go version alignment — all synced. You cannot forget. You cannot drift.

🏷️

Staging Before Point of No Return

Go Module Proxy caches forever. --write creates staging worktree with publish-state. Check before you push. --push ships. --abort rolls back. Go's missing npm pack.

How it works →

🔗

Composable Subcommands

gover bump | gover release | gover build | gover notes | gh release create. Each does one thing. Any replaceable with svu, git-cliff, goreleaser, or a shell script.

See the design →

📦

Works For All Go Projects

Library? bump + release + notes. CLI tool? Add build. Multi-module? Add dev-state sync. Single-module is first-class, not degraded mode.

Three project types →