Sample deliverable for maintainers

A written proof packet for review-load triage.

This sample shows how AgentProof turns public AI PR pain into a bounded review decision: what to verify, how much review churn is at stake, and when to stop instead of spending maintainer time.

Open targeted checkout packet View market proof Buyer handoff

What the buyer gets back

1. Public target brief

Repo or PR URL, proof goal, risky paths, changed-file scope, and explicit no-secrets boundary.

2. Evidence plan

Commands, route or PR proof, CI links, artifacts, screenshots, and review blockers to verify first.

3. Review decision

Review, send back for proof, close, or escalate to outside proof with a written stop rule.

Buyer economics

Current sample math

27 low-proof PRs * 10 minutes = 4.5 hours estimated review churn.

Full-sample break-even

$33.11/hour. Hourly avoided-review value needed for the $149 proof pass to break even if a similar load is prevented.

Smaller slice threshold

At $50/hour, it needs 3 hours saved; at $100/hour, it needs 1.5 hours.

From sample to paid proof pass

1. Keep one public target

google-gemini/gemini-cli

2. Precheck the same public repo

Verify the target stays public-input-only before money or handoff.

Run precheck
3. Buy with repo context

The checkout URL carries the target so the buyer path does not reset.

Target-specific checkout

Source examples used as demand research

Sample written output

Verdict: do not spend maintainer review time until the PR provides linked intent, bounded scope, command output, risky-path evidence, and artifacts.

  • Review-load estimate: 27 low-proof PRs would cost about 4.5 hours at 10 minutes each.
  • First proof ask: attach the exact commands run, CI URLs, screenshots or logs, and a stop rule.
  • Paid escalation: use the $149 async proof pass when outside written evidence is cheaper than review churn.

Scope boundary

Allowed

Public repos, public PRs, public demos, safe test inputs, CI logs, and generated proof reports.

Not allowed

Secrets, private customer data, private repo access, payment data, credentials, or compliance advice.

No pressure

Watch-only source examples are market research. Direct outreach still requires reply eligibility and guard approval.