rule-cascade 1.0.0a2__tar.gz

rule_cascade-1.0.0a2/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

rule_cascade-1.0.0a2/NOTICE

@@ -0,0 +1,9 @@
+Rule Cascade
+Copyright 2026 Yarlis LLC
+
+This product is licensed under the Apache License, Version 2.0 (see LICENSE).
+Contributors keep the copyright of their contributions, which they license
+under the same terms; the Git history records each one.
+
+The name "Rule Cascade" and its logos are trademarks of Yarlis LLC and are not
+licensed under the Apache License. See TRADEMARKS.md.

rule_cascade-1.0.0a2/PKG-INFO

@@ -0,0 +1,349 @@
+Metadata-Version: 2.4
+Name: rule-cascade
+Version: 1.0.0a2
+Summary: Rule Cascade for Python, and the reference implementation: compile, publish and evaluate YAML/JSON business rules.
+License-Expression: Apache-2.0
+Project-URL: Repository, https://github.com/YarlisAISolutions/rule-cascade
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: jsonschema>=4.21
+Provides-Extra: yaml
+Requires-Dist: pyyaml>=6.0; extra == "yaml"
+Dynamic: license-file
+
+# rule-cascade (Python)
+
+The Rule Cascade runtime for Python, and the **reference implementation** of the
+[specification](../../spec/v1/SPECIFICATION.md). It implements both conformance levels: it reads a
+bundle and evaluates (evaluator), and it loads source documents and produces bundles (compiler).
+
+Requires Python 3.10 or later. The only dependency is `jsonschema`, which validates source documents
+against the ruleset schema.
+
+```bash
+pip install ./packages/python          # from the repository root
+```
+
+The package is not published to an index. To use it from a checkout without installing it, put
+`packages/python/src` on `PYTHONPATH`; that is what the Makefile, CI and `tools/rulecheck.py` do.
+
+| Module | What it is |
+|---|---|
+| `rule_cascade.expressions` | Expressions, operators and portable patterns: specification section 4 |
+| `rule_cascade.ruleset` | Loading, inheritance, load-time checks, checksum, manifests, bundles: sections 5 to 7 |
+| `rule_cascade.evaluate` | Evaluation of a request against a manifest: section 8 |
+| `rule_cascade.values` | Numbers, equality, canonical JSON and rendering, shared by the others |
+| `rule_cascade.engine` | The engine protocol: section 13 |
+
+The snippets below run from the repository root. They read the JSON fixtures of the conformance
+suite, which are the example rulesets in `examples/contracts` and `examples/catalog` converted to
+JSON.
+
+## Compile and evaluate
+
+`load(document, registry, loader)` runs every step of specification section 5 and returns a
+`RuleSet`, or raises `LoadError`. It never returns a ruleset that failed a check.
+
+```python
+import json
+from pathlib import Path
+
+from rule_cascade import LoadError, load
+
+fixtures = Path("conformance/fixtures")
+
+
+def read(name):
+    return json.loads((fixtures / name).read_text(encoding="utf-8"))
+
+
+registry = {                                    # ruleset id -> document, so `extends` can be resolved
+    "acme.org.base": read("acme-org-base.ruleset.json"),
+    "acme.payments.transfer": read("payments-transfer.ruleset.json"),
+}
+schemas = {"./payments.openapi.yaml": read("payments.openapi.json")}
+
+rules = load(registry["acme.payments.transfer"], registry, schemas.get)
+print(rules.id, rules.version, rules.checksum)
+# acme.payments.transfer 1.0.0 sha256:c192dd53b5b1d307d52ccbc27fc1674114e8714d53b699b24088a648ae242c7e
+
+result = rules.evaluate({
+    "entity": "Transfer",
+    "operation": "create",
+    "data": {"type": "international", "amount": 12000, "currency": "USD",
+             "beneficiary": {"name": "Ana", "country": "ES"}},
+    "actor": {"id": "u-1", "roles": ["teller"]},
+})
+print(result["decision"])
+for finding in result["findings"]:
+    print(finding["code"], finding["severity"], finding["blocking"], finding["fields"])
+# deny
+# ORG-TRF-003 warning False ['/memo']
+# PAY-TRF-002 error True ['/beneficiary/swiftCode']
+# PAY-TRF-003 warning True ['/amount', '/beneficiary/name']
+print(result["effects"])
+# [{'type': 'value', 'field': '/fee', 'value': 180, 'rule': 'transfer.fee.international'}]
+```
+
+- `registry` maps ruleset ids to source documents. The parent named by `extends` must be in it.
+- `loader(file)` returns the parsed document behind the file part of an entity's `$ref`, or `None`.
+  Without a loader the `PATH_UNKNOWN` and `SCHEMA_REF_UNRESOLVED` checks are skipped; every other
+  check still runs.
+- The result is a `dict` with `ruleset`, `version`, `checksum`, `decision`, `findings`, `effects` and
+  `commands`, as specification section 8 defines them.
+
+`evaluate(request, channel="server", operators=None)` checks the shape of the request before it
+evaluates anything and raises `ValueError` for a request that is not well formed:
+
+```python
+rules.evaluate({"entity": "Transfer", "operation": "create", "data": []})
+# ValueError: 'data' must be an object
+```
+
+A ruleset that breaks a rule of section 5 does not load. `LoadError.problems` is a list of
+`{code, message, rule?}` and `LoadError.codes` lists the codes:
+
+```python
+broken = json.loads(json.dumps(registry["acme.payments.transfer"]))
+broken["overrides"]["params"]["maxTransferAmount"] = 60000      # the parent allows only lower values
+try:
+    load(broken, registry, schemas.get)
+except LoadError as err:
+    print(err.codes)
+# ['PARAM_LOOSENED']
+```
+
+### YAML
+
+The package reads no YAML: it takes parsed documents. `read()` in
+[`tools/rulecheck.py`](../../tools/rulecheck.py) parses a ruleset file by the YAML 1.2 core schema,
+as specification section 12 requires, and `python tools/rulecheck.py check <file>` reports every
+scalar that YAML 1.1 and YAML 1.2 parsers read differently. A file that passes that check means the
+same to `yaml.safe_load`.
+
+## Manifests and channels
+
+A loaded ruleset holds two manifests. The server manifest contains everything. The client manifest
+contains only what a browser may see.
+
+```python
+print(len(rules.manifest("server")["rules"]), len(rules.manifest("client")["rules"]))
+# 14 9
+print(sorted(rules.manifest("client")["params"]))
+# ['internationalFeeRate', 'largeTransferThreshold', 'maxTransferAmount']
+
+blocked = {"entity": "Transfer", "operation": "create",
+           "data": {"type": "international", "amount": 500, "currency": "USD", "memo": "gift",
+                    "beneficiary": {"name": "X", "country": "KP", "swiftCode": "ABCDKPPY"}}}
+print(rules.evaluate(blocked)["decision"], rules.evaluate(blocked, "client")["decision"])
+# deny allow
+```
+
+The rule that blocks the country is `enforcement: server`, so the client channel does not know it.
+A client evaluation is advice; the server evaluation is the decision.
+
+`rule_cascade.evaluate(manifest, request, operators=None)` evaluates a manifest received from
+elsewhere, for example one fetched from a rule server.
+
+## Bundles
+
+A bundle is the compiled form of a ruleset: one JSON document with both manifests. Compile once, in
+CI, and evaluate the same bundle in every runtime.
+
+```python
+from rule_cascade import RuleSet
+
+bundle = rules.bundle()
+print(list(bundle))
+# ['ruleCascadeBundle', 'id', 'version', 'checksum', 'manifests']
+Path("acme.payments.transfer.bundle.json").write_text(json.dumps(bundle), encoding="utf-8")
+
+loaded = RuleSet.from_bundle(json.loads(Path("acme.payments.transfer.bundle.json").read_text(encoding="utf-8")))
+print(loaded.checksum == rules.checksum, loaded.resolved)
+# True None
+```
+
+`RuleSet.from_bundle` raises `LoadError` with `BUNDLE_UNSUPPORTED` for a bundle whose format is not
+version 1.x and `BUNDLE_INVALID` for one without a usable `server` and `client` manifest. It runs no
+other check, because the compiler already did. `resolved` is `None` for a ruleset read from a
+bundle: a bundle holds manifests, not the resolved source. A bundle contains the server manifest, so
+it is never sent to a browser.
+
+From the command line, `python tools/rulecheck.py compile <file> -o <id>.bundle.json` writes the
+bundle of a ruleset file.
+
+## Custom operators
+
+A ruleset declares the custom operators it uses under `operators` and calls them as
+`{"op": "x-<name>", "args": [...]}`. The host supplies each one as a function, by name:
+
+```python
+def luhn(text):
+    if not isinstance(text, str) or len(text) < 2 or not all("0" <= c <= "9" for c in text):
+        return False
+    total = 0
+    for i, c in enumerate(reversed(text)):
+        d = int(c) * (2 if i % 2 else 1)
+        total += d - 9 if d > 9 else d
+    return total % 10 == 0
+
+
+operators = {"x-luhn": luhn}
+
+customer = RuleSet.from_bundle(json.loads(
+    Path("conformance/bundles/acme.onboarding.customer.bundle.json").read_text(encoding="utf-8")))
+print(customer.manifest("server")["operators"])      # what this manifest needs; check it at start-up
+# ['x-luhn']
+
+request = {"entity": "Customer", "operation": "update", "original": {},
+           "data": {"loyaltyNumber": "79927398710"}, "view": {"section": "membership"}}
+finding = customer.evaluate(request, "server", operators)["findings"][0]
+print(finding["code"], finding["message"])
+# ONB-CUS-001 This loyalty number is not valid. Check the digits.
+print(finding["location"])
+# {'page': 'onboarding', 'screen': 'profile', 'section': 'membership'}
+
+finding = customer.evaluate(request, "server")["findings"][0]      # not registered: fails closed
+print(finding["code"], finding["blocking"], finding["detail"])
+# RULE-EVALUATION-ERROR True custom operator x-luhn is not registered
+```
+
+An operator receives its arguments as positional plain values (`None`, `bool`, `str`, `int` or
+`float` rounded to 15 significant digits, `list`, `dict`) and returns a JSON value. It must be a pure
+function. An operator that is missing, raises, or returns NaN or an infinity makes the rule fail
+closed with a `RULE-EVALUATION-ERROR` finding.
+
+The `view` in the request above narrows the evaluation to one place in the user interface, and
+`finding["location"]` reports the place the rule's target names (specification section 8).
+
+Check at start-up that every operator the rules need is registered. A missing operator does not
+fail the load; it fails every rule that uses it, closed.
+
+```python
+rules = RuleSet.from_bundle(bundle)                              # the onboarding catalog
+print(rules.missing_operators({}))                               # ['x-luhn']
+print(rules.missing_operators({"x-luhn": lambda text: True}))    # []
+```
+
+## One manifest on its own
+
+A front end receives the client manifest, not the bundle. A ruleset read from one manifest has that
+one channel:
+
+```python
+from rule_cascade import ChannelError, RuleSet
+
+client = RuleSet.from_manifest(bundle["manifests"]["client"])
+print(client.channels)                                           # ['client']
+print(client.evaluate({"entity": "Customer", "operation": "create", "data": {"fullName": "Maya"}})["decision"])  # deny
+try:
+    client.evaluate({"entity": "Customer", "operation": "create"}, "server")
+except ChannelError as err:
+    print(err)                                                   # ruleset acme.onboarding.customer has no server manifest
+```
+
+## Expressions
+
+```python
+from rule_cascade import EvalError, evaluate_expression
+
+print(evaluate_expression({"op": "add", "args": [0.1, 0.2]}))
+# 0.3
+vat = {"params": ["amount"],
+       "body": {"op": "round", "args": [{"op": "mul", "args": [{"var": "arg.amount"}, 0.21]}, 2]}}
+print(evaluate_expression({"fn": "vat", "args": [{"var": "data.net"}]}, {"data": {"net": 19.99}}, {"vat": vat}))
+# 4.2
+print(evaluate_expression({"var": "data.rate"}, {"data": {"rate": 0.1234567890123456}}))
+# 0.123456789012346
+try:
+    evaluate_expression({"op": "lt", "args": [None, 100]})
+except EvalError as err:
+    print(err)
+# number expected, got None
+```
+
+`evaluate_expression(expr, env=None, functions=None, operators=None)` returns a plain JSON value and
+raises `EvalError` for an evaluation error. Arithmetic is decimal with 34 significant digits; every
+number that leaves is rounded half even to 15 significant digits (specification 4.2).
+`rule_cascade.expressions.pattern_problem(pattern)` returns why a pattern is outside the portable
+subset of specification 4.4, or `None` when it is inside.
+
+## Refreshing the rules
+
+`RuleSetHolder` loads the rules again on an interval (seconds) or a cron schedule and swaps them in.
+When a load raises, it keeps the last good rules; a ruleset with the checksum already held is not
+swapped in. The schedule runs on a daemon `threading.Timer`.
+
+```python
+from rule_cascade import RuleSet, RuleSetHolder
+
+
+def load_bundle():
+    return RuleSet.from_bundle(json.loads(Path("transfer.bundle.json").read_text(encoding="utf-8")))
+
+
+rules = RuleSetHolder(load_bundle, interval=300, on_reload=lambda r: r.error and print("not refreshed:", r.error))
+# or RuleSetHolder(load_bundle, cron="0 * * * *", tz=ZoneInfo("Europe/Paris"))
+result = rules.get().evaluate(request)
+rules.close()
+```
+
+`CronSchedule("*/5 * * * *").next(after, tz)` is the cron syntax of
+[docs/caching.md](../../docs/caching.md#cron-syntax). `packages/python/bench/evaluate.py` measures
+evaluations per second ([docs/performance.md](../../docs/performance.md)).
+
+## Engine protocol
+
+The package runs as a program that any language drives over standard input and output: one JSON
+request per line in, one JSON response per line out (specification section 13).
+
+```bash
+printf '%s\n' '{"id":1,"command":"version"}' '{"id":2,"command":"expression","expr":{"op":"add","args":[0.1,0.2]}}' \
+  | python -m rule_cascade engine
+# {"id":1,"ok":true,"result":{"engine":"rule-cascade-python","engineVersion":"1.0.0a1","ruleCascade":"1.0.0","bundle":"1.0.0","levels":["evaluator","compiler"],"operators":[]}}
+# {"id":2,"ok":true,"result":0.3}
+```
+
+It implements `version`, `load`, `manifest`, `evaluate`, `expression` and `compile`.
+`--conformance-operators` registers the three operators of the conformance suite (`x-test-reverse`,
+`x-test-sum`, `x-luhn`); without the option no custom operator is registered, and rules that use one
+fail closed. To serve the protocol with operators of your own, call
+`rule_cascade.engine.serve(sys.stdin, sys.stdout, operators)` from a program of yours, or use the
+`Engine` class directly: `Engine(operators).handle(request)` takes a request object and returns the
+response object.
+
+## Role as the reference implementation
+
+The other runtimes (TypeScript, Java, Go) are ports of this package and must agree with it on every
+case of the [conformance suite](../../conformance/README.md). Three things follow:
+
+- A change to the specification is implemented here first, then in the other runtimes.
+- The generated parts of the suite (checksums, bundles, the evaluation corpus) are produced by this
+  package through `python tools/rulecheck.py sync`. They prove that the runtimes agree with the
+  reference. The hand-written expression, load-error and protocol cases and the golden tests are
+  what tie the reference to the specification.
+- [`tools/rulecheck.py`](../../tools/rulecheck.py) is the command-line front end of this package:
+  `check`, `compile`, `manifest`, `conformance`, `sync`, `jsonlogic` and `derive`.
+
+The code is written to be read next to the specification. It is not optimised: use it for tooling,
+tests and services where Python is the language of the host.
+
+## Tests
+
+From the repository root, with the tool dependencies installed
+(`pip install -r tools/requirements.txt`):
+
+```bash
+PYTHONPATH=packages/python/src python -m unittest discover -s packages/python/tests -q   # or: make python
+python tools/rulecheck.py conformance | tail -1                                          # or: make conformance
+# conformance: 1899 cases, 0 failure(s)
+PYTHONPATH=packages/python/src python tools/rulecheck.py conformance \
+  --engine "python -m rule_cascade engine --conformance-operators" | tail -1
+# conformance: 1899 cases, 0 failure(s)
+```
+
+The first command runs the whole conformance suite through the engine protocol in process and checks
+that the generated files are current. The last one runs the same cases against the package started
+as a separate program.