RESULTBOND · CHROME EXTENSION

Verify AI-written code.
Share the proof.

ResultBond for Chrome brings signed Proof Receipts into GitHub. It checks the receipt signature locally; evaluation of the actual PR head commit is a separate, upcoming integration.

ActSavo does it You inspect and share the proof ResultBond signs and verifies evidence

The viral loop

Every proof can bring the next user.

01

AI changes code

Claude, Codex, Copilot, Cursor, Devin, ActSavo or a human opens a pull request.

02

ResultBond verifies

The exact work is bound to an evaluator and receives PASS, FAIL or INCONCLUSIVE with a signed receipt.

03

Share the proof

A GitHub-ready badge and receipt link let anyone inspect the verdict independently.

04

The viewer becomes a user

The receipt opens with a ResultBond entry point: verify your own AI work and share the next proof.

Chrome extension v0.4 · preview build

Useful now. Narrow on purpose.

What it does today

  • Recognizes the GitHub pull request you explicitly opened.
  • Scans only that active tab for ResultBond Proof Receipt links.
  • Verifies an open ResultBond receipt tab in one click, or a proof link you paste from any website.
  • Shows how many proofs are present and opens the latest one.
  • Checks receipt signatures locally and opens the full independent ResultBond verifier.
  • Prepares a PR-specific verification request in one click, without uploading code or claiming a completed test.

What it does not claim yet

  • It does not issue a new PASS merely by opening the popup.
  • It does not silently read repositories in the background.
  • It does not upload source code from the extension.
  • “Verify this PR” with an actual signed outcome arrives only after the GitHub evaluator binds an immutable commit SHA.

Privacy by architecture

Two temporary permissions. No permanent GitHub access.

activeTab gives temporary access only to the page you chose when you clicked ResultBond. scripting lets the extension look on that one page for ResultBond receipt links.

No browsing-history permission. No persistent github.com host permission. No background page scraping. No source-code upload by extension v0.4.