Metadata-Version: 2.4
Name: zu-checks
Version: 0.7.0
Summary: Zu built-in checks: detectors (empty, error, js-shell, embedded-widget, bot-wall, captcha, human-gate) + validators (schema, grounding)
Project-URL: Homepage, https://github.com/k3-mt/zu
Project-URL: Repository, https://github.com/k3-mt/zu
License-Expression: Apache-2.0
Classifier: Development Status :: 4 - Beta
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: Apache Software License
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Classifier: Topic :: Software Development :: Libraries :: Application Frameworks
Classifier: Typing :: Typed
Requires-Python: >=3.11
Requires-Dist: jsonschema>=4
Requires-Dist: zu-core==0.7.0
Description-Content-Type: text/markdown

# zu-checks

The built-in **checks** that ship with the Zu base runtime — two stdlib plugin
kinds in one package:

- **detectors** (`zu_checks.detectors`) — `empty`, `error`, `js-shell`,
  `bot-wall`. Inspect an observation and return a `Verdict`; the severity drives
  the loop (`ESCALATE` climbs the tier ladder, `TERMINAL` ends the run).
- **validators** (`zu_checks.validators`) — `schema` (does the result fit the
  requested shape?) and `grounding` (does every extracted value actually appear
  in retrieved content? — the anti-hallucination check).

They're packaged together because both are pure-stdlib (schema adds only
`jsonschema`) and always present in the base — unlike the adapter packages
(`zu-providers`, `zu-tools`, `zu-backends`), whose separation carries distinct
heavy optional dependencies. All register via the standard `zu.detectors` /
`zu.validators` entry-point groups, exactly as a third-party check would.
