Skip to content

Narrative Contracts 0.1.0a3 — audit existing validators

Pre-release
Pre-release

Choose a tag to compare

View all tags
@pablomate4b pablomate4b released this 29 Sep 20:36
v0.1.0a3
980c78f

Audit an existing Python validator without adopting the Document/Claim model. Version 0.1.0a3 gives the independent audit APIs their own installable package version, synchronized across core, pytest plugin, and report metadata.

What is included

  • Paired baseline/fault/control cases, finding-ID attribution, obligation inventories, explicit unknown/error outcomes, and CI thresholds.
  • Reports prioritize survivors and other known gaps, incomplete evidence, and untested obligations. Independent evidence flags retain simultaneous gaps and execution failures; the display assessment remains available.
  • Opt-in observed or supplied Git metadata, corpus digests, and versioned JSON reports.
  • State-field bindings and bounded comparison/transition contracts.
  • Progressive adoption from boolean validators, a survivor-to-regression pytest recipe, and executable JSON Schema/Pydantic configuration trials.

Install

python -m pip install narrative-contracts==0.1.0a3 pytest-narrative-contracts==0.1.0a3

The plugin is optional. Core runtime has no third-party dependencies and does not call a model or network during evaluation.

Verification and boundaries

Both wheels and source distributions were installed and exercised in separate clean environments. Validation includes 154 local tests with optional integrations, Ruff, mypy, documentation builds, selected source mutants, and frozen benchmark replay. Historical labels, findings and scores remain unchanged; replays permit only the explicit library-version change.

Integration cases and policies are authored. They demonstrate configuration gaps, not bugs in third-party libraries, independent adoption, production accuracy, or arbitrary-prose truthfulness. The refund prose-only survivor remains in the 8/9 denominator. Corpus design and label review remain the integrator's work.

Release artifacts were built from source commit 980c78f. The attached manifest and SHA256SUMS identify the exact bytes used for PyPI publication; subsequent documentation/publication metadata commits do not rebuild these files.

Documentation · Regression recipe · Source CI

Assets 9
Loading