Skip to content

Resource

From suggested change to production, one handoff at a time.

The matrix traces an AI-generated change through the developer machine, the pull request, the build and the deployment. At each stage you record who can act, which credentials are in reach and what review is required.

Matrix fields

Changes, credentials and release approvals.

  • Repo permission map
  • Branch protection checklist
  • Secrets and workflow trigger table
  • PR trust-boundary matrix
  • Package and deployment authority notes

Example entries

Risk matrix preview

The matrix shows how a suggestion turns into code, then a pull request, a workflow run, a package change, and finally a deployment.

Workflow row

Example to examine: an untrusted pull request influences a workflow that has a privileged token. Record the event, code actually executed, token permissions and approval before deciding whether the path is exploitable.

PR trust boundary

Record who authored, reviewed, tested, approved, and merged AI-generated changes.

  • Agent output
  • Human review
  • CI result
  • Deployment permission

Package path

Map package additions, lockfile changes, build scripts, post-install hooks, and release automation that an AI system can influence.

01

Matrix dimensions

  • Who can request, approve, merge, or deploy AI-generated changes?
  • Which workflow triggers run with secrets, write tokens, or release authority?
  • Which package, dependency, and generated-code paths can affect production?
  • Which records show what the agent proposed, changed or ran, and who approved it?

Next step

Request the editable matrix.

Request editable matrix