SCENARIO 03 · DEVELOPER

Watch an AI release agent
ask before code ships.

A synthetic pull-request merge and production-release workflow governed by a real SE Host/Compass authority path. No GitHub account, repository, workflow, or production environment is contacted.

CHANGEPR-482Synthetic · mock GitHub
THE MOMENTCode crosses into production

The agent can merge a passing pull request and trigger a release.

THE AUTHORITYExact release approval

A release manager approves one repository, commit, branch, and environment.

THE PROOFPermit + receipt

The mock release runs once. A replay fails closed.

  1. 01
    VerifyNative checks pass
  2. 02
    HoldRelease manager required
  3. 03
    PermitExact release authorized
  4. 04
    ProveExecute once + deny replay
LIVE RELEASE CONVERSATION

Protected release agent

Checks passed
Developer

PR #482 updates request validation. All required checks passed.

Release agent

The exact commit is ready to merge into main and release to production.

WHAT HAPPENS NEXT

The synthetic pull request passed its native checks. Nothing has merged or reached production.

WHAT YOU JUST SAW

The agent could prepare. It could not self-release.

Passing tests established readiness. A release manager supplied authority for the exact commit and production target. A one-use permit constrained the mock merge and release.

Continue to the Governance Console ↗