halo-record 0.1.0__tar.gz

halo_record-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 Brian Kuan

halo_record-0.1.0/PKG-INFO

@@ -0,0 +1,140 @@
+Metadata-Version: 2.4
+Name: halo-record
+Version: 0.1.0
+Summary: Open, tamper-evident runtime records for AI agents: the Halo Runtime Record format, with a dependency-free conformance verifier.
+Author: Brian Kuan
+License: Apache-2.0
+Project-URL: Homepage, https://halo.dev
+Project-URL: Specification, https://halo.dev/spec/v0.1/
+Keywords: ai,agents,audit,tamper-evident,attestation,compliance
+Classifier: Development Status :: 3 - Alpha
+Classifier: Programming Language :: Python :: 3
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Topic :: Security
+Classifier: Topic :: System :: Logging
+Requires-Python: >=3.8
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Dynamic: license-file
+
+# halo-record
+
+Tamper-evident **runtime records for AI agents**: the audit trail the vendor runs but cannot edit.
+
+Every action your agent takes (tool calls, model calls, data access, approvals) becomes one record in an append-only, hash-chained log. Any party can verify the log was never altered, without trusting whoever produced it. When a customer's security team asks "what did your agent do with our data?", you hand them a link instead of a paragraph. Security reviews already ask AI questions next to the SOC 2 checklist, and today a written assurance still passes. The bet behind this project is that it won't for long.
+
+The record format is open and free to implement. This package is the reference implementation: recorder, verifier, witness client, and report server.
+
+## Why you can trust this code
+
+You are being asked to put a recorder inside your agent. You should not take that on faith:
+
+- **Zero runtime dependencies.** Standard library only. `pip install halo-record` installs exactly one package.
+- **No network calls**, except the witness, which is opt-in and receives only a record count and a chain fingerprint. Record contents never leave your infrastructure.
+- **Raw inputs never enter a record.** Arguments are hashed and summarized through a redaction pass before writing. Secrets and personal data stay out by construction.
+- **Small enough to audit.** ~3,800 lines of Python. Read all of it in an afternoon.
+- **Apache-2.0.**
+
+## 60-second demo
+
+No agent required. With [uv](https://docs.astral.sh/uv/), nothing to install:
+
+```
+uvx --from halo-record halo demo --serve
+```
+
+or the classic way:
+
+```
+pip install halo-record
+halo demo --serve
+```
+
+Either one scaffolds a fictional support-agent vendor with two customers, witnesses the chains, serves their gated Runtime Reports, and opens the operator console in your browser. Then try the tamper test: delete a line from one of the `.jsonl` files and reload. The report catches it.
+
+## Record your own agent
+
+One line at the boundary:
+
+```python
+from halo import trace
+
+agent = trace(run_my_agent)   # wraps your entrypoint; records every tool call
+```
+
+or use the adapter for what you already run (see the matrix below). Then render the report:
+
+```
+halo report audit.jsonl -o report.html    # one chain -> self-verifying HTML
+halo serve ./records --port 8721          # all tenants, gated per customer
+```
+
+The quickstart ends when you are looking at your own agent's Runtime Report in a browser. If you got a JSONL file and no report, something is wrong: open an issue.
+
+## Connect to what you already run
+
+| Captured at the boundary | Ingested from existing telemetry |
+|---|---|
+| Native recorder (`from halo import trace`) | OpenTelemetry GenAI spans |
+| MCP interceptor | LiteLLM callbacks |
+| LangChain / LangGraph callback | Langfuse export |
+| OpenAI Agents SDK hooks | Any gateway / reverse-proxy log |
+| Claude Code / Claude Agent SDK hook | |
+
+Every record carries a `source` tag, so the report discloses how each piece of evidence was collected. Captured and ingested records live in the same chain.
+
+Anything that emits OpenTelemetry GenAI spans (CrewAI, LlamaIndex, and most agent frameworks with OTel instrumentation) lands in the chain through the OTel adapter, and the [TypeScript package](https://github.com/bkuan001/halo-record-ts) ships native adapters for the Vercel AI SDK and the JS agent ecosystem. Missing an adapter for your stack? Open an issue. Most adapters are about a hundred lines.
+
+## Integrity vs. completeness (read this part)
+
+A self-held chain proves **integrity**: nothing was edited or reordered after the fact. It cannot prove **completeness**: the operator of a recorder can delete the bad day and re-seal the chain, or never write a record at all, and the chain stays internally consistent.
+
+Completeness requires a party outside the operator's control holding periodic fingerprints of the chain (a count and a head hash, nothing else). That is the witness:
+
+```
+halo anchor audit.jsonl --witness witness.jsonl     # local witness file
+halo anchor audit.jsonl --check                     # completeness verdict
+```
+
+Anyone can run a witness. A witness you run yourself proves integrity to *you*; proving completeness to *your customer* requires a witness they have reason to trust. The protocol is open either way.
+
+A hosted, recognized witness is how this project will sustain itself. Early access: bkuan001@gmail.com.
+
+## Where this sits in a compliance stack
+
+halo-record is an evidence layer, not a certification. It produces the artifact that assessment frameworks keep asking for in different words:
+
+- **Security questionnaires and SOC 2 reviews:** answer the AI sections with a verifiable Runtime Report instead of screenshots and prose.
+- **AIUC-1:** continuous runtime evidence for agent-behavior requirements, instead of evidence reconstructed at audit time.
+- **EU AI Act:** logging and record-keeping obligations for high-risk AI systems.
+- **ISO 42001 / NIST AI RMF:** the operational evidence behind management-system controls.
+
+None of this certifies anything by itself. It gives your assessor something verifiable to look at.
+
+## CLI
+
+```
+halo verify   validate schema + hash chain (non-zero exit on failure; CI-friendly)
+halo report   render a chain as a self-verifying HTML Runtime Report
+halo serve    serve per-tenant reports over HTTP, access-scoped per customer
+halo grant    designate a report recipient (email or domain)
+halo anchor   witness a chain head, or --check completeness
+halo demo     scaffold the full vendor demo (record -> witness -> gated report)
+halo sample   emit a valid example log
+halo hash     canonical sha256 of a JSON value
+halo hook     Claude Code PostToolUse hook
+```
+
+## Integrity model
+
+To compute a record's hash: take the record excluding `integrity.hash`, with `integrity.prev_hash` set to the previous record's hash; canonicalize with RFC 8785 (JSON Canonicalization Scheme); SHA-256 the bytes. The first record's `prev_hash` is 64 zeros. Verification recomputes every hash and checks every link. No secret required; that is the point.
+
+Full field reference: [`halo-record.schema.json`](src/halo_record/halo-record.schema.json).
+
+## TypeScript
+
+The same recorder ships for Node: [`halo-record-ts`](https://github.com/bkuan001/halo-record-ts). Same chain format, same witness protocol. Records written in either language verify with either verifier.
+
+## License
+
+Apache-2.0

halo_record-0.1.0/README.md

@@ -0,0 +1,121 @@
+# halo-record
+
+Tamper-evident **runtime records for AI agents**: the audit trail the vendor runs but cannot edit.
+
+Every action your agent takes (tool calls, model calls, data access, approvals) becomes one record in an append-only, hash-chained log. Any party can verify the log was never altered, without trusting whoever produced it. When a customer's security team asks "what did your agent do with our data?", you hand them a link instead of a paragraph. Security reviews already ask AI questions next to the SOC 2 checklist, and today a written assurance still passes. The bet behind this project is that it won't for long.
+
+The record format is open and free to implement. This package is the reference implementation: recorder, verifier, witness client, and report server.
+
+## Why you can trust this code
+
+You are being asked to put a recorder inside your agent. You should not take that on faith:
+
+- **Zero runtime dependencies.** Standard library only. `pip install halo-record` installs exactly one package.
+- **No network calls**, except the witness, which is opt-in and receives only a record count and a chain fingerprint. Record contents never leave your infrastructure.
+- **Raw inputs never enter a record.** Arguments are hashed and summarized through a redaction pass before writing. Secrets and personal data stay out by construction.
+- **Small enough to audit.** ~3,800 lines of Python. Read all of it in an afternoon.
+- **Apache-2.0.**
+
+## 60-second demo
+
+No agent required. With [uv](https://docs.astral.sh/uv/), nothing to install:
+
+```
+uvx --from halo-record halo demo --serve
+```
+
+or the classic way:
+
+```
+pip install halo-record
+halo demo --serve
+```
+
+Either one scaffolds a fictional support-agent vendor with two customers, witnesses the chains, serves their gated Runtime Reports, and opens the operator console in your browser. Then try the tamper test: delete a line from one of the `.jsonl` files and reload. The report catches it.
+
+## Record your own agent
+
+One line at the boundary:
+
+```python
+from halo import trace
+
+agent = trace(run_my_agent)   # wraps your entrypoint; records every tool call
+```
+
+or use the adapter for what you already run (see the matrix below). Then render the report:
+
+```
+halo report audit.jsonl -o report.html    # one chain -> self-verifying HTML
+halo serve ./records --port 8721          # all tenants, gated per customer
+```
+
+The quickstart ends when you are looking at your own agent's Runtime Report in a browser. If you got a JSONL file and no report, something is wrong: open an issue.
+
+## Connect to what you already run
+
+| Captured at the boundary | Ingested from existing telemetry |
+|---|---|
+| Native recorder (`from halo import trace`) | OpenTelemetry GenAI spans |
+| MCP interceptor | LiteLLM callbacks |
+| LangChain / LangGraph callback | Langfuse export |
+| OpenAI Agents SDK hooks | Any gateway / reverse-proxy log |
+| Claude Code / Claude Agent SDK hook | |
+
+Every record carries a `source` tag, so the report discloses how each piece of evidence was collected. Captured and ingested records live in the same chain.
+
+Anything that emits OpenTelemetry GenAI spans (CrewAI, LlamaIndex, and most agent frameworks with OTel instrumentation) lands in the chain through the OTel adapter, and the [TypeScript package](https://github.com/bkuan001/halo-record-ts) ships native adapters for the Vercel AI SDK and the JS agent ecosystem. Missing an adapter for your stack? Open an issue. Most adapters are about a hundred lines.
+
+## Integrity vs. completeness (read this part)
+
+A self-held chain proves **integrity**: nothing was edited or reordered after the fact. It cannot prove **completeness**: the operator of a recorder can delete the bad day and re-seal the chain, or never write a record at all, and the chain stays internally consistent.
+
+Completeness requires a party outside the operator's control holding periodic fingerprints of the chain (a count and a head hash, nothing else). That is the witness:
+
+```
+halo anchor audit.jsonl --witness witness.jsonl     # local witness file
+halo anchor audit.jsonl --check                     # completeness verdict
+```
+
+Anyone can run a witness. A witness you run yourself proves integrity to *you*; proving completeness to *your customer* requires a witness they have reason to trust. The protocol is open either way.
+
+A hosted, recognized witness is how this project will sustain itself. Early access: bkuan001@gmail.com.
+
+## Where this sits in a compliance stack
+
+halo-record is an evidence layer, not a certification. It produces the artifact that assessment frameworks keep asking for in different words:
+
+- **Security questionnaires and SOC 2 reviews:** answer the AI sections with a verifiable Runtime Report instead of screenshots and prose.
+- **AIUC-1:** continuous runtime evidence for agent-behavior requirements, instead of evidence reconstructed at audit time.
+- **EU AI Act:** logging and record-keeping obligations for high-risk AI systems.
+- **ISO 42001 / NIST AI RMF:** the operational evidence behind management-system controls.
+
+None of this certifies anything by itself. It gives your assessor something verifiable to look at.
+
+## CLI
+
+```
+halo verify   validate schema + hash chain (non-zero exit on failure; CI-friendly)
+halo report   render a chain as a self-verifying HTML Runtime Report
+halo serve    serve per-tenant reports over HTTP, access-scoped per customer
+halo grant    designate a report recipient (email or domain)
+halo anchor   witness a chain head, or --check completeness
+halo demo     scaffold the full vendor demo (record -> witness -> gated report)
+halo sample   emit a valid example log
+halo hash     canonical sha256 of a JSON value
+halo hook     Claude Code PostToolUse hook
+```
+
+## Integrity model
+
+To compute a record's hash: take the record excluding `integrity.hash`, with `integrity.prev_hash` set to the previous record's hash; canonicalize with RFC 8785 (JSON Canonicalization Scheme); SHA-256 the bytes. The first record's `prev_hash` is 64 zeros. Verification recomputes every hash and checks every link. No secret required; that is the point.
+
+Full field reference: [`halo-record.schema.json`](src/halo_record/halo-record.schema.json).
+
+## TypeScript
+
+The same recorder ships for Node: [`halo-record-ts`](https://github.com/bkuan001/halo-record-ts). Same chain format, same witness protocol. Records written in either language verify with either verifier.
+
+## License
+
+Apache-2.0

halo_record-0.1.0/pyproject.toml

@@ -0,0 +1,39 @@
+[build-system]
+requires = ["setuptools>=61"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "halo-record"
+version = "0.1.0"
+description = "Open, tamper-evident runtime records for AI agents: the Halo Runtime Record format, with a dependency-free conformance verifier."
+readme = "README.md"
+requires-python = ">=3.8"
+license = { text = "Apache-2.0" }
+authors = [{ name = "Brian Kuan" }]
+keywords = ["ai", "agents", "audit", "tamper-evident", "attestation", "compliance"]
+classifiers = [
+  "Development Status :: 3 - Alpha",
+  "Programming Language :: Python :: 3",
+  "License :: OSI Approved :: Apache Software License",
+  "Topic :: Security",
+  "Topic :: System :: Logging",
+]
+dependencies = []
+
+[project.scripts]
+halo = "halo_record.cli:main"
+
+[project.urls]
+Homepage = "https://halo.dev"
+Specification = "https://halo.dev/spec/v0.1/"
+
+[tool.setuptools]
+# Ship the top-level ``halo`` shim alongside the package so the hero snippet
+# ``from halo import trace`` resolves from a plain ``pip install``.
+py-modules = ["halo"]
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+halo_record = ["*.json"]

halo_record-0.1.0/setup.cfg

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

halo_record-0.1.0/src/halo.py

@@ -0,0 +1,19 @@
+"""``from halo import trace`` — the one-import front door.
+
+The package is :mod:`halo_record`; this thin shim lets the hero snippet read
+exactly as advertised::
+
+    from halo import trace
+
+    agent = trace(run, profile="acme-support")
+    agent(...)
+
+Everything re-exported here lives in and is documented under ``halo_record``;
+this module adds no behavior, only the shorter name.
+"""
+
+from halo_record import *  # noqa: F401,F403
+from halo_record import __all__ as _all
+from halo_record import __version__
+
+__all__ = list(_all)

halo_record-0.1.0/src/halo_record/__init__.py

@@ -0,0 +1,56 @@
+"""halo-record — open, tamper-evident runtime records for AI agents.
+
+Public API:
+
+    from halo_record import Recorder, build, verify_log
+
+    rec = Recorder("audit.jsonl")
+    rec.append(build("tool_call", "security", tool="Read",
+                     tool_input={"path": "secrets.env"}))
+
+    verify_log("audit.jsonl")   # -> True if schema + hash chain are intact
+"""
+
+__version__ = "0.1.0"
+
+from .canon import canon, compute_hash, input_hash, GENESIS_PREV
+from .capture import record, record_call, derive_outcome
+from .record import Recorder, TenantRecorder, build, SCHEMA_VERSION
+from .redact import scan, redact_text, redact_sample
+from .verify import verify_log, validate_record, load_schema
+from .anchor import Notary, checkpoint, verify_completeness
+from .witness import anchor_remote, fetch_checkpoints
+from .report import render, write_report
+from .session import current_recorder, bind_recorder, reset_recorder
+from .trace import trace
+
+__all__ = [
+    "__version__",
+    "SCHEMA_VERSION",
+    "Recorder",
+    "build",
+    "trace",
+    "current_recorder",
+    "bind_recorder",
+    "reset_recorder",
+    "record",
+    "record_call",
+    "derive_outcome",
+    "verify_log",
+    "validate_record",
+    "load_schema",
+    "scan",
+    "redact_text",
+    "redact_sample",
+    "canon",
+    "compute_hash",
+    "input_hash",
+    "GENESIS_PREV",
+    "Notary",
+    "checkpoint",
+    "verify_completeness",
+    "anchor_remote",
+    "fetch_checkpoints",
+    "render",
+    "write_report",
+]