Public proof

Change Record Check output without leaking publish proof details.

This proof shows the exact Markdown body Abizor prepares for a GitHub Check, and the separate operator proof output that records publish status, idempotency, client call, and receipt state.

Date2026-06-09
Check bodypublic reviewer text
Operator proofkept outside Check body
Truthevent log remains canonical

What was verified

Abizor used the Change Record output renderer for the Check body.

The proof projected an event log into an Abizor Change Record and built a GitHub Check publish request.

The published-facing Check body came from hosted_github_change_record_check_output_v1.

Publish execution details stayed in the operator proof output instead of appearing in the Check body.

GitHub Check body

This is what reviewers should see.

## Abizor Change Record Check

- Final status: `ready_for_merge`
- GitHub Check conclusion: `success`
- Next safe action: `merge_pr`
- Evidence/fact count: `3`
- Contract surface changed: `yes`
- Contract surface detail: `python / top_level_public_functions / 1 change / review_required`
- Publish proof: tracked outside this GitHub Check body.

Event log remains canonical truth.
This output is projection-only.

Operator proof

Publish mechanics stay outside the Check body.

## Abizor Change Record Check

- Final status: `ready_for_merge`
- GitHub Check conclusion: `success`
- Next safe action: `merge_pr`
- Evidence/fact count: `3`
- Contract surface changed: `yes`
- Contract surface detail: `python / top_level_public_functions / 1 change / review_required`
- Publish status: `published`
- Idempotency: `publish_needed` -> `already_published`
- Client called: `true`
- Receipt appended: `true`

Event log remains canonical truth.
This output is projection-only.

Contract surface evidence

Structured evidence stays outside the short Check body.

Languagepython
Surfacetop_level_public_functions
Change count1
Severityreview_required
Review requirementhuman_review_before_delivery
Evidence items1

Artifact hashes

Public hash references for the output bodies.

The raw event log is not published on this public page. These hashes identify the exact Markdown bodies used in the proof.

Check body SHA-2566f2cf57b7982966092b6d8ca32502eff05b6d5ad8706098233506568a84774d6
Operator proof output SHA-2565ba25c819848b4ca9d56ca57f9efc931ee6f5e7791786ca1696b7604a3c1a6db
Publish request idgithub-check-publish-request-0958cb584929dfb7
Projection SHA-256418b309db2f054d78bb7afec830e7b65694600e2d00a94b1c2d103e26d2a7517

Boundary

What this proof does not claim.

It does not prove live GitHub API publishing.

It does not prove hosted app, hosted API, dashboard, billing, or GitHub App behavior.

It did not create or merge a PR.

It did not deploy code.

It does not make GitHub Check text canonical Abizor state.

It does not claim compliance, security audit coverage, or broad platform support.

Read the surrounding proof trail.

The Check body is one projection over the Abizor Change Record. The event log remains the proof record.

Open comment proof Back to proofs