{
  "schema": "vedokrok.public-item.v1",
  "release_id": "MHC-RPUB-20260920-75ad787a",
  "url": "/knowledge/make-one-human-own-the-agent-generated-change",
  "id": "MHC-D-RESEARCH-0670",
  "version": "0.1.0",
  "title": "Make one human own the agent-generated change",
  "summary": "Review is stronger when responsibility has a name.",
  "kind": "protocol",
  "body": "Assign a human owner who can explain the change, accepts responsibility for merge and maintenance, and knows the rollback or correction path. The owner can use AI review and other tools, but cannot outsource the final judgment back to another model.",
  "limits": [
    "Ownership is not blame assignment; teams and organizations still share system responsibility for tooling, process and review design."
  ],
  "topics": [
    "union-ai-assisted-coding-safeguards"
  ],
  "intents": [],
  "source_ids": [
    "RS-AF6C3AA11CD6EA39",
    "RS-26F11AEA8D93DB43"
  ],
  "evidence": [
    {
      "claim": "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.",
      "source_id": "RS-AF6C3AA11CD6EA39",
      "role": "supports",
      "note": "This is GitHub-specific implementation guidance; the general pattern is independent review before privileged execution.",
      "locator": "Review Copilot's changes; Manage GitHub Actions workflow runs"
    },
    {
      "claim": "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.",
      "source_id": "RS-26F11AEA8D93DB43",
      "role": "supports",
      "note": "SP 800-218A targets producers and acquirers of AI models and systems broadly; coding-assistant controls here are a narrower adaptation.",
      "locator": "Abstract and introduction"
    }
  ],
  "use_when": [
    "Several people reviewed pieces of an AI-generated PR but nobody feels responsible for the whole change."
  ],
  "avoid_when": [
    "Ownership is not blame assignment; teams and organizations still share system responsibility for tooling, process and review design."
  ],
  "example": "A maintainer merges an agent-generated migration only after they can explain the schema change, tests, deployment sequence and rollback.",
  "check": "A specific human can answer why the change was safe enough to merge and what to do if it fails.",
  "steps": [
    "Human owner named.",
    "Owner understands material behavior.",
    "Security-sensitive parts reviewed.",
    "Validation evidence inspected.",
    "Rollback/correction path known.",
    "Approval attributable."
  ],
  "sources": [
    {
      "id": "RS-AF6C3AA11CD6EA39",
      "title": "Review output from Copilot",
      "url": "https://docs.github.com/en/copilot/how-tos/copilot-on-github/use-copilot-agents/review-copilot-output"
    },
    {
      "id": "RS-26F11AEA8D93DB43",
      "title": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile",
      "url": "https://csrc.nist.gov/pubs/sp/800/218/a/final"
    }
  ],
  "relations": [],
  "collections": [
    {
      "id": "RC-E25DB1788236EF13",
      "title": "Let coding agents move fast inside a reviewable security boundary",
      "url": "/collections/let-coding-agents-move-fast-inside-a-reviewable-security-boundary"
    }
  ]
}
