PROOFCIComing soon
PR assurance for engineering teams

Stop approving promises. Start reviewing proof.

ProofCI maps every requirement to implementation, tests, and CI evidence—so reviewers can see what is actually supported before merge.

Private beta coming soon See the proof chain
  • Source-linked
  • Fail-closed
  • GitHub-native
Illustrative website rendering Complete

Same ProofCI assessment data and evidence structure.GitHub displays this report using native Checks and Markdown styling.

proofci/proofci · PR #11

Controlled GitHub App onboarding

7Supported
0Partially supported
0Unsupported
0Unknown
0Out of scope
0Warnings
Requirement 02 of 07 · BEHAVIORAL · PR description

Keep new installations fail-closed until explicit operator activation with quotas.

Matching implementation and direct test evidence were found, and the mapped CI check passed.
SUPPORTED96% confidence
Implementation evidencepackages/database/src/postgres-installation-store.ts:401–4043 citations
Direct test evidencepackages/database/src/postgres-installation-store.integration.test.ts:109–1112 citations
CI evidencevalidate · 515fa09PASS
Evidence gapsNone identified
Full GitHub check expands all 7 requirements with exact source links

Requirements

→

Implementation

→

Tests

→

CI checks

One defensible decision.
01 / The problem

A PR can pass CI and still fail its promise.

Tests tell you whether code executed as expected. ProofCI tells you whether the change actually satisfies the requirements it was supposed to deliver.

SUPPORTED

The evidence is complete.

Implementation, test coverage, and required checks support the stated requirement.

PARTIALLY SUPPORTED

Something is still missing.

Some evidence exists, but the full requirement is not demonstrated by the change.

UNSUPPORTED

The claim outruns the proof.

No trustworthy evidence connects the requirement to implementation and validation.

02 / The proof chain

From issue claim to merge decision.

  1. 01

    Extract the requirements

    ProofCI identifies the concrete behaviors the pull request says it delivers.

    Claim
  2. 02

    Observe implementation and tests

    It maps repository evidence without inventing paths, symbols, checks, or citations.

    Evidence
  3. 03

    Publish a defensible verdict

    Reviewers get a concise assessment that links every conclusion to what was observed.

    Decision
03 / Built for trust

Control the blast radius before you scale the value.

ProofCI is designed for deliberate adoption: start with selected repositories, set hard limits, and revoke access immediately when your organization changes.

01

Fail-closed onboarding

Installation alone never authorizes analysis. Activation is explicit.

02

Repository-level control

Enable only the repositories approved for your pilot or rollout.

03

Bounded usage and cost

Daily, monthly, and cost limits keep consumption predictable.

04

Immediate revocation

Suspension or repository removal blocks both queued and future work.

Private beta · Coming soon

Private beta is coming soon.

Access requests will open after the private-beta process is ready.

  • Access requests are currently closed
  • Selected-repository onboarding when the beta opens
  • Usage controls configured before analysis begins
Coming soonRequests closed
Private beta preparation

We're not accepting access requests yet.

No access-request information is being collected through this site. Check back when private-beta access opens.