Coding agents that ship,
inside change control
Platform teams use govern.sh to let coding agents open PRs, run CI, and deploy — with repo access scoped to branches, production gated behind on-call approval, and every merge carrying its own change-management evidence.
Where autonomy breaks down today
Bot PATs with org-wide write
The token behind most coding agents can push to any repo in the org, including the ones it has no business touching. Rotation is manual and scope review never happens.
Agent commits blur accountability
When agent and human commits share a bot account, git blame stops answering the only question that matters during an incident: what changed this, and who or what decided to.
Autonomous deploys fail the audit
SOC 2 change management wants documented approval per production change. An agent that deploys on green CI produces exactly none of that — until the auditor asks.
From bug report to production, gated
Overnight, patch-agent picks up a triaged null-pointer bug in the billing service and carries the fix all the way to a deploy — with two checkpoints.
patch-agent signs its own commits
PassportWorking under its own passport rather than a shared bot account, its commits and PRs are attributable to a specific agent identity and the run that produced them.
Repo write is scoped to its branch
Policyrepo-guardrail allows pushes to fix/* branches on the billing service only. An attempted push to main — or to any other repo — is denied before it reaches the remote.
CI passes, and the deploy request holds
PolicyTests are green and the PR is mergeable, but production deploys are approval-required by policy regardless of who — or what — requests them.
The on-call engineer approves the release
ApprovalSofia reviews the diff summary, the test results, and the rollback plan in the approval card, and signs off. The deploy proceeds with her name on it.
The change record writes itself
ReceiptA signed receipt links the commit range, CI run, approver, and deploy — chained into the trail and attached to the PR. That is the change-management evidence, already assembled.
Guardrails that feel like good tooling
Scope, gate, and record agent activity across repos, CI, and deploy targets — without slowing the loop your engineers actually like.
Allow pushes by ref pattern and repository. Coding agents get room to work in their branches and a hard wall everywhere else.
Staging flows at machine speed; production requires the on-call's approval. The distinction lives in policy, not in each agent's prompt.
Passport-signed commits mean git blame, incident reviews, and dashboards distinguish every agent from every human, permanently.
Each production change carries a receipt linking code, tests, approval, and deployment — collected continuously instead of reconstructed annually.
Representative outcomes reported by govern.sh customers in software teams.
Change management, continuously satisfied
SOC 2 CC8.1 expects authorized, documented, and tested changes. With govern.sh, every agent-driven production change carries a signed receipt binding the commit, the CI result, and the human approval into one verifiable record — so the evidence for your Type II observation window accumulates as a side effect of shipping.
The blocker was never whether the agent could write the fix — it was whether I could put an autonomous deploy in front of our auditor. Now every agent release has a better paper trail than our human ones did last year.
Related use cases
Put a verified agent to work in software teams.
Mint a passport, attach a policy, and watch the first signed receipt land — free for your first three agents.