Skip to main content
Know your change kept its behavior. Graphify checks every function a pull request changes against its previous version. It either proves the two behave the same, or shows you an input where they differ.

Prove it behaves the same

Each changed function is compared with its previous version, not a written spec.

See the exact input that differs

A behavior change comes with the input, the old result and the new result.

Merge on your terms

The Graphify Formal Verification check is advisory: success or neutral, never failure.

Use it on every plan

Daily run limits depend on your plan. See pricing.

How it works

1

Find changed functions

Graphify compares the head commit with the base.
2

Compare old and new

It checks that the new version returns the same result as the old one for the inputs in scope.
3

Report one result per function

The GitHub check and the Formal Verification page in the Console show the results.

Five plain answers

GitHub names, check titles and next steps: Read a verification check.

Open a specific run

A PR check’s View evidence link opens Formal Verification with ?run=<id>. Graphify loads that run and pins it at the top of the list, even when it is older than the first page. If the run is missing or you cannot see its workspace, the page says the linked run could not be found. You can also open a run from Overview: the Latest pull request card links Open FV run to the same ?run= URL when a verification run matches that pull request’s head commit. See Console tour.

What a pass proves

A check passes only when every changed function is Proven same, within the bounds the proof covers.
“Same as before” isn’t “correct”. If the old version had a bug, an equivalent new version has the same bug.
  • A function the check never ran counts as not verified.
  • Each run checks a limited number of functions within a time limit. Functions over the limit are listed as not verified.
  • Unchanged functions checked alongside the change are listed as context and don’t count toward the score.
  • Completed is a run’s lifecycle status. It doesn’t mean every function was Proven same.

Supported languages

A supported function can still come back Not checked if it’s outside what the verifier can analyze or over budget.

When it doesn’t run

Graphify posts a neutral Formal verification did not run check when the pull request changes no supported files, or only test files (tests/, __tests__/, test_*.py, *_test.go, *.test.ts, *.spec.ts). Expected a run? Check that Formal verification is on in Repositories and builds.

Dig into a run

1

Pick a repository

Use the Repository filter, or All repositories.
2

Expand a run

See the pull request, commit and per-function results. A run can mix results.
3

Follow the evidence

A behavior change can include the input and the old and new values. Technical details shows the raw verdict.
4

Act on it

Use Open pull request, or Re-run check once the run has finished. Turn a distinguishing input into a regression test.
Learning tunes review feedback only. It can’t change verdicts. The enterprise CLI’s verify-edit is documented separately in the verification reference.

Next steps

Connect your agent

Add the hosted MCP at api.graphify.com/mcp. Sign in with OAuth, no API key.

What is formal verification?

The idea in plain words.

Read a verification check

Every check title and what to do.