Current proof

Abizor 0.1.5 ran the public CLI wheel quickstart on the Abizor proof target.

This proof records the public CLI wheel path running outside the Abizor source repository on Abizor/abizor-public-proof-target. GitHub Actions installed Abizor 0.1.5 from the public CLI wheel, ran abizor ci-proof, published a live GitHub Check, uploaded proof artifacts, and the downloaded bundle verified with abizor verify-proof.

Date2026-06-11

Wheel0.1.5

TargetAbizor public repo

Verifierverify-proof

What was verified

Existing PR, GitHub Actions, live Check, and verified bundle.

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.5-py3-none-any.whl.

The workflow ran abizor ci-proof, reached the merge boundary, published the Abizor GitHub Check, and uploaded proof artifacts.

A clean local virtual environment installed the public CLI wheel and verified the downloaded bundle with abizor verify-proof.

The 0.1.5 verifier checked event log, manifest, Change Record JSON, Change Record Markdown, evaluator identity, evidence refs, and receipt step count consistency.

Canonical truth

The event log remains the proof record.

Canonical truth remains the Abizor event log.

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

Evidence

Proof identifiers and artifact hashes.

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

Abizor CI Proof run27322324644

Python Tests run27322324645

GitHub Check run80716009656

Head commitedbf2fc58f7eef6f9463b08576ccea6cee2a4a82

Public CLI wheel SHA-256a2927a4bd2a0df3eb06a1ed3b72443e01c0ac5f5ac8a62c310dbe7e337bfc4f8

Historical 0.1.4 wheel SHA-25620033e3a5105a068adf666acd7c2d1ce2bb9256ff3e8ca94338c220603e11c5c

Event log SHA-256adc98b5bf7f731103f36392cace58a704870a14a97710e56d797bcb0a9d6413b

Manifest file SHA-2560c0973b0b6ecc1b70da67bb242d2660e3abec3f7faa2d38faa7e3083fe728db0

Manifest content refsha256:99235983f0e6e754f939f7afaa0de475eea65504145736b36ce57a31523c9fd2

Change Record JSON SHA-256ad676c81aec5a2f52960a8c9f816bcc49c9e4decd36bc4998d3aca0efb37a338

Change Record Markdown SHA-2566ec67cb63b18d9acc11bfa6d1c8b4a06a936d00875a86ca79f82548716da4367

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.

Hosted app, hosted API, dashboard, billing, and GitHub App installation are not live.

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