Protect one repo before the next AI-authored production PR.

Start with one repo and name the organization that will own the approval receipts. This captures the human and company context before asking for GitHub installation permissions.

Pick the highest-consequence path first. Most teams start with deploy workflows, infrastructure, database migrations, or release branches.

Connect one low-risk repo first. Permission Protocol syncs the repo, then guides you to the required check setup. Existing GitHub App installs are recovered through the same flow.

Add the Permission Protocol workflow and make permission-protocol/approval the required status check context in GitHub branch protection or rulesets.

1. Create a Permission Protocol workspace.
2. Connect or install the GitHub App on the repo you want to protect.
3. Add policy rules in .pp-policy.yml.
4. In the app, copy the repo-specific Permission Protocol workflow.
5. Commit that workflow to .github/workflows/permission-protocol.yml.
6. Make permission-protocol/approval a required check for the protected branch.

name: Permission Protocol
on: [pull_request]
jobs:
  approval:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      pull-requests: read
      statuses: write
      checks: write
    steps:
      - uses: permission-protocol/gate@v1
        with:
          pp-api-key: ${{ secrets.PP_API_KEY }}
          pp-base-url: https://app.permissionprotocol.com
          fail-mode: closed
          production-environments: production,prod,live

required_status_checks:
  strict: true
  contexts:
    - ci/test
    - permission-protocol/approval
protected_branches:
  - main
production_paths:
  - .github/workflows/deploy.yml
  - infra/**
  - migrations/**
policy_file: .pp-policy.yml

Open a test PR touching the protected path. GitHub should show the Permission Protocol check display name as pending, backed by the permission-protocol/approval API context. That pending check is the product working: merge is held until a signer reviews the exact repo, PR, commit, action, policy, and production path.

After an authorized human signs, Permission Protocol issues a receipt tied to the PR, commit, action, policy, signer, and timestamp. The required check turns green for that approved change.