PROOF.

Product

How it works The graph Changes Agents Life after installation

Evidence

Public Proof Findings jsonparser rsync jsonparser case Correctness labels

Practice

Methodology The audit Instruments Trust Topics Labs

Compare

Jama Connect CodeRabbit SonarQube Snyk LDRA

Company

About Partners Open-source audit Install Brand Museum

Higher engineering standards.
Less manual QA. More work you can delegate.

A connected change / interface study

The request is only the beginning.

Follow one fix from the failure to the requirements it affects, the checks it passes and the decision that remains. Select any record to look closer.

Historical change review

Recorded review · Omarchy #14054

A fresh prompt should not answer an old uninstall question.

  1. The request: dismiss an earlier uninstall confirmation when a fresh menu request arrives.
  2. The agreement: the fresh prompt receives the answer. Enter, Escape and Cancel still work on the original question.
  3. The reach: the report records one new requirement, one changed requirement and 30 more in scope.
  4. The evidence: the 10-check regression harness fails on base 821ae58 and passes on head 09bfcda. A separate audit at merge fe3afbf, on proof base 1e43373 pinned to upstream 035ce29, records 69 tests passing. These counts describe different scopes.
  5. The next change: keep the requirement, regression test and review history. Maintainer acceptance remains separate; the PR was still open when checked.

This page presents recorded observations. It does not run checks or approve the change. Read the pull request and the independent confirmation.