feat(workflows): add production-ready agent release gate (AUT-72) - #175
Closed
derrix060 wants to merge 1 commit into
Closed
feat(workflows): add production-ready agent release gate (AUT-72)#175derrix060 wants to merge 1 commit into
derrix060 wants to merge 1 commit into
Conversation
Deterministic CI/CD gate that checks an agent against the production-ready agent bar before it ships: ownership, registry, security scan (runs in CI), evals (runs in CI), risk/autonomy tier, egress/policy, SLO, observability, cost-center. Fails closed on anything it cannot verify. Sibling of ai-review (review gate: a diff; release gate: the agent). - .github/workflows/agent-release-gate.yaml (reusable workflow) - examples/agent-release-gate/README.md (usage + bar + eval contract) - README.md (section pointer) Gate script hardened: urllib.parse + datetime imports, waiver expiry normalized across PyYAML date/str, no-PyYAML fallback parser rewritten (correct list-of-maps handling; the old one mis-parsed security.waivers).
There was a problem hiding this comment.
🟡 Changes recommended
The README introduces a link to examples/agent-release-gate/README.md, but that path does not exist in the repository, resulting in a dead link.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
Adds a top-level README entry for a new “Production-Ready Agent Release Gate” example, intended to point readers to further documentation in the examples/ area.
Changes:
- Add a new README section advertising the Production-Ready Agent Release Gate.
- Add a link from the README to the (intended) example documentation location.
File summaries
| File | Description |
|---|---|
| README.md | Adds a new section and link for the agent release gate documentation. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
+55
to
+57
| ## Production-Ready Agent Release Gate | ||
|
|
||
| Read about it in the [examples/agent-release-gate/README.md](examples/agent-release-gate/README.md) file. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
AUT-72 — the production-ready agent bar, enforcement half.
ai-review(AUT-427/AUT-444) reviews a diff with an LLM. This gate reviewsthe agent against the production-ready bar
with deterministic checks — no LLM, so it's stable, cheap, auditable.
The 9 gates
Fails closed on anything it cannot verify (no manifest, no eval suite,
no scan, unparsable ratio, expired waiver → red +
agent-not-production-readylabel). It runs the caller's own
maketargets (security_command,eval_command) so the gate stays repo-agnostic; the eval contract is amachine-readable
pass_rate <0..1>on the last non-empty stdout line.Verified
passing manifest, SLO-off, eval-below-bar, missing manifest, evals-not-configured,
un-waived findings, valid waiver, expired waiver, platform-team ownership,
A3-tier with A2 coverage. All behave correctly, including the no-PyYAML
fallback parser path (waivers list-of-maps parses cleanly).
Rollout plan (KR A3)
Advisory first (like ai-review in AUT-444): callers add one
release-gatejob;branch protection to require
release-gate / release-gateis a per-repo follow-up.First enrollment: jake (staffing yokai) in citizen-automations — the cleanest
gateway-migration candidate; tracked by a dedicated ticket.