Governed Engineering
A governance system for agent-driven software development: explicit lifecycle state, path authority checked against the actual diff, commit-bound evidence, single-use state-bound approvals — it decides whether an agent's work counts.
The problem it addresses
A coding agent is not done because it says it is done. Agents produce plausible work at speed — including correct-looking changes nobody authorized, passing tests that prove less than they appear to, and confident claims with no evidence behind them. Review-by-vibes does not scale to agent throughput, and a human approval given yesterday says nothing about the repository that exists today.
What it does
Governed Engineering makes advancement a governed fact rather than a claim. A project's lifecycle phase is explicit state only a validated transition can change. Work happens in bounded runs: the agent receives permitted and prohibited paths, and the governor compares the ACTUAL git diff against that authority — a violation blocks every transition until it is resolved through a governed path. Completion is derived, never asserted: every declared verification must be executed, its output hashed, and the record bound to the run's exact result commit. Human approvals are single-use instruments bound to the governance digest and git tree at issuance — any change after issuance stales them. The kernel that decides all of this is pure, dependency-free, and versioned; the repository's own records are the only source of truth.
Governed Engineering is an independent Robinett Industries product, developed and maintained in its own repository. This site does not contain, reimplement, or simulate it — this page is the product's record here, nothing more.