Current proof

Abizor generated a local redacted feedback export from a real CI proof bundle.

This proof shows Abizor public CLI wheel 0.1.4 running the self-serve CI proof path on Abizor/abizor-public-proof-target, verifying the proof bundle, and producing a local redacted Markdown feedback export. The export was not uploaded to Abizor servers.

Date2026-06-10

Wheel0.1.4

Feedbacklocal-only

Canonical truthevent log

What was verified

Public wheel, CI proof, verify-proof, live Check, and feedback export.

The target repository was Abizor/abizor-public-proof-target, not the Abizor source repository.

GitHub Actions installed Abizor from https://abizor.dev/downloads/abizor-0.1.4-py3-none-any.whl.

The workflow ran abizor ci-proof, reached the merge boundary, published the Abizor GitHub Check, and verified the proof bundle with abizor verify-proof.

The workflow ran abizor feedback-export and uploaded abizor-feedback.md as a GitHub Actions artifact for the operator to inspect.

Feedback boundary

The feedback file is a projection, not telemetry.

The feedback export declared Projection: true, Canonical truth: false, and Local-only: true.

It stated that the export is generated locally and does not send data to Abizor servers.

The exported Markdown included short questions: what failed, what was unclear, what felt unsafe, and what would block CI adoption.

The redaction check confirmed the feedback export did not contain target repository identity, branch name, PR URL, changed file paths, commit SHA, raw event log, raw manifest, raw Change Record, diffs, or test output.

Evidence

Proof identifiers and artifact hashes.

Target PRAbizor/abizor-public-proof-target#5

Head commit6586e6287c1cb0d52db8d4dd03420440d879f333

Abizor CI Proof run27299686825

GitHub Check run80641821717

Public CLI wheel SHA-25620033e3a5105a068adf666acd7c2d1ce2bb9256ff3e8ca94338c220603e11c5c

Event log SHA-2569782a733defd70f3b208ea4a30249126032a5d36749bf3baae7b3dd837f45cac

Manifest file SHA-2563418d6e659525233391dd6214f3f6ac8938bd6b2dde2cb07399f18145054b603

Change Record JSON SHA-256747f3b50edf1aa6a828c772339972bd5db81604d1513c83f7cde552620262243

Change Record Markdown SHA-256185597004f5232f41d156e5f8ee3d46c983388a567bef9d6090985cfd06265c1

Feedback export SHA-256b098067df79f3ab979011264b8d35bfca66fa3ac65cfef1fc7fb95c0590565be

Output

The downloaded proof bundle verified locally.

verified: event log, manifest, and Change Record artifacts match

Boundary

What this proof does not claim.

This proof did not create, merge, or deploy the pull request.

It did not use PyPI, a hosted app, hosted API, dashboard, billing flow, or GitHub App.

It did not upload feedback to Abizor servers or use a hosted feedback endpoint.

It does not claim hosted customer access, compliance, security-audit, regulated-enterprise, or production-deployment coverage.

Canonical truth remains the Abizor event log. The feedback export, Change Record, GitHub Check, summary, PR comment body, manifest, publish receipt, proof report, and this public page are projections or evidence over that event log.