Guided sandbox walkthrough

See Veripsa Core on a public sandbox.

If your repo does not have overlapping open PRs today, the value can be hard to see. This walkthrough uses a public sandbox to show the shape of the check.

This controlled demo shows the GitHub check surface on a prepared PR pair. Evaluate Veripsa on your own repository before changing merge policy.

Fork the sandbox first Read how it works →

Rather see the result first?

The prepared pair below has already run on the public sandbox. Agent A reserves orders/pricing.py and lands clear; Agent B is shown waiting behind it — the exact landing order Veripsa suggested. It's the same pair you fork in the steps.

See the real check on GitHub →

1
Step 1
Open and fork the public sandbox
Open the current public sandbox, fork it onto your own account, then clone the fork so you control the repository.
```
open https://veripsa.com/go/sandbox?source=try_command
```
The redirect opens the current sandbox repository. Click Fork and uncheck "Copy the main branch only" so the two prepared walkthrough branches come with your fork, then clone the fork URL GitHub creates under your own account. (gh repo fork copies all branches by default.)
Caveat: The sandbox is illustrative. Use it to learn the check surface, then evaluate Veripsa on a repository you maintain.
2
Step 2
Install Veripsa Core on your fork
Open the GitHub App page and pick your fork as the single covered repository. Initial processing is usually quick on the small sandbox, but wait for the check to appear before judging the result.
```
open https://veripsa.com/go/install?source=try_command
```
On the install page, choose Only select repositories and pick the fork you created in Step 1. No sign-up, no credit card, no email collected. The App uses minimal operational metadata for advisory checks; source file bodies are not stored.
Caveat: Wait for the first ingest to finish before opening the scenario PRs in Step 3 — brand-new PRs on a freshly installed App can resolve to Unknown for a short window.
3
Step 3
Open the prepared PR pair on your fork
The sandbox includes two prepared branches for the walkthrough. Open one PR from each branch and wait for the Veripsa checks to appear.
```
FORK="$(gh api user -q .login)/ai-pr-collision-lab"
gh pr create --repo "$FORK" --base main --head collide-a --title "Demo scenario A" --body "Prepared Veripsa sandbox scenario A."
gh pr create --repo "$FORK" --base main --head collide-b --title "Demo scenario B" --body "Prepared Veripsa sandbox scenario B."
```
The --repo flag points both PRs at your fork. Without it, gh in a fork clone asks you to pick a default repository and suggests the upstream sandbox first — PRs opened there are invisible to the install on your fork. After the checks run, compare the two PRs. The important part is the GitHub surface: status, comment tone, and the link to Details.
Caveat: If the sandbox branch names change, use the current README in the sandbox repository as the source of truth.
Step 4
Read the comments and click into Details
Each PR gets one advisory check from Veripsa Core. Open the check, read the comment, then click Details to see the short explanation behind the verdict.
Compare the two PRs side by side. The check surfaces what it observed and leaves the merge-order decision to the team.
Caveat: The check is advisory by default. Whether it gates a merge is a branch-protection decision you make later from your own PR history.
Step 5
What just happened
You saw the GitHub check surface: install, open PRs, read the advisory result, and decide what to do next.
The sandbox is a fixture. Your own repo is the evaluation point: whether the verdicts match the PR patterns your AI agents and humans produce.
Caveat: Same-owner per-repo today. A PR in one repo will not warn against a PR in a different repo, even on the same GitHub account. Cross-repo coordination is on the roadmap.

What this walkthrough doesn't claim

The fixture is a controlled scenario. It is not a benchmark, not an assertion of behaviour on your repo, and not a measurement of false-positive or false-negative rates.
Veripsa Core is not an AI code reviewer. It does not store, retain, display, or use source file bodies for code review.
The check is advisory by default. The App does not hard-block a merge by itself — whether its check gates a merge is controlled by your GitHub branch-protection rules.
Same-owner per-repo today. Cross-repo coordination across two different repositories — even on the same GitHub account — is not shipped yet.

After the walkthrough

Install on your own repository — The sandbox shows the UI surface. Fit is evaluated on your own repo — install on a repo you maintain and read a few checks.
How Veripsa works, in five moments — The product flow: install once, receive automatic PR checks, read advisory states, and optionally add advanced controls later.
Docs — Language coverage, plan matrix, webhook surface, false-positive triage — the reference for after you have read the walkthrough.
Is Veripsa right for you? — A four-question self-check. Three honest tiers: strong fit, advisory-only, or come back when the PR traffic shows up.

Walkthrough done. Now evaluate it on your own repo.

The sandbox is a fixture. Your own repository is where you evaluate fit. Veripsa Core is free to install, and file contents are never stored.

Install Veripsa Core

See Veripsa Core on a public sandbox.

If your repo does not have overlapping open PRs today, the value can be hard to see. This walkthrough uses a public sandbox to show the shape of the check.

This controlled demo shows the GitHub check surface on a prepared PR pair. Evaluate Veripsa on your own repository before changing merge policy.

FORK="$(gh api user -q .login)/ai-pr-collision-lab" gh pr create --repo "$FORK" --base main --head collide-a --title "Demo scenario A" --body "Prepared Veripsa sandbox scenario A." gh pr create --repo "$FORK" --base main --head collide-b --title "Demo scenario B" --body "Prepared Veripsa sandbox scenario B."

What this walkthrough doesn't claim

The fixture is a controlled scenario. It is not a benchmark, not an assertion of behaviour on your repo, and not a measurement of false-positive or false-negative rates.

Veripsa Core is not an AI code reviewer. It does not store, retain, display, or use source file bodies for code review.

The check is advisory by default. The App does not hard-block a merge by itself — whether its check gates a merge is controlled by your GitHub branch-protection rules.

Same-owner per-repo today. Cross-repo coordination across two different repositories — even on the same GitHub account — is not shipped yet.

After the walkthrough

Install on your own repository — The sandbox shows the UI surface. Fit is evaluated on your own repo — install on a repo you maintain and read a few checks.

How Veripsa works, in five moments — The product flow: install once, receive automatic PR checks, read advisory states, and optionally add advanced controls later.

Docs — Language coverage, plan matrix, webhook surface, false-positive triage — the reference for after you have read the walkthrough.

Is Veripsa right for you? — A four-question self-check. Three honest tiers: strong fit, advisory-only, or come back when the PR traffic shows up.

Open and fork the public sandbox

Install Veripsa Core on your fork

Open the prepared PR pair on your fork

Read the comments and click into Details

What just happened

What this walkthrough doesn't claim

After the walkthrough

Walkthrough done. Now evaluate it on your own repo.

Open and fork the public sandbox

Install Veripsa Core on your fork

Open the prepared PR pair on your fork

Read the comments and click into Details

What just happened

What this walkthrough doesn't claim

After the walkthrough

Walkthrough done. Now evaluate it on your own repo.