jamjet-guardrails-validators 0.1.0__tar.gz

jamjet_guardrails_validators-0.1.0/.gitignore

@@ -0,0 +1,30 @@
+__pycache__/
+*.egg-info/
+dist/
+build/
+.venv/
+.pytest_cache/
+# Hypothesis writes its own caches here. The `ci` profile in tests/conftest.py
+# sets `database=None`, so no failing example is stored, but the unicode and
+# constants caches are written regardless.
+.hypothesis/
+.ruff_cache/
+.mypy_cache/
+.claude/
+.superpowers/
+docs/superpowers/
+CLAUDE.md
+progress-tracker.md
+REQUIREMENTS.md
+docs/specs/
+benchmarks/.cache/
+
+# The training tree's virtualenv, which is NOT the package's `.venv`. The rule
+# above matches a directory named exactly `.venv` and does not reach this one.
+/.venv-training/
+
+# Raw downloads and intermediate splits for the training tree. Anchored with a
+# leading slash on purpose: a bare `data/` also matches any nested directory of
+# that name, and `data` is common enough that an unanchored rule would silently
+# swallow a real source directory somewhere under src/ or corpora/.
+/data/

jamjet_guardrails_validators-0.1.0/LICENSE

@@ -0,0 +1,204 @@
+
+                                 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.
+
+Copyright 2026 JamJet Labs

jamjet_guardrails_validators-0.1.0/PKG-INFO

@@ -0,0 +1,206 @@
+Metadata-Version: 2.5
+Name: jamjet-guardrails-validators
+Version: 0.1.0
+Summary: Guardrails AI validators backed by jamjet-guardrails.
+Project-URL: Homepage, https://github.com/jamjet-labs/jamjet-guardrails
+Project-URL: Repository, https://github.com/jamjet-labs/jamjet-guardrails
+Project-URL: Issues, https://github.com/jamjet-labs/jamjet-guardrails/issues
+Author: Sunil Prakash
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: guardrails,guardrails-ai,llm-security,pii,prompt-injection,validator
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Security
+Classifier: Typing :: Typed
+Requires-Python: <3.14,>=3.10
+Requires-Dist: guardrails-ai<1.0.0,>=0.11.0
+Requires-Dist: jamjet-guardrails<1.0.0,>=0.3.0
+Provides-Extra: dev
+Requires-Dist: mypy>=1.11; extra == 'dev'
+Requires-Dist: pytest>=8; extra == 'dev'
+Requires-Dist: ruff>=0.6; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# jamjet-guardrails-validators
+
+[Guardrails AI](https://github.com/guardrails-ai/guardrails) validators backed by
+[jamjet-guardrails](https://github.com/jamjet-labs/jamjet-guardrails), a
+zero-dependency library of deterministic content checks with published precision
+and recall.
+
+Installed from PyPI, not from the Guardrails Hub, which is closed. Every
+validator here is an ordinary pip install.
+
+## Install
+
+```
+pip install jamjet-guardrails-validators
+```
+
+Requires Python 3.10 to 3.13, the range `guardrails-ai` itself supports.
+
+## Use the composite
+
+```python
+from guardrails import Guard
+from jamjet_guardrails_validators import JamJetChain
+
+guard = Guard().use(JamJetChain(checks=["pii", "secrets"], on_fail="fix"))
+
+outcome = guard.validate("SLACK_BOT_TOKEN=xoxb-0000000000-2000000000008-EXAMPLEONLYnotarealtoken")
+outcome.validated_output
+# 'SLACK_BOT_TOKEN=[REDACTED:CREDIT_CARD+SLACK_TOKEN]'
+```
+
+## Why one validator and not two
+
+Stacking `jamjet/pii` and `jamjet/secrets` as two validators is not the same
+thing, and the difference is a leak rather than a preference. Measured on
+guardrails-ai 0.11.0, which has two validator services and picks between them
+without asking.
+
+**The sequential service** (`GUARDRAILS_RUN_SYNC=true`) hands each validator the
+previous validator's `fix_value`. Over the token above, with `jamjet/pii` first,
+the guard reports `validation_passed=True` and returns:
+
+```
+SLACK_BOT_TOKEN=[REDACTED:SLACK_TOKEN][REDACTED:CREDIT_CARD]-EXAMPLEONLYnotarealtoken
+```
+
+The 13-digit middle segment is Luhn-valid and begins with a 2, so the PII check
+reads it as a payment card and redacts it first. That placeholder splits the
+token in half. The secrets check then matches only the 16-character prefix, and
+the 24-character secret tail survives into a value the guard calls valid.
+
+**The default async service** runs every validator over the original value and
+combines the fixes with a three-way merge. That closes the stump above and opens
+something worse: a `FailResult` with no `fix_value`, which is what a deny is, is
+outvoted by one that carries a fix. Stacking `jamjet/injection-structural` with
+`jamjet/pii` under `on_fail="fix"`, over a string carrying both an address and a
+tag-character injection payload, returns `validation_passed=False` in one order
+and `validation_passed=True` with the payload intact in the other.
+
+`JamJetChain` has neither failure because it does not compose fixes at all. It
+runs one chain, which hands every check the same original string, merges every
+redaction in a single pass over that string, and combines decisions restrictively
+so a later check cannot talk an earlier deny back down to a pass. The host gets
+one `FailResult` with one `fix_value`, and the placeholder names every check that
+claimed the region: `[REDACTED:CREDIT_CARD+SLACK_TOKEN]` rather than one of the
+two.
+
+The per-check validators exist for a caller composing a single check. If you want
+two, use the composite.
+
+## Which checks you can name
+
+`checks` takes any check the installed `jamjet-guardrails` registers. That list
+grows with the core library, so read it from the library rather than from this
+page:
+
+```python
+from jamjet_guardrails_validators import VALIDATORS
+sorted(VALIDATORS)
+```
+
+`VALIDATORS` is generated from `jamjet_guardrails.detectors.AVAILABLE` at import,
+so a check added to the core is a validator here with no edit. A single check:
+
+```python
+from jamjet_guardrails_validators import validator_for
+
+guard = Guard().use(validator_for("pii")(on_fail="fix"))
+```
+
+A check that takes options is configured through `options`, keyed by check name:
+
+```python
+JamJetChain(checks=["secrets"], options={"secrets": {"on_match": "deny"}}, on_fail="exception")
+```
+
+## Choosing `on_fail`
+
+| Chain decision | `FailResult` carries | `on_fail="fix"` | `on_fail="exception"` |
+|---|---|---|---|
+| `allow` | nothing, it passes | value unchanged | value unchanged |
+| `redact` | `fix_value` and the spans | the redacted value | raises |
+| `deny` | the spans, no `fix_value` | `validation_passed` is False and `validated_output` is None | raises |
+
+Measured on guardrails-ai 0.11.0: `on_fail="fix"` over a `FailResult` with no
+`fix_value` does not raise and does not pass the original through. It sets
+`validation_passed` to False and `validated_output` to None. That is the right
+answer and a quiet one, so **put deny-class checks under
+`on_fail="exception"`**. There is no fix for a deny, and a caller that reads
+`validated_output` without reading `validation_passed` gets `None` rather than a
+signal.
+
+The chain's own content on a deny is never offered as a `fix_value`.
+`GuardrailChain`'s docstring is explicit that on a deny that string exists for
+the audit record and is not safe to send.
+
+## What the failure carries
+
+`error_message` names the validator, the decision and the finding types, for
+example:
+
+```
+jamjet/chain[pii,secrets]: redact (pii:CREDIT_CARD, secrets:SLACK_TOKEN)
+```
+
+`error_spans` carries one `ErrorSpan` per located finding, with `start` and `end`
+indexing the value that was validated and `reason` naming the detector and the
+finding type.
+
+Neither ever quotes the content. If a check itself fails, the message carries the
+exception's type name and the SHA-256 of what was inspected, and not the
+exception's message: an exception message routinely quotes the value that caused
+it, and that value is the content.
+
+## Direction and origin
+
+Every validator takes `direction` (`"input"` or `"output"`, default `"output"`)
+and `origin` (default `"model"`). They reach the check as its `Context`, they are
+recorded on every verdict, and some checks decide differently per direction.
+Validating a user's message rather than a model's reply means
+`JamJetChain(checks=[...], direction="input", origin="user")`.
+
+Any `metadata` a Guard passes is forwarded to the check as `Context.metadata`.
+
+## Licence
+
+Apache-2.0.
+
+## The framework this adapter installs makes network calls
+
+`jamjet-guardrails` says on its own front page: no dependencies, no network
+calls, no model downloads. That is true of the core and it stops being true of
+your environment the moment you install this adapter, so it is said here rather
+than left for you to find.
+
+Measured on `guardrails-ai` 0.11.0: it posts usage metrics unless
+`settings.rc.enable_metrics` is false, and it builds an OpenTelemetry batch span
+exporter AT IMPORT whose flush happens at interpreter exit. On a machine with no
+route to the endpoint, that flush is several seconds of OTLP retries at the end
+of every process; on a machine with one, it is a report.
+
+Both are yours to turn off, and the ORDER matters, because the exporter is built
+during import:
+
+```python
+import os
+os.environ["OTEL_SDK_DISABLED"] = "true"   # before importing guardrails
+
+from guardrails import settings
+settings.rc.enable_metrics = False
+settings.disable_tracing = True
+```
+
+`tests/conftest.py` in this package does exactly that, for the same reason.
+
+Nothing in this adapter sends anything anywhere. The spans and messages it
+returns go back to the host in-process.

jamjet_guardrails_validators-0.1.0/README.md

@@ -0,0 +1,177 @@
+# jamjet-guardrails-validators
+
+[Guardrails AI](https://github.com/guardrails-ai/guardrails) validators backed by
+[jamjet-guardrails](https://github.com/jamjet-labs/jamjet-guardrails), a
+zero-dependency library of deterministic content checks with published precision
+and recall.
+
+Installed from PyPI, not from the Guardrails Hub, which is closed. Every
+validator here is an ordinary pip install.
+
+## Install
+
+```
+pip install jamjet-guardrails-validators
+```
+
+Requires Python 3.10 to 3.13, the range `guardrails-ai` itself supports.
+
+## Use the composite
+
+```python
+from guardrails import Guard
+from jamjet_guardrails_validators import JamJetChain
+
+guard = Guard().use(JamJetChain(checks=["pii", "secrets"], on_fail="fix"))
+
+outcome = guard.validate("SLACK_BOT_TOKEN=xoxb-0000000000-2000000000008-EXAMPLEONLYnotarealtoken")
+outcome.validated_output
+# 'SLACK_BOT_TOKEN=[REDACTED:CREDIT_CARD+SLACK_TOKEN]'
+```
+
+## Why one validator and not two
+
+Stacking `jamjet/pii` and `jamjet/secrets` as two validators is not the same
+thing, and the difference is a leak rather than a preference. Measured on
+guardrails-ai 0.11.0, which has two validator services and picks between them
+without asking.
+
+**The sequential service** (`GUARDRAILS_RUN_SYNC=true`) hands each validator the
+previous validator's `fix_value`. Over the token above, with `jamjet/pii` first,
+the guard reports `validation_passed=True` and returns:
+
+```
+SLACK_BOT_TOKEN=[REDACTED:SLACK_TOKEN][REDACTED:CREDIT_CARD]-EXAMPLEONLYnotarealtoken
+```
+
+The 13-digit middle segment is Luhn-valid and begins with a 2, so the PII check
+reads it as a payment card and redacts it first. That placeholder splits the
+token in half. The secrets check then matches only the 16-character prefix, and
+the 24-character secret tail survives into a value the guard calls valid.
+
+**The default async service** runs every validator over the original value and
+combines the fixes with a three-way merge. That closes the stump above and opens
+something worse: a `FailResult` with no `fix_value`, which is what a deny is, is
+outvoted by one that carries a fix. Stacking `jamjet/injection-structural` with
+`jamjet/pii` under `on_fail="fix"`, over a string carrying both an address and a
+tag-character injection payload, returns `validation_passed=False` in one order
+and `validation_passed=True` with the payload intact in the other.
+
+`JamJetChain` has neither failure because it does not compose fixes at all. It
+runs one chain, which hands every check the same original string, merges every
+redaction in a single pass over that string, and combines decisions restrictively
+so a later check cannot talk an earlier deny back down to a pass. The host gets
+one `FailResult` with one `fix_value`, and the placeholder names every check that
+claimed the region: `[REDACTED:CREDIT_CARD+SLACK_TOKEN]` rather than one of the
+two.
+
+The per-check validators exist for a caller composing a single check. If you want
+two, use the composite.
+
+## Which checks you can name
+
+`checks` takes any check the installed `jamjet-guardrails` registers. That list
+grows with the core library, so read it from the library rather than from this
+page:
+
+```python
+from jamjet_guardrails_validators import VALIDATORS
+sorted(VALIDATORS)
+```
+
+`VALIDATORS` is generated from `jamjet_guardrails.detectors.AVAILABLE` at import,
+so a check added to the core is a validator here with no edit. A single check:
+
+```python
+from jamjet_guardrails_validators import validator_for
+
+guard = Guard().use(validator_for("pii")(on_fail="fix"))
+```
+
+A check that takes options is configured through `options`, keyed by check name:
+
+```python
+JamJetChain(checks=["secrets"], options={"secrets": {"on_match": "deny"}}, on_fail="exception")
+```
+
+## Choosing `on_fail`
+
+| Chain decision | `FailResult` carries | `on_fail="fix"` | `on_fail="exception"` |
+|---|---|---|---|
+| `allow` | nothing, it passes | value unchanged | value unchanged |
+| `redact` | `fix_value` and the spans | the redacted value | raises |
+| `deny` | the spans, no `fix_value` | `validation_passed` is False and `validated_output` is None | raises |
+
+Measured on guardrails-ai 0.11.0: `on_fail="fix"` over a `FailResult` with no
+`fix_value` does not raise and does not pass the original through. It sets
+`validation_passed` to False and `validated_output` to None. That is the right
+answer and a quiet one, so **put deny-class checks under
+`on_fail="exception"`**. There is no fix for a deny, and a caller that reads
+`validated_output` without reading `validation_passed` gets `None` rather than a
+signal.
+
+The chain's own content on a deny is never offered as a `fix_value`.
+`GuardrailChain`'s docstring is explicit that on a deny that string exists for
+the audit record and is not safe to send.
+
+## What the failure carries
+
+`error_message` names the validator, the decision and the finding types, for
+example:
+
+```
+jamjet/chain[pii,secrets]: redact (pii:CREDIT_CARD, secrets:SLACK_TOKEN)
+```
+
+`error_spans` carries one `ErrorSpan` per located finding, with `start` and `end`
+indexing the value that was validated and `reason` naming the detector and the
+finding type.
+
+Neither ever quotes the content. If a check itself fails, the message carries the
+exception's type name and the SHA-256 of what was inspected, and not the
+exception's message: an exception message routinely quotes the value that caused
+it, and that value is the content.
+
+## Direction and origin
+
+Every validator takes `direction` (`"input"` or `"output"`, default `"output"`)
+and `origin` (default `"model"`). They reach the check as its `Context`, they are
+recorded on every verdict, and some checks decide differently per direction.
+Validating a user's message rather than a model's reply means
+`JamJetChain(checks=[...], direction="input", origin="user")`.
+
+Any `metadata` a Guard passes is forwarded to the check as `Context.metadata`.
+
+## Licence
+
+Apache-2.0.
+
+## The framework this adapter installs makes network calls
+
+`jamjet-guardrails` says on its own front page: no dependencies, no network
+calls, no model downloads. That is true of the core and it stops being true of
+your environment the moment you install this adapter, so it is said here rather
+than left for you to find.
+
+Measured on `guardrails-ai` 0.11.0: it posts usage metrics unless
+`settings.rc.enable_metrics` is false, and it builds an OpenTelemetry batch span
+exporter AT IMPORT whose flush happens at interpreter exit. On a machine with no
+route to the endpoint, that flush is several seconds of OTLP retries at the end
+of every process; on a machine with one, it is a report.
+
+Both are yours to turn off, and the ORDER matters, because the exporter is built
+during import:
+
+```python
+import os
+os.environ["OTEL_SDK_DISABLED"] = "true"   # before importing guardrails
+
+from guardrails import settings
+settings.rc.enable_metrics = False
+settings.disable_tracing = True
+```
+
+`tests/conftest.py` in this package does exactly that, for the same reason.
+
+Nothing in this adapter sends anything anywhere. The spans and messages it
+returns go back to the host in-process.