PyVAL — Pure Python PDDL Plan Validator
A pure-Python PDDL plan validator — a drop-in alternative to the compiled VAL binary. Built on unified-planning, zero compiled dependencies, pip install-able everywhere.
PyVAL produces rich, structured diagnostics designed for both humans and LLM consumption: per-step state changes, precondition deficit reporting, and repair-oriented messages.
Install
pip install pddl-pyvalidator
Quick Start
# Validate a plan against a domain and problem
pyval domain.pddl problem.pddl plan.txt
# JSON output for tool integration
pyval domain.pddl problem.pddl plan.txt --json
# Numeric fluent trajectory (one row per step)
pyval domain.pddl problem.pddl plan.txt --trajectory --track fuel --track cost
# Syntax check only (domain, or domain + problem)
pyval domain.pddl
pyval domain.pddl problem.pddl
Exit code is 0 on a valid plan, 1 otherwise.
Python API
from pyval import PDDLValidator
validator = PDDLValidator()
result = validator.validate(
domain_path="domain.pddl",
problem_path="problem.pddl",
plan_path="plan.txt",
)
if result.is_valid:
print("Plan is valid")
else:
for err in result.errors:
print(err)
What Gets Validated
PyVAL runs a three-phase pipeline and halts on the first fatal error:
- Syntax & semantic — PDDL parses, types/predicates/functions are well-formed, no duplicates or arity mismatches.
- Plan structure — every action name exists in the domain, parameters are declared objects with type-compatible (subtype-aware) bindings.
- Plan execution — each step's preconditions hold, effects apply, and goals are satisfied in the final state. Numeric fluents are tracked across steps; quality metrics (
minimize/maximize) are evaluated on the final state.
Unsupported PDDL features (durative actions, PDDL+ processes/events) are reported as warnings rather than silent failures.
Output Modes
- Plain text (default, VAL-like, optionally
-vfor per-step detail) - JSON (
--json) — structured for programmatic consumption - Trajectory (
--trajectory) — numeric fluent values per step, optionally filtered via--track
Development
python3 -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"
pytest
See CLAUDE.md for architecture notes and the validation pipeline overview.
License
MIT — see LICENSE.
Metadata
Release files for pddl-pyvalidator 0.1.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pddl_pyvalidator-0.1.5.tar.gz | 19.2 kB | With provenance | Details for pddl_pyvalidator-0.1.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pddl_pyvalidator-0.1.5-py3-none-any.whl | Python 3 | none | any | Details for pddl_pyvalidator-0.1.5-py3-none-any.whl |
Total release size: 36.4 kB
Release files / pddl_pyvalidator-0.1.5.tar.gz
| Download URL | pddl_pyvalidator-0.1.5.tar.gz |
|---|---|
| Size | 19.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aeea66824ab7c95855591b6b8f8d9e70722c02b7e4575a1f418268bd4bee6e93
|
|
BLAKE2b-256 checksum How to use checksums |
123881f3f2d5391efcd72fab2520dcd305a666e74b99ff4115b5c17c2d0e6ede
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 19, 2026.
Transparency logRelease files / pddl_pyvalidator-0.1.5-py3-none-any.whl
| Download URL | pddl_pyvalidator-0.1.5-py3-none-any.whl |
|---|---|
| Size | 17.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
60a6513edeb000a3b39f9bfaac82c6939a5644a62fb8802f598600ceb58227a4
|
|
BLAKE2b-256 checksum How to use checksums |
9ba42e6f4f9be8a4279f53f3de9dc09065b3c29c72e825b8a859b48969f8f96e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 19, 2026.
Transparency logSecurity for pddl-pyvalidator 0.1.5
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pddl_pyvalidator-0.1.5.tar.gz
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 May 19, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.