Install once. Work as usual. Receive the Veripsa Brief automatically.

One click on the GitHub App page. Pick the repositories where humans and agents open pull requests — a single repo, a hand-picked set, or all of them. No credit card.

Veripsa Core uses minimal operational metadata to compare open PRs. Source file bodies are not stored, displayed, or used for code review.

Caveat: Until repository context is available, some PRs may resolve to Unknown. That's expected.

Humans and agents keep opening branches and pull requests through their existing workflow. There is no Veripsa command sequence to run.

This is the point of the product: GitHub is the workbench, coding agents are the workers, Actions verifies, and Veripsa adds the merge-control signal before PRs land together.

Caveat: Agent availability and entry points depend on your GitHub and Copilot setup. Veripsa does not require agents to be configured a specific way.

Each matching PR automatically gets a Veripsa Brief in GitHub: Clear, Heads up, Wait in line, or Unknown.

The brief names the changed surface, related open PRs, and the evidence snapshot behind the warning. You decide what merges; Veripsa makes the merge-order risk visible.

Caveat: Same-owner per-repo today. A PR in one repository doesn't warn against a PR in a different repository, even on the same GitHub account. Cross-repo coordination is on the roadmap.

Merge-capable agent guidance, the veripsa-ack exception label, and GitHub required-check gating are all opt-in controls, not installation steps.

Use agent guidance only to standardize how existing merge automation reads the advisory. Use veripsa-ack only when a human wants an auditable override. Make the check required in a GitHub ruleset or branch protection only after your team has reviewed its own signals.

Caveat: Veripsa remains useful as an advisory if you never enable any of these controls.

Veripsa Core is free while in early access. Fair-use limits protect the shared service so the GitHub App can stay public without surprise infrastructure bills.

If a repository outgrows the free early-access band, Veripsa keeps the warning honest and asks you to reduce coverage or wait for future GitHub Marketplace plans. The active launch path stays install-first.

Caveat: Required-check on private repos is a separate GitHub-plan decision in branch protection. Veripsa itself stays advisory unless you make its check required.