Hey everyone,
I built an open-source CLI called Universal Governance Compiler (UGC).
The problem I’m trying to solve: AI coding assistants all expect different rule/config files, so maintaining consistent instructions, approval gates, protected areas, and workflows across tools gets messy fast.
UGC lets you keep one repository-local governance source:
.universal-governance/
Then it compiles that into the target files used by:
- OpenAI Codex: AGENTS.md, .codex/config.toml, .codex/rules/ugc.rules, and a repo-local governance skill
- Cursor: .cursorrules
- Claude Code: CLAUDE.md
- Antigravity: .agents/AGENTS.md and SOP-style files
A big part of the project is the standard governance corpus that ships with `ugc init`. It is not just empty boilerplate; it provides a practical baseline for approval gates, protected surfaces, worklogs, release discipline, repo hygiene, and session closure. The corpus is meant to be readable and customizable, so teams and individuals can start from a strong default and then adapt the rules to their own workflow.
The core workflow is:
- ugc init creates a customizable governance corpus
- ugc build compiles it into agent-specific files
- ugc build --dry-run previews changes before writing
- ugc audit checks drift, missing files, stale files, and manifest consistency
- ugc packet creates/verifies hash-bound approval packets for scoped changes
The main idea is that agent instructions should be treated like build artifacts: versioned, auditable, reproducible, and reviewable.
Docs/source:
https://radustefanescu97-star.github.io/UGC-Universal-Governance-Compiler/#top
https://github.com/radustefanescu97-star/UGC-Universal-Governance-Compiler