voltry-probe 0.1.0__tar.gz

voltry_probe-0.1.0/.gitignore

@@ -0,0 +1,50 @@
+# --- OS / editor ---
+.DS_Store
+*.swp
+.idea/
+.vscode/
+
+# --- Python ---
+__pycache__/
+*.py[cod]
+*.egg-info/
+.eggs/
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+.coverage
+.coverage.*
+coverage.xml
+htmlcov/
+.venv/
+venv/
+dist/
+build/
+
+# --- Node / TS ---
+node_modules/
+.next/
+.turbo/
+*.tsbuildinfo
+out/
+
+# --- Generated token outputs are committed? No — regenerated in CI ---
+packages/tokens/dist/
+apps/web/.next/
+
+# --- Local secrets (never committed; enforced by hooks) ---
+.env
+.env.*
+*.pem
+*.key
+
+# --- SBOM / scan artifacts (regenerated in CI) ---
+sbom*.json
+sbom*.xml
+trivy-results.*
+
+# Next.js generated
+next-env.d.ts
+
+# hypothesis example database
+.hypothesis/

voltry_probe-0.1.0/CHANGELOG.md

@@ -0,0 +1,34 @@
+# Changelog
+
+All notable changes to `voltry-probe` are documented here. The format follows
+Keep a Changelog.
+
+## [0.1.0] - 2026-07-02
+
+First public release.
+
+- `voltry scan`: read-only capture from NVML, DCGM, Redfish, and the NVIDIA
+  attestation chain into a signed evidence bundle. Works fully offline and
+  air-gapped. Live readers behind the `[hardware]` extra; fixtures and
+  simulator supported everywhere.
+- `voltry cert`: renders a bundle to a self-contained offline HTML
+  certificate. Measured facts and modeled estimates are separate blocks;
+  exposure renders "Not Assessed" without facility instrumentation. The command
+  verifies the bundle signature and renders a prominent UNVERIFIED watermark
+  (with a stderr warning) for any bundle whose signature does not validate, so
+  the offline certificate can never look authoritative without cryptographic
+  backing.
+- `voltry submit`: separate, explicit, opt-in submission client behind the
+  `[submit]` extra. Scan and cert never use the network.
+- `voltry --version` reports the installed version; malformed inputs to `cert`
+  produce a clean error and a non-zero exit, never a raw traceback.
+- Readers refuse to fabricate any measured fact. Every counter the certificate
+  renders as a Block-2 measured fact — ECC (volatile and aggregate), spare-row
+  headroom, and retired pages — must have actually been read at the leaf level;
+  an absent, empty, or partially-populated block is rejected rather than
+  certified as "0 errors" / "512/512 spare rows" / "0 retired pages". A
+  genuinely-measured zero is still a valid clean read. The live reader now
+  captures aggregate (lifetime) ECC and retired-page counts.
+- Attestation verdicts reflect real chain state (VERIFIED, FAILED, UNVERIFIED,
+  FALLBACK); never a stubbed pass.
+- Python 3.10 through 3.13. Typed (`py.typed`).

voltry_probe-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,22 @@
+# voltry-probe
+
+The open, **read-only** Voltry agent. PyPI `voltry-probe`, import `voltry_probe`, CLI
+`voltry` (Stage 5).
+
+Stage 3 (Read mode):
+
+- `voltry_probe/sources/` — read-only capture (live NVML on hardware via the `[hardware]`
+  extra, or captured fixtures / the DCGM simulator). No device-mutating call anywhere.
+- `voltry_probe/readers/` — pure mappers: verbatim NVML/DCGM/Redfish payloads → typed
+  evidence-schema blocks. Spare-rows-remaining derived against the fixed 512 cap.
+- `voltry_probe/attestation/` — **real** ECDSA P-384 verification of the device-identity
+  chain (root → device key → signed measurement) + VBIOS re-flash detection. Never a
+  stubbed PASS: `UNVERIFIED` with no root, `FAILED` on a broken chain, `FALLBACK` (lower
+  confidence, marked) for parts without a hardware root.
+- `voltry_probe/evidence/` — thin adapter assembling a signed Read-mode (Bronze) bundle.
+
+Read + cert work fully offline; submission is a separate, opt-in step (Stage 5).
+
+```bash
+uv run pytest          # readers, attestation, builder, read-only invariant
+```

voltry_probe-0.1.0/Dockerfile

@@ -0,0 +1,40 @@
+# syntax=docker/dockerfile:1
+#
+# Voltry Probe container — the read-only agent on the NVIDIA CUDA base.
+# Multi-arch (amd64 + arm64; arm64 covers Grace). Build from the REPO ROOT so the
+# evidence-schema contract (a workspace sibling, not on PyPI) is in the build context:
+#
+#   docker buildx build -f packages/voltry-probe/Dockerfile \
+#     --platform linux/amd64,linux/arm64 \
+#     -t ghcr.io/voltry/voltry-probe:0.1.0 .
+#
+# Collects NO PII (NGC GDPR posture): identity is device-level only; account linkage is
+# server-side. No secrets are baked in (no keys/.env copied; see .dockerignore). Image is
+# signed (cosign) and CVE-scanned (Trivy) in CI.
+ARG CUDA_TAG=12.6.2-base-ubuntu22.04
+FROM nvcr.io/nvidia/cuda:${CUDA_TAG}
+
+# Pinned uv binary from the official image (no `curl | sh`).
+COPY --from=ghcr.io/astral-sh/uv:0.11.21 /uv /uvx /usr/local/bin/
+
+ENV DEBIAN_FRONTEND=noninteractive \
+    PYTHONDONTWRITEBYTECODE=1 \
+    PYTHONUNBUFFERED=1
+
+RUN apt-get update \
+    && apt-get install -y --no-install-recommends python3.12 python3.12-venv ca-certificates \
+    && rm -rf /var/lib/apt/lists/*
+
+WORKDIR /opt/voltry
+# evidence-schema (the contract) must be installed before the probe that depends on it.
+COPY packages/evidence-schema /opt/voltry/evidence-schema
+COPY packages/voltry-probe    /opt/voltry/voltry-probe
+RUN uv pip install --system --python python3.12 ./evidence-schema ./voltry-probe
+
+# Run unprivileged; the agent is read-only and collects no PII.
+RUN useradd --create-home --uid 10001 voltry
+USER voltry
+WORKDIR /home/voltry
+
+ENTRYPOINT ["voltry"]
+CMD ["--help"]

voltry_probe-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 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 2026 Voltry
+
+   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.

voltry_probe-0.1.0/PKG-INFO

@@ -0,0 +1,118 @@
+Metadata-Version: 2.4
+Name: voltry-probe
+Version: 0.1.0
+Summary: Voltry Probe — the open, read-only agent. Reads NVML/DCGM/Redfish/attestation into a signed evidence bundle and renders the offline certificate.
+License-Expression: Apache-2.0
+License-File: LICENSE
+Classifier: Operating System :: OS Independent
+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: Typing :: Typed
+Requires-Python: >=3.10
+Requires-Dist: cryptography<50,>=44
+Requires-Dist: pydantic<3,>=2.11
+Requires-Dist: rfc8785<0.2,>=0.1.4
+Requires-Dist: typer<1,>=0.12
+Requires-Dist: voltry-evidence-schema<2,>=1
+Provides-Extra: hardware
+Requires-Dist: nvidia-ml-py<13,>=12.560; extra == 'hardware'
+Requires-Dist: sushy<6,>=5.0; extra == 'hardware'
+Provides-Extra: submit
+Requires-Dist: httpx<1,>=0.27; extra == 'submit'
+Description-Content-Type: text/markdown
+
+# Voltry Probe
+
+Voltry Probe is an open, read-only agent that produces a signed condition and
+provenance record for data-center GPUs. It reads what the hardware already
+exposes (NVML, DCGM, Redfish, and the NVIDIA attestation chain), binds the
+readings to the device's fused cryptographic identity, and renders a
+self-contained certificate you can open with no network at all.
+
+It never states or implies what your hardware is worth. It records what the
+hardware is.
+
+## Install
+
+```bash
+pipx install voltry-probe
+```
+
+Requires Python 3.10 or newer. Stock DGX OS and Ubuntu 22.04 hosts work as-is.
+`pip install voltry-probe` inside a virtualenv works too.
+
+Optional extras:
+
+```bash
+pipx install "voltry-probe[hardware]"   # live NVML + Redfish readers
+pipx install "voltry-probe[submit]"     # the opt-in submission client
+```
+
+Without `[hardware]` the probe runs against captured fixtures and simulators,
+which is all you need to evaluate it.
+
+## Sixty seconds to a certificate
+
+```bash
+# 1. Scan. Read-only, works fully offline and air-gapped.
+#    Reads live hardware; signs with your operator key.
+voltry scan --signing-key operator.pem --out bundle.json
+
+# 2. Render. A self-contained HTML certificate, no network needed to view.
+voltry cert bundle.json --out cert.html
+```
+
+Just evaluating, with no GPU and no key of your own? Point `scan` at a captured
+sample and sign with a throwaway key:
+
+```bash
+voltry scan --fixture sample.json --ephemeral-key --out bundle.json
+voltry cert bundle.json --out cert.html
+```
+
+That is the whole loop. `voltry submit` exists as a separate, explicit,
+opt-in step; scanning and rendering never phone home.
+
+## What read-only means
+
+The probe never writes to, resets, reconfigures, or stress-tests a device
+during a scan. You can run it on a live production fleet. Functional
+qualification (which does exercise the device) is a separate mode behind an
+explicit flag, never part of a read-only `scan`.
+
+## What the certificate says, and what it does not
+
+The certificate keeps measured facts and modeled estimates in separate blocks
+that never look alike:
+
+- Deterministic gates: authenticity, firmware integrity, functional and
+  sanitization results. Pass or fail, no model in the loop.
+- Measured condition: ECC and Xid history, retired and remapped pages, spare
+  rows remaining, throttle and clock behavior. Raw values against published
+  thresholds.
+- Provenance: certification history on the device's permanent identity,
+  append-only. A failed attempt stays on the record; cherry-picking is
+  structurally impossible.
+
+It never contains a price, a dollar figure, or a lifetime guarantee. Power-chain
+exposure reads "Not Assessed" unless the facility itself was instrumented; it
+is never inferred from board power.
+
+## Verifying a bundle yourself
+
+Every bundle is signed (ECDSA P-384 over RFC 8785 canonical JSON) and can be
+verified by anyone with the `voltry-evidence-schema` package:
+
+```python
+import json
+from evidence_schema import EvidenceBundle, verify_bundle
+
+bundle = EvidenceBundle.model_validate(json.load(open("bundle.json")))
+assert verify_bundle(bundle)
+```
+
+## License
+
+Apache-2.0.

voltry_probe-0.1.0/README.md

@@ -0,0 +1,93 @@
+# Voltry Probe
+
+Voltry Probe is an open, read-only agent that produces a signed condition and
+provenance record for data-center GPUs. It reads what the hardware already
+exposes (NVML, DCGM, Redfish, and the NVIDIA attestation chain), binds the
+readings to the device's fused cryptographic identity, and renders a
+self-contained certificate you can open with no network at all.
+
+It never states or implies what your hardware is worth. It records what the
+hardware is.
+
+## Install
+
+```bash
+pipx install voltry-probe
+```
+
+Requires Python 3.10 or newer. Stock DGX OS and Ubuntu 22.04 hosts work as-is.
+`pip install voltry-probe` inside a virtualenv works too.
+
+Optional extras:
+
+```bash
+pipx install "voltry-probe[hardware]"   # live NVML + Redfish readers
+pipx install "voltry-probe[submit]"     # the opt-in submission client
+```
+
+Without `[hardware]` the probe runs against captured fixtures and simulators,
+which is all you need to evaluate it.
+
+## Sixty seconds to a certificate
+
+```bash
+# 1. Scan. Read-only, works fully offline and air-gapped.
+#    Reads live hardware; signs with your operator key.
+voltry scan --signing-key operator.pem --out bundle.json
+
+# 2. Render. A self-contained HTML certificate, no network needed to view.
+voltry cert bundle.json --out cert.html
+```
+
+Just evaluating, with no GPU and no key of your own? Point `scan` at a captured
+sample and sign with a throwaway key:
+
+```bash
+voltry scan --fixture sample.json --ephemeral-key --out bundle.json
+voltry cert bundle.json --out cert.html
+```
+
+That is the whole loop. `voltry submit` exists as a separate, explicit,
+opt-in step; scanning and rendering never phone home.
+
+## What read-only means
+
+The probe never writes to, resets, reconfigures, or stress-tests a device
+during a scan. You can run it on a live production fleet. Functional
+qualification (which does exercise the device) is a separate mode behind an
+explicit flag, never part of a read-only `scan`.
+
+## What the certificate says, and what it does not
+
+The certificate keeps measured facts and modeled estimates in separate blocks
+that never look alike:
+
+- Deterministic gates: authenticity, firmware integrity, functional and
+  sanitization results. Pass or fail, no model in the loop.
+- Measured condition: ECC and Xid history, retired and remapped pages, spare
+  rows remaining, throttle and clock behavior. Raw values against published
+  thresholds.
+- Provenance: certification history on the device's permanent identity,
+  append-only. A failed attempt stays on the record; cherry-picking is
+  structurally impossible.
+
+It never contains a price, a dollar figure, or a lifetime guarantee. Power-chain
+exposure reads "Not Assessed" unless the facility itself was instrumented; it
+is never inferred from board power.
+
+## Verifying a bundle yourself
+
+Every bundle is signed (ECDSA P-384 over RFC 8785 canonical JSON) and can be
+verified by anyone with the `voltry-evidence-schema` package:
+
+```python
+import json
+from evidence_schema import EvidenceBundle, verify_bundle
+
+bundle = EvidenceBundle.model_validate(json.load(open("bundle.json")))
+assert verify_bundle(bundle)
+```
+
+## License
+
+Apache-2.0.

voltry_probe-0.1.0/pyproject.toml

@@ -0,0 +1,71 @@
+[project]
+name = "voltry-probe"
+version = "0.1.0"
+description = "Voltry Probe — the open, read-only agent. Reads NVML/DCGM/Redfish/attestation into a signed evidence bundle and renders the offline certificate."
+requires-python = ">=3.10"
+license = "Apache-2.0"
+readme = "README.md"
+classifiers = [
+  "Programming Language :: Python :: 3.10",
+  "Programming Language :: Python :: 3.11",
+  "Programming Language :: Python :: 3.12",
+  "Programming Language :: Python :: 3.13",
+  "Typing :: Typed",
+  "Operating System :: OS Independent",
+]
+dependencies = [
+  "voltry-evidence-schema>=1,<2",
+  "pydantic>=2.11,<3",
+  "cryptography>=44,<50",
+  "rfc8785>=0.1.4,<0.2",
+  "typer>=0.12,<1",
+]
+
+[project.scripts]
+voltry = "voltry_probe.cli:main"
+
+[project.optional-dependencies]
+# Real-hardware readers. Lazy-imported by sources/live.py; absent on dev/CI, where the
+# probe runs against captured fixtures / the DCGM simulator (read-only either way).
+hardware = [
+  "nvidia-ml-py>=12.560,<13",
+  "sushy>=5.0,<6",
+]
+# The network client for `voltry submit` only. Kept optional so scan/cert stay offline
+# and dependency-light (§1.7 federated-by-default).
+submit = [
+  "httpx>=0.27,<1",
+]
+
+# Published on PyPI with a 3.10 floor (ADR-0003): lint for the floor, not the
+# workspace default. `extend` keeps the root select/per-file-ignores rules.
+[tool.ruff]
+extend = "../../pyproject.toml"
+target-version = "py310"
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["voltry_probe"]
+
+# The sdist must not ship the internal agent constitution or local caches to PyPI.
+[tool.hatch.build.targets.sdist]
+exclude = ["CLAUDE.md", "AGENTS.md", ".claude", ".hypothesis", ".pytest_cache", ".ruff_cache"]
+
+# voltry-evidence-schema resolves from the workspace locally and from PyPI when published.
+[tool.uv.sources]
+voltry-evidence-schema = { workspace = true }
+
+[tool.pytest.ini_options]
+addopts = "-q --import-mode=importlib"
+testpaths = ["tests"]
+filterwarnings = ["error"]
+
+[tool.coverage.run]
+branch = true
+source = ["voltry_probe"]
+
+[tool.coverage.report]
+exclude_also = ["if TYPE_CHECKING:", "raise NotImplementedError", "@(abc\\.)?abstractmethod"]