v0.10 · Apache-2.0 · open source

Decisions that stay decided.

Your team decides something. Months later a pull request quietly undoes it, review misses it, and the question gets relitigated from zero. Verdica keeps decisions as files in the repo and holds every diff to them.

EVERY COMMIT MEETS THE REGISTRY
Self-host · €0 forever Run it yourself The whole gate, Apache-2.0. Your CI, your keys, nothing leaves your infra. Verdica Cloud · early access Or let our cloud hold the line One-click GitHub App, judgment included, digests to your inbox. No keys, no workflow files.
The registry

A decision is a page, not a memory.

One Markdown file per decision, living next to the code it governs. This one is real: it ships in Verdica’s own repository and gates Verdica’s own pull requests.

.decisions/DEC-0005-shadow-mode-default.md
--- id: DEC-0005 title: Never block by default status: accepted severity: block scope: paths: ["verdica/gate.py", "action.yml"] deciders: [alberto] ---

Decision

The gate reports; it does not fail builds until a team opts a decision into blocking, one decision at a time. Trust is earned in shadow mode first.

Rationale

A gate that cries wolf on day one gets uninstalled on day two. Precision before authority.

ID Citable, greppable, permanent

PRs cite DEC-0005 the way courts cite precedent. The ID survives refactors, people leaving, and the next reorg.

SCOPE The paths it governs

Deterministic glob matching decides which decisions a diff even wakes up. No scope hit, no noise.

STATUS Merging is the ratification

Proposed, reviewed, accepted, superseded: all through ordinary pull requests. CODEOWNERS says who ratifies. Your repo stays the only source of truth.

1Record  a choice as a file, or bootstrap the registry from your repo’s own history 2Ratify  by merging 3Enforce  on every pull request, forever
The gate

Enforcement you can read.

Deterministic first: path scopes select the decisions a diff touches. Only on a hit does a model judge contradiction, and it must cite the exact hunks. No API key? The scope report alone still tells you which law governs the change.

✓ upheldRespects what was ratified

The change touches a decision’s scope and honors it. One quiet line, nothing to do.

⚠ contradictedReverses a standing decision

Flagged with the decision cited and the guilty hunks quoted. Warns by default; blocks only where the team opted in.

· out of scopeSilence is a feature

Decisions whose paths the diff never touches say nothing. The gate lectures nobody.

Evidence

Measured before it was built.

On a ninety-thousand-star repository, a change passed review, merged, and had to be reverted days later for violating two architecture decisions that had been on the books for years.
home-assistant/core, 2026: the merge and the revert. The decisions were recorded. Nobody was holding the diff to them.

Before writing the gate we mined public GitHub: 326 repositories with decision registries, 1,926 recorded decisions, and every pull request that cited one.

Across projects that record decisions, roughly one violation in ten slips through human review and merges. The rest are caught by reviewers doing, by hand and from memory, what a gate does from files.

And the registries themselves rot: 93 percent had never marked a single decision superseded, while their code kept moving. A registry nobody checks becomes fiction. Enforcement is what keeps it true.

Today

What ships, ships whole.

GitHub Action, one workflow fileuses: verdicahq/verdica@v0 and every PR meets the registry.
Reads your existing ADRs in placedocs/adr and friends, Nygard and MADR formats. No migration.
Bootstrap from the repo itselfNormative comments, reverts and meeting notes distilled into proposed decisions, evidence attached.
Rule previews before ratifyingA proposed rule is replayed over recent merges: see its cost before you sign it.
Registry hygiene in the digestDead scopes, unenforceable rules and silently-reversed pairs, surfaced weekly.
Bring your own model, or noneMistral is the reference provider, Anthropic supported. Keyless mode still reports scope.
Agents inherit the registryDecisions are files in the repo, so every coding agent reads them for free.
A review page for non-terminal peoplebootstrap --html renders proposals for the leads who ratify them.
Pricing

Open source forever. Or managed in Verdica Cloud.

The entire gate is Apache-2.0, free forever. Verdica Cloud is the managed service: install the GitHub App, pick your repos, and we run everything else. Always up to date, judgment included, and your code is analyzed in memory, never stored.

Open Source
€0 · APACHE-2.0 · FOREVER
  • The entire gate, CLI and GitHub Action
  • Runs in your CI, nothing leaves your infra
  • Bring your own LLM key, or run keyless
  • Bootstrap, digest, rule previews, hygiene
Install from the repo

You run the workflow, your keys, your CI minutes.

Verdica Cloud
EARLY ACCESS · PRICING AT LAUNCH
  • Install once from GitHub, protected in minutes
  • Judgment included: no API keys to buy or manage
  • Weekly decision digests to the team’s inbox
  • Cross-repo registry view for the org
  • Meeting-notes ingestion by email
  • Code analyzed in memory, never stored
Watch releases for the launch

Early access opens soon; pricing at launch. Watch releases to get in first.