Docs · Pull requests
PR body composition
Zero composes the PR body from session summaries and proof artifacts. Suggested updates queue for operator approval — Zero never silently rewrites a published PR body.
Compose
When a Work item is ready to open a PR, Zero composes the initial body from:
- Session summaries from the Work item's memory
- Proof artifacts attached during VERIFYING
- Outcome classification and resolution notes
POST /api/cases/:id/pr-body/compose
The composed body is not published to GitHub until you create the PR. Review the draft first.
Draft
Retrieve the current composed draft at any time before or after PR creation.
GET /api/cases/:id/pr-body/draft
Suggest updates
After the PR is open — for example after addressing reviewer feedback — Zero can suggest an update to the PR body to reflect the new session output.
POST /api/cases/:id/pr-body/suggest-update
Suggested updates are queued. They are not applied until an operator approves them. Zero never rewrites the published PR body without approval.
Approve updates
Review queued updates in the console and approve to publish.
POST /api/cases/:id/pr-body/updates/:update_id/approve
See also: PR review loop, Proof evidence.