Skip to main content

Verdict — Python

The Python implementation of Verdict — a small, zero-dependency, async-native rule-evaluation engine. See the top-level README.md for what Verdict is and why it's shaped this way in narrative form; this doc is just "how do I install it and write my first rule" for Python specifically.

This exact file is also what PyPI renders as the package description — none of its sibling files travel with a pip install, which is why every link below is an absolute GitHub URL rather than a relative path; on GitHub itself they work exactly the same way.

Install

pip install verdict-rules

The distribution on PyPI is named verdict-rules (the name verdict was already taken by an unrelated package), but the import name is plain verdict:

from verdict import Rule, FunctionRule, AndRule, OrRule, RulesEngine

A first rule

A FunctionRule's predicate returns a full RuleResult, not a bare boolean — that keeps it in control of detail/data, not just pass/fail:

import asyncio
from verdict import FunctionRule, AndRule, RuleResult, RulesEngine

async def under_limit(context: dict) -> RuleResult:
    return RuleResult(
        rule_name="under_limit",
        passed=context["requests_this_minute"] < context["limit"],
    )

async def in_good_standing(context: dict) -> RuleResult:
    return RuleResult(
        rule_name="in_good_standing",
        passed=context["account_status"] == "active",
    )

async def main() -> None:
    can_proceed = AndRule(
        "can_proceed",
        [
            FunctionRule("under_limit", under_limit),
            FunctionRule("in_good_standing", in_good_standing),
        ],
    )
    engine = RulesEngine([can_proceed])
    result = await engine.run_named(
        "can_proceed",
        {"requests_this_minute": 3, "limit": 10, "account_status": "active"},
    )
    print(result.passed)  # True

asyncio.run(main())

Where to go next

Doc For
docs/quickstart.md The quickstart — core concepts and a full worked example
docs/architecture.md Why it's shaped this way, in depth — type structure, the execution model
docs/extension.md Building on top of it from your own code, with no changes here
docs/maintenance.md Changing this package itself
docs/testing.md How the test suite is organized, and what a change needs to prove
docs/samples/ Worked examples — dynamic discounts, fee waivers, tier promotions, moderation routing, data-driven rule sets
examples/ Full, tested mini-projects behind the more comprehensive samples — real code, real tests, real docs

Development

uv sync
uv run pytest

Release files for verdict-rules 0.2.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for verdict-rules 0.2.1
File Size Uploaded
verdict_rules-0.2.1.tar.gz 7.8 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for verdict-rules 0.2.1
File Interpreter ABI Platform
verdict_rules-0.2.1-py3-none-any.whl Python 3 none any Details

Total release size:17.2 kB

Release files / verdict_rules-0.2.1.tar.gz

Download URL verdict_rules-0.2.1.tar.gz
Size 7.8 kB
Tags Source
SHA-256 checksum
How to use checksums
c60f2fa3318a16efec9d3dc429c106ab75ce05d637eab5e9a22c8cce07cd7ba3
BLAKE2b-256 checksum
How to use checksums
e053271e78e284ad84a15f8b8441deb88c4d4fdeace019b95129c383000bf733
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 12, 2026.

Transparency log

Release files / verdict_rules-0.2.1-py3-none-any.whl

Download URL verdict_rules-0.2.1-py3-none-any.whl
Size 9.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b8eb3e70d293b252fffcb5dc573636a7799a5b8689b3912442aa90e840da82cf
BLAKE2b-256 checksum
How to use checksums
f99e20c9a62b512caf30982fb5a0667698577d1c950071aac75fa0888279518b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 12, 2026.

Transparency log

Release history Release notifications | RSS feed

0.3.1

2 release files

0.3.0

2 release files

0.2.9

2 release files

0.2.8

2 release files

0.2.7

2 release files

0.2.6

2 release files

0.2.5

2 release files

0.2.4

2 release files

0.2.3

2 release files

0.2.2

2 release files

This release

0.2.1 This release

2 release files

0.2.0

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page