Current proof
Abizor reached DONE through a real PR delivery loop.
This proof summarizes PR #9: a docs-only pull request that passed CI,
reached readiness, published a live Abizor Check, merged through
Abizor with explicit merge permission, ran cleanup with explicit
cleanup permission, and replayed to DONE.
What was verified
The loop did not stop at proof generation.
GitHub Actions ran the Abizor CI proof workflow and the live Abizor Check concluded successfully.
The downloaded Abizor event log had MERGE as the next safe action.
abizor run-next --allow-merge executed the merge boundary, then abizor run-next --allow-cleanup executed post-merge cleanup.
The final replay decision was done in state DONE.
Canonical truth
The event log remains the record of delivery.
Canonical truth remains the Abizor event log. This page is a public proof summary, not a replacement for the event log.
Change Record, GitHub Check, proof report, summary, PR comment body, and artifact manifest outputs are projections or evidence derived from the run.
Evidence
Key delivery facts and artifact hashes.
27227374627803981941488770c4a63b0224ca5cb5f06451f142f44e46f9ee377a76ebdea9fc3bcb8f3ab146fad247b56e9620af02ac6a991094fd6b6839957e51fdf588ebd387c0a6b02b111d50e5a95c1f3e6c261105bdb1ad1169c23f76d3d1fe43035026dbbc778dd7eac8399467b3bfdbOutput
The final Abizor decision was done.
decision: done
state: DONE
reason: post-merge cleanup completed
facts_used:
- kind: cleaned
fresh: trueBoundary
What this proof does not claim.
This proof did not create the pull request. It did merge PR #9 through Abizor with explicit --allow-merge.
It did not deploy code or use a hosted app, hosted API, dashboard, billing flow, or GitHub App.
It is not a compliance, security-audit, regulated-enterprise, or production-deployment claim.