EXAMPLE / Agents
Review an agent's migration proposal
Follow a deterministic release migration through scoped subagents, digest-bound approval, and a draft PR receipt.
Follow the pattern. Inspect its limits.
Explore the source walkthrough, its evidence and the choices you would make in your own application.
Compile the application
The source compiles the release-steward filesystem application and inspects required approvals for patching, draft PR creation, and selected delegation tools.
An exploration of the inspected source; no example is executed here.
The situation.
A fixture release removes billing.invoices.createLegacy and identifies two affected consumer files. The reference separates impact analysis, migration, and independent verification, then produces governed patch and draft-PR evidence without contacting GitHub.
What you will learn
- Declare an agent application's instructions, tools, connections, sandbox, and evaluations as source.
- Constrain analysis, migration, and verification responsibilities.
- Bind approval to the proposed migration and preserve a reviewable draft outcome.
Follow the operation.
- 01
Compile the application
The source compiles the release-steward filesystem application and inspects required approvals for patching, draft PR creation, and selected delegation tools.
- 02
Inspect the migration scope
The fixture calculates an immutable source digest and identifies the affected billing files. Subagent evidence records permitted tools and denied effects, including auto-merge.
- 03
Bind approval and apply once
Tests assert that approval is bound to migration digests, changed material invalidates it, and the patch invocation occurs once even when replayed.
- 04
Read the remaining qualification
The fixture's PR URL is under github.example.test, its PR is a draft, and autoMerge is false. Adapter and deployment composition results explicitly remain candidate with unresolved live requirements.
What the source demonstrates.
- The inspected source asserts separate subagent authority and digest-bound approval.
- Tests assert one application invocation, replay evidence, a draft result, and no auto-merge.
- Candidate readiness retains unresolved requirements for exact live environments.
What it does not establish.
- A real patch applied to a user's repository or an actual GitHub PR.
- Successful CI in a production repository; this fixture reports deterministic CI evidence.
- Production isolation or deployment qualification merely because a topology composes.
Bring it into your environment.
Use the exact source context and prerequisites below. A source walkthrough is not a verified public-package installation recipe.
- Access to the inspected source repository and a checkout at the cited revision.
- The repository's Bun workspace dependencies and required generated package exports. These instructions were inspected; the examples were not executed in this review.
Working directory: examples/agent-application-foundation
bun run example:release-steward
bun test src/release-steward/release-steward.test.tsThe source fixture returns deterministic migration, approval, replay, draft-PR, adapter, and candidate-readiness evidence.
Commands and tests inspected; not executed here.
Read the related guide →Make the pattern your own.
- Begin with read-only impact analysis and a reviewable patch proposal.
- Bind approval to exact source and patch material.
- Keep merge authority and live-environment qualification explicit in the host application.
Inspect the evidence.
Reviewed 2026-10-27 · b67c376f
Pinned source links require repository access; publication and anonymous package availability were not checked for this example.
- Declared maturity
- Not declared
- Catalogue registration
- Source package exists; absent from inspected generated registry
- Inline preview
- Not registered
- Execution in this review
- Not rerun
- Production qualification
- Candidate