Public proof

Guarded PR comment posting without changing truth.

This proof summarizes a real PR comment posting run where Abizor used a generated comment body, verified its manifest/hash relationship to the event log, posted the comment, and left the event log unchanged.

Date2026-06-07
Resultcomment posted
Canonical stateevent log unchanged
PR closureclosed, no merge

What was verified

Abizor posted only generated review output.

Abizor ran a CI proof on pull request #6 and produced event log, summary, comment body, and manifest artifacts.

The explicit abizor post-comment step then used the event log, generated comment body, manifest, pull request id, and GitHub command.

The manifest hash relationship bound the comment body to the event log before posting.

What Abizor did

It posted a PR comment without changing the proof record.

  • Produced CI proof artifacts for a real pull request.
  • Verified the comment body against the artifact manifest.
  • Posted the generated PR comment to GitHub.
  • Checked that the event log hash was unchanged before and after posting.
  • Closed the proof PR without merge after recording the proof.

Output

The comment said merge boundary was reached.

Posted GitHub comment:
https://github.com/Abizor/abizor/pull/6#issuecomment-4643054673

Body status: merge boundary reached
Body boundary: merge_pr was not executed
Canonical state: event log unchanged

Artifact hashes

Public hash references for the proof artifacts.

The raw event logs are not published on this public page. The hashes identify the CI artifact set and the local posting artifact set used for the guarded comment command.

Actions event loge4311cce2a3319dd9f226d077ea731bb0f3f0c4b1155e43fc3af39468318433f
Actions comment bodyacf3ffaf5c5229fd55ec8dfbaa00b2a447dac00bd863e45814c6f756ad7a3285
Actions manifestd343db7a3b356182fbbb3c46b16484cb37261b033480b3909d847047027984e2
Posted event log before and afterd08c32196d6cb66efa92ab458256835b0219930d6563391488d63b9456a3cf81
Posted comment body4935c46ed7a46565e6cec8a6bc7e989b3ea893bff32c55a7b532b40e1e93aa8f
Posted manifest60d1516df728292f244f99478bb19201350771a9f23af3017a1cd5db1d296c56

Boundary

What this proof does not claim.

This proof did not create or merge the pull request.

It did not deploy code and did not make GitHub comments the Abizor proof record.

It did not prove hosted app, hosted API, dashboard, billing, GitHub App behavior, compliance, security-audit coverage, or broad platform support.

Use comments as readable output only.

The event log remains the Abizor proof record. The GitHub comment is readable output for reviewers.

Open quickstart Back to trust