LWlwhsiao·Feb 5, 2026Submission
CLI tool to enforce RFC-driven AI coding
2 points · Open discussiongovctl-org
govctl
Rust2026–2026
govctl-org / govctl
govctl
A governance harness for AI coding.
2Distinct people
2Mentions
0Explicit recommenders
277GitHub stars
What to know before exploring
What it is
A governance harness for AI coding.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by day2 dated mentions
Observed mentions: 2026-01-17 21:51:36 UTC to 2026-02-05 12:05:18 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Jan 17 | 2026-01-17 00:00:00 UTC | 2026-01-18 00:00:00 UTC | 1 | 1 | 0 |
| Jan 18 | 2026-01-18 00:00:00 UTC | 2026-01-19 00:00:00 UTC | 0 | 0 | 0 |
| Jan 19 | 2026-01-19 00:00:00 UTC | 2026-01-20 00:00:00 UTC | 0 | 0 | 0 |
| Jan 20 | 2026-01-20 00:00:00 UTC | 2026-01-21 00:00:00 UTC | 0 | 0 | 0 |
| Jan 21 | 2026-01-21 00:00:00 UTC | 2026-01-22 00:00:00 UTC | 0 | 0 | 0 |
| Jan 22 | 2026-01-22 00:00:00 UTC | 2026-01-23 00:00:00 UTC | 0 | 0 | 0 |
| Jan 23 | 2026-01-23 00:00:00 UTC | 2026-01-24 00:00:00 UTC | 0 | 0 | 0 |
| Jan 24 | 2026-01-24 00:00:00 UTC | 2026-01-25 00:00:00 UTC | 0 | 0 | 0 |
| Jan 25 | 2026-01-25 00:00:00 UTC | 2026-01-26 00:00:00 UTC | 0 | 0 | 0 |
| Jan 26 | 2026-01-26 00:00:00 UTC | 2026-01-27 00:00:00 UTC | 0 | 0 | 0 |
| Jan 27 | 2026-01-27 00:00:00 UTC | 2026-01-28 00:00:00 UTC | 0 | 0 | 0 |
| Jan 28 | 2026-01-28 00:00:00 UTC | 2026-01-29 00:00:00 UTC | 0 | 0 | 0 |
| Jan 29 | 2026-01-29 00:00:00 UTC | 2026-01-30 00:00:00 UTC | 0 | 0 | 0 |
| Jan 30 | 2026-01-30 00:00:00 UTC | 2026-01-31 00:00:00 UTC | 0 | 0 | 0 |
| Jan 31 | 2026-01-31 00:00:00 UTC | 2026-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 1 | 2026-02-01 00:00:00 UTC | 2026-02-02 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2 | 2026-02-02 00:00:00 UTC | 2026-02-03 00:00:00 UTC | 0 | 0 | 0 |
| Feb 3 | 2026-02-03 00:00:00 UTC | 2026-02-04 00:00:00 UTC | 0 | 0 | 0 |
| Feb 4 | 2026-02-04 00:00:00 UTC | 2026-02-05 00:00:00 UTC | 0 | 0 | 0 |
| Feb 5 | 2026-02-05 00:00:00 UTC | 2026-02-06 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
2 sourcesShow HN: Govctl – A CLI enforcing RFC-driven discipline on AI coding
AI coding assistants are fast but undisciplined. They jump from idea to implementation
without specification. Docs drift from code. "Best practices" become optional suggestions.
I built govctl to fix this. It's an opinionated governance CLI that enforces phase
discipline on software development:
spec → impl → test → stable
Every feature requires an RFC before implementation. Phases can't be skipped. Gates are
checked, not suggested.
The workflow:
$ govctl new rfc "Caching Strategy" # spec first
$ govctl finalize RFC-0015 normative # lock the spec
$ govctl advance RFC-0015 impl # now you can code
$ govctl check # validate everything
govctl governs itself. Every feature in the CLI was specified in an RFC/ADR before
a line of code was written. This repo is the proof that the model w
Read the rest
orks.
Not for everyone. If you thrive in "move fast and break things" workflows, this isn't
for you. But if you're frustrated by AI-generated spaghetti and documentation that lies,
govctl might help.
Built in Rust. MIT licensed.