pbom 0.1.0__tar.gz

pbom-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 [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.

pbom-0.1.0/PKG-INFO

@@ -0,0 +1,139 @@
+Metadata-Version: 2.4
+Name: pbom
+Version: 0.1.0
+Summary: Open-source reference implementation of the PBOM format.
+Author: Eqo
+License: Apache-2.0
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Libraries
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: pydantic>=2.0
+Requires-Dist: click
+Provides-Extra: dev
+Requires-Dist: pytest; extra == "dev"
+Requires-Dist: pytest-cov; extra == "dev"
+Requires-Dist: ruff; extra == "dev"
+Dynamic: license-file
+
+# PBOM
+
+PBOM is the open standard for tamper-evident LLM audit trails. This package is the reference implementation.
+
+[![License: Apache-2.0](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
+![Python 3.11+](https://img.shields.io/badge/python-3.11%2B-3776AB)
+[![CI](https://github.com/eqo/pbom-spec/actions/workflows/ci.yml/badge.svg)](https://github.com/eqo/pbom-spec/actions/workflows/ci.yml)
+
+## What is PBOM?
+
+PBOM (Prompt Bill of Materials) is an open JSON-LD format for recording LLM interactions as tamper-evident records. Each record captures identity, prompt fingerprints, model metadata, response fingerprints, telemetry, and hash links to prior records.
+
+**Security model.** PBOM provides tamper-evidence *relative to an external anchor*. Chain linking makes in-place modification and mid-chain deletion detectable on their own; detecting deliberate rewriting or truncation of the chain requires holding one record hash outside the `.pbom/` directory. Records are unsigned in v1.0.0 — the chain proves linkage, not authorship. See [Security model](docs/spec.md#12-security-model) in the specification for the full treatment.
+
+The goal is: make LLM interactions auditable without locking teams into one provider or one runtime. PBOM gives you verifiable evidence about what was sent and what came back, while keeping storage mode flexible (`fingerprint` vs `forensic`) and extension-friendly.
+
+## Why PBOM?
+
+Software supply chains have the SBOM. Machine-learning systems have the ML-BOM. Both inventory *static* artifacts — code dependencies, model weights, datasets — and neither captures the thing that actually shaped a given LLM output: the prompt, the model version, and the parameters at inference time.
+
+That layer usually lives only in application logs, if it's recorded at all — raw text, often PII-heavy, with no integrity guarantee and no link from one call to the next. When you later need to answer "what exactly did we send, which model answered, and has this record been altered since," logs can't prove it.
+
+PBOM fills that gap at the inference boundary: a per-call record that fingerprints the prompt and response, pins the model, and hash-links to the record before it — so the audit trail is verifiable, not just present.
+
+## Quick Start
+
+```bash
+pip install pbom
+pbom init
+```
+
+```python
+from pbom import PBOMEmitter
+emitter = PBOMEmitter(application_id="demo-app", storage_mode="fingerprint")
+with emitter.commit(system_prompt="You are concise.", user_prompt="Summarize PBOM.") as commit:
+    response_text = call_your_llm()  # your LLM client call
+    record = commit.complete(response_text=response_text, model_id="gpt-4.1")
+print(record.identity.entry_id)
+print(record.commitment.commitment_verified)
+```
+
+```bash
+pbom validate .pbom/
+```
+
+## The Two APIs
+
+- **API 1: `PBOMEmitter.commit(...)` (context manager)**  
+  Pre-inference commitment flow. You commit prompt material before model execution, then complete the record after receiving the response.
+- **API 2: `PBOMEmitter.record(...)` (single call)**  
+  Post-hoc record creation. Useful for existing pipelines, but it does **not** provide pre-inference guarantees.
+
+See the specification and examples for full semantics and edge cases.
+
+## CLI Commands
+
+| Command | Purpose |
+| --- | --- |
+| `pbom init` | Create and initialize a local PBOM chain directory. |
+| `pbom validate <dir>` | Validate chain integrity and commitment status for a PBOM directory. |
+| `pbom status <dir>` | Show chain status summary (record count, head info). |
+| `pbom export-schema <path>` | Export the PBOM JSON Schema to a file. |
+| `pbom install-skill [--force]` | Install the pbom skill file into `.claude/skills/pbom/` and add a pbom grounding note to `CLAUDE.md`. |
+
+`pbom install-skill` is for teams using an agentic coding tool (like Claude Code) to instrument pbom. It writes two things into your project: the skill file at `.claude/skills/pbom/SKILL.md`, and a short grounding note appended to `CLAUDE.md` (created if absent). Both operations are safe to re-run: the skill file is not overwritten unless you pass `--force`, and the `CLAUDE.md` note is only added once.
+
+## What's Captured
+
+| Section | What it captures | Presence |
+| --- | --- | --- |
+| `identity` | Record ID, chain sequence, timestamps, previous hash pointer | Always present |
+| `principal` | Emitting application and SDK identity/version | Always present |
+| `commitment` | Commitment mode, nonce, commitment hash, verification timing | Always present |
+| `prompt` | Prompt hashes, token counts, optional raw prompt text | Always present |
+| `inference` | Model ID and optional runtime inference settings | Always present |
+| `response` | Response hash, token counts, stop reason, optional raw text | Always present |
+| `telemetry` | Optional end-to-end and inference latency measurements | Always present |
+| `context_management` | Optional history/cache metadata | Optional (nullable) |
+| `provider_metadata` | Optional provider request metadata | Optional (nullable) |
+| `structural_analysis` | Optional machine-readable output analysis | Optional (nullable) |
+| `action_primitives` | Canonical action detections with confidence/evidence | Optional (empty list default) |
+| `extensions` | Implementation-specific metadata outside core PBOM fields | Always present |
+| `storage_mode` | Whether raw content is omitted (`fingerprint`) or retained (`forensic`) | Always present |
+
+## What This Package Is NOT
+
+- **Not an LLM client wrapper**  
+  You call your model/provider SDK directly, then call PBOM to commit/record results.
+- **Not a policy engine**  
+  No gating or risk-scoring decisions are performed here. If you want that layer, build it separately and store outputs in `extensions`.
+- **Not a hosted service**  
+  PBOM records are local JSON files. You own storage, transport, and retention.
+
+If you want all-in-one model routing, enforcement, and hosted analytics today, this is not that.
+
+## Documentation
+
+- [PBOM specification (`docs/spec.md`)](docs/spec.md)
+- [Field-by-field guide (`docs/fields.md`)](docs/fields.md)
+- [Converting message lists (`docs/canonical.md`)](docs/canonical.md)
+- [Examples (`examples/`)](examples/)
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md).
+
+## License
+
+Apache 2.0. See [LICENSE](LICENSE).
+
+---
+
+Built and maintained by Eqo. PBOM is an open standard; anyone may implement it.

pbom-0.1.0/README.md

@@ -0,0 +1,113 @@
+# PBOM
+
+PBOM is the open standard for tamper-evident LLM audit trails. This package is the reference implementation.
+
+[![License: Apache-2.0](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
+![Python 3.11+](https://img.shields.io/badge/python-3.11%2B-3776AB)
+[![CI](https://github.com/eqo/pbom-spec/actions/workflows/ci.yml/badge.svg)](https://github.com/eqo/pbom-spec/actions/workflows/ci.yml)
+
+## What is PBOM?
+
+PBOM (Prompt Bill of Materials) is an open JSON-LD format for recording LLM interactions as tamper-evident records. Each record captures identity, prompt fingerprints, model metadata, response fingerprints, telemetry, and hash links to prior records.
+
+**Security model.** PBOM provides tamper-evidence *relative to an external anchor*. Chain linking makes in-place modification and mid-chain deletion detectable on their own; detecting deliberate rewriting or truncation of the chain requires holding one record hash outside the `.pbom/` directory. Records are unsigned in v1.0.0 — the chain proves linkage, not authorship. See [Security model](docs/spec.md#12-security-model) in the specification for the full treatment.
+
+The goal is: make LLM interactions auditable without locking teams into one provider or one runtime. PBOM gives you verifiable evidence about what was sent and what came back, while keeping storage mode flexible (`fingerprint` vs `forensic`) and extension-friendly.
+
+## Why PBOM?
+
+Software supply chains have the SBOM. Machine-learning systems have the ML-BOM. Both inventory *static* artifacts — code dependencies, model weights, datasets — and neither captures the thing that actually shaped a given LLM output: the prompt, the model version, and the parameters at inference time.
+
+That layer usually lives only in application logs, if it's recorded at all — raw text, often PII-heavy, with no integrity guarantee and no link from one call to the next. When you later need to answer "what exactly did we send, which model answered, and has this record been altered since," logs can't prove it.
+
+PBOM fills that gap at the inference boundary: a per-call record that fingerprints the prompt and response, pins the model, and hash-links to the record before it — so the audit trail is verifiable, not just present.
+
+## Quick Start
+
+```bash
+pip install pbom
+pbom init
+```
+
+```python
+from pbom import PBOMEmitter
+emitter = PBOMEmitter(application_id="demo-app", storage_mode="fingerprint")
+with emitter.commit(system_prompt="You are concise.", user_prompt="Summarize PBOM.") as commit:
+    response_text = call_your_llm()  # your LLM client call
+    record = commit.complete(response_text=response_text, model_id="gpt-4.1")
+print(record.identity.entry_id)
+print(record.commitment.commitment_verified)
+```
+
+```bash
+pbom validate .pbom/
+```
+
+## The Two APIs
+
+- **API 1: `PBOMEmitter.commit(...)` (context manager)**  
+  Pre-inference commitment flow. You commit prompt material before model execution, then complete the record after receiving the response.
+- **API 2: `PBOMEmitter.record(...)` (single call)**  
+  Post-hoc record creation. Useful for existing pipelines, but it does **not** provide pre-inference guarantees.
+
+See the specification and examples for full semantics and edge cases.
+
+## CLI Commands
+
+| Command | Purpose |
+| --- | --- |
+| `pbom init` | Create and initialize a local PBOM chain directory. |
+| `pbom validate <dir>` | Validate chain integrity and commitment status for a PBOM directory. |
+| `pbom status <dir>` | Show chain status summary (record count, head info). |
+| `pbom export-schema <path>` | Export the PBOM JSON Schema to a file. |
+| `pbom install-skill [--force]` | Install the pbom skill file into `.claude/skills/pbom/` and add a pbom grounding note to `CLAUDE.md`. |
+
+`pbom install-skill` is for teams using an agentic coding tool (like Claude Code) to instrument pbom. It writes two things into your project: the skill file at `.claude/skills/pbom/SKILL.md`, and a short grounding note appended to `CLAUDE.md` (created if absent). Both operations are safe to re-run: the skill file is not overwritten unless you pass `--force`, and the `CLAUDE.md` note is only added once.
+
+## What's Captured
+
+| Section | What it captures | Presence |
+| --- | --- | --- |
+| `identity` | Record ID, chain sequence, timestamps, previous hash pointer | Always present |
+| `principal` | Emitting application and SDK identity/version | Always present |
+| `commitment` | Commitment mode, nonce, commitment hash, verification timing | Always present |
+| `prompt` | Prompt hashes, token counts, optional raw prompt text | Always present |
+| `inference` | Model ID and optional runtime inference settings | Always present |
+| `response` | Response hash, token counts, stop reason, optional raw text | Always present |
+| `telemetry` | Optional end-to-end and inference latency measurements | Always present |
+| `context_management` | Optional history/cache metadata | Optional (nullable) |
+| `provider_metadata` | Optional provider request metadata | Optional (nullable) |
+| `structural_analysis` | Optional machine-readable output analysis | Optional (nullable) |
+| `action_primitives` | Canonical action detections with confidence/evidence | Optional (empty list default) |
+| `extensions` | Implementation-specific metadata outside core PBOM fields | Always present |
+| `storage_mode` | Whether raw content is omitted (`fingerprint`) or retained (`forensic`) | Always present |
+
+## What This Package Is NOT
+
+- **Not an LLM client wrapper**  
+  You call your model/provider SDK directly, then call PBOM to commit/record results.
+- **Not a policy engine**  
+  No gating or risk-scoring decisions are performed here. If you want that layer, build it separately and store outputs in `extensions`.
+- **Not a hosted service**  
+  PBOM records are local JSON files. You own storage, transport, and retention.
+
+If you want all-in-one model routing, enforcement, and hosted analytics today, this is not that.
+
+## Documentation
+
+- [PBOM specification (`docs/spec.md`)](docs/spec.md)
+- [Field-by-field guide (`docs/fields.md`)](docs/fields.md)
+- [Converting message lists (`docs/canonical.md`)](docs/canonical.md)
+- [Examples (`examples/`)](examples/)
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md).
+
+## License
+
+Apache 2.0. See [LICENSE](LICENSE).
+
+---
+
+Built and maintained by Eqo. PBOM is an open standard; anyone may implement it.

pbom-0.1.0/pyproject.toml

@@ -0,0 +1,48 @@
+[build-system]
+requires = ["setuptools>=68", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "pbom"
+version = "0.1.0"
+description = "Open-source reference implementation of the PBOM format."
+readme = "README.md"
+requires-python = ">=3.10"
+license = { text = "Apache-2.0" }
+authors = [
+  { name = "Eqo" }
+]
+dependencies = [
+  "pydantic>=2.0",
+  "click"
+]
+classifiers = [
+  "Development Status :: 3 - Alpha",
+  "Intended Audience :: Developers",
+  "License :: OSI Approved :: Apache Software License",
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3.10",
+  "Programming Language :: Python :: 3.11",
+  "Programming Language :: Python :: 3.12",
+  "Topic :: Software Development :: Libraries",
+  "Typing :: Typed"
+]
+
+[project.optional-dependencies]
+dev = [
+  "pytest",
+  "pytest-cov",
+  "ruff"
+]
+
+[project.scripts]
+pbom = "pbom.cli:main"
+
+[tool.setuptools]
+package-dir = { "" = "src" }
+
+[tool.setuptools.package-data]
+pbom = ["skill/SKILL.md"]
+
+[tool.setuptools.packages.find]
+where = ["src"]

pbom-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

pbom-0.1.0/src/pbom/__init__.py

@@ -0,0 +1,30 @@
+"""Public API surface for the PBOM package."""
+
+from .canonical import canonicalize_messages
+from .exceptions import UnsupportedMessageShapeError
+from pbom.emitter import PBOMEmitter
+from pbom.exceptions import (
+    ChainCorruptedError,
+    InvalidCommitmentError,
+    PBOMError,
+    SchemaValidationError,
+)
+from pbom.schema import PBOMRecord
+from pbom.validator import ValidationResult, validate_chain, validate_commitment
+
+__version__ = "0.1.0"
+
+__all__ = [
+    "ChainCorruptedError",
+    "InvalidCommitmentError",
+    "PBOMEmitter",
+    "PBOMError",
+    "PBOMRecord",
+    "UnsupportedMessageShapeError",
+    "SchemaValidationError",
+    "ValidationResult",
+    "__version__",
+    "canonicalize_messages",
+    "validate_chain",
+    "validate_commitment",
+]