GitHub Actions CI proof
Abizor ran in GitHub Actions on a real pull request, reached the merge boundary, and uploaded proof artifacts.
Read CI proofPublic proofs
Evidence records for the current Abizor loop.
These public pages summarize what has been verified so far. They are intentionally narrow: Abizor shows the CI proof boundary, public surface evidence, and guarded PR comment output without claiming hosted product capabilities that are not live yet.
CIreal GitHub Actions proof
Evidencepublic surface recorded
PR outputguarded comment posted
Boundaryno merge, deploy, or hosted app
Read the proofs
Start with the public summaries.
The durable proof is the event log or run record. These pages are public summaries with dates, output summaries, boundary statements, and artifact hashes where available.
Contract-surface proof
Abizor recorded Python public function signature changes as review evidence before readiness.
Read contract proofGuarded PR comment proof
Abizor posted a PR comment from generated artifacts while keeping the proof record unchanged.
Read comment proofRun it yourself
The quickstart shows the current self-serve CI path for one existing pull request.
Open quickstartBoundary
What these proofs do not claim.
These proofs did not create or merge a pull request.
They did not deploy code or use a hosted app, hosted API, dashboard, billing flow, or GitHub App.
They are not compliance, security-audit, or production-deployment claims.
Raw event logs are not published on the public site unless a specific proof page says otherwise; public proof pages use summary fields and artifact hashes.