Protocol
Name the person accountable for an AI-generated change
A review comment from another model does not take responsibility for the change. Name the human who understands the material behavior and owns the merge decision.
Before you use it
- Use when
- Several people reviewed pieces of an AI-generated PR but nobody feels responsible for the whole change.
Keep this limit in mind
- Ownership is not blame assignment; teams and organizations still share system responsibility for tooling, process and review design.
Current editorial reading
Make ownership usable
Before merge, record the owner, the exact revision reviewed, the important validation results and the correction or rollback path. The owner may rely on specialists for parts of the review, but should know which questions remain unresolved. For example, a generated migration needs someone who can explain its data effects and recovery limits, not just point to passing tests.
Keep responsibility shared
The owner can ask for independent security, domain or operational review when the change needs it. Do not ask one person to certify work they cannot assess. If an important question is unresolved, hold or narrow the change. Naming an owner does not make the code error-free, replace the team’s review controls or turn ownership into blame.
Take it with you
Ask who can explain why this revision is acceptable, what remains uncertain and who will handle a failure. Record that decision rather than treating an AI verdict as the owner.
Sources and evidence (3)
What we checked
OWASP calls for a human owner and explicit developer approval of AI-generated code.
Selected official passage inspected on 2026-10-04. Direct support for this coding-agent practice replaces reliance on a broader AI-development profile.
Secure Coding with AI Cheat Sheet · Secure Coding with AI, section 14: Human Accountability
GitHub asks reviewers to check Copilot pull requests thoroughly before merge.
Selected current official documentation inspected on 2026-10-04. This is product-specific review guidance, not a universal approval implementation.
Review output from Copilot · Review Copilot’s changes
NIST SP800-218A augments the SSDF for AI model development and related AI producers/acquirers.
Abstract inspected on 2026-10-04; full document not reviewed for this card. It does not directly establish this coding-agent ownership checklist.
Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile · Official publication abstract; final July 2024
An AI-generated review is not a substitute for accountable human review.
This is practitioner guidance, not evidence that assigning an owner makes a change error-free.
Secure Coding with AI Cheat Sheet · Section 14, Do and Don’t
Editorial sources (3)
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingName the person accountable for an AI-generated change
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Use before this ideaRequire a human decision before privileged workflow execution
Original edition evidence and sources
These records belong to the original released edition. The current editorial reading has its own evidence above; neither set silently replaces the other.
GitHub documentation says Copilot agent pull requests should receive the same thorough review as other contributions and warns reviewers to inspect workflow changes before allowing privileged Actions runs.
This is GitHub-specific implementation guidance; the general pattern is independent review before privileged execution.
Review output from Copilot · Review Copilot's changes; Manage GitHub Actions workflow runs
NIST SP 800-218A adds AI-specific practices and considerations to the existing SSDF, reinforcing that AI-enabled development inherits ordinary software-security obligations plus additional AI risks.
SP 800-218A targets producers and acquirers of AI models and systems broadly; coding-assistant controls here are a narrower adaptation.
Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile · Abstract and introduction
Original edition, downloads and provenance
The reading above is editorial version 1.0.0, bound to this exact source edition. The original data and saved downloads retain that edition and the separate editorial layer. They may contain earlier wording; use the current reading above when interpreting it.
Version 0.1.0
No review details are supplied for this edition.
Read the original edition and overlay as JSON · Release details