cendor-acttrace 0.7.0__tar.gz

cendor_acttrace-0.7.0/.gitignore

@@ -0,0 +1,19 @@
+__pycache__/
+*.py[cod]
+*.egg-info/
+build/
+dist/
+.venv/
+.uv/
+.ruff_cache/
+.pytest_cache/
+.mypy_cache/
+.coverage
+htmlcov/
+.idea/
+.vscode/
+.DS_Store
+*.log
+
+# MkDocs build output (local preview only)
+site/

cendor_acttrace-0.7.0/CHANGELOG.md

@@ -0,0 +1,69 @@
+# Changelog — cendor-acttrace
+
+Format: [Keep a Changelog](https://keepachangelog.com).
+
+## [0.7.0] — 2026-06-27
+### Added
+- **Redaction now leaves a record (`flag_on_redact`, default on).** When the built-in redactor scrubs sensitive data (categories: `email` / `api_key` / `bearer_token`) from a content-bearing entry (`decision`, `decision_record`, `llm_call`, `tool_call`, `context_assembly`), `AuditLog` appends a follow-up `policy_flag` (`action="redacted"`, `severity="info"`, `data=[categories]`, `auto=True`) tagged to the active decision — so PII removal is itself in the tamper-evident chain instead of happening silently. Closes the gap where the redactor scrubbed PII with no trace and `flag()` was purely manual. Disable with `AuditLog(..., flag_on_redact=False)`; only the built-in redactor triggers it (a custom `redactor=` owns its own flagging). Note `llm_call` records only metadata (no prompt text), so PII most often surfaces in a decision's input or a tool_call's arguments. Never recurses; the chain still `verify()`s.
+- **Evidence-pack `_meta` summary.** `export(...)` now writes a `summary` into the `_meta` header — counts of `decisions`, `llm_calls`, `tool_calls`, `context_assemblies`, `human_oversight`, and `policy_flags`, plus `flags_by_action`/`flags_by_severity` — the substance a reviewer scans first.
+
+### Changed
+- `Decision.flag(...)` now returns the chained `AuditEntry` (matching `AuditLog.flag`). `action`/`severity` on both are normalized to lowercase (recommended vocab: action ∈ {`flagged`, `redacted`, `blocked`}, severity ∈ {`info`, `warning`, `critical`}; other strings are accepted, not rejected).
+
+## [0.6.0] — 2026-06-24
+### Fixed
+- **`verify()` now detects tail-truncation.** A hash chain catches edits and middle deletions but not *trailing* entries being dropped — the most likely real-world tamper (silently removing the inconvenient end of a log). `verify` now cross-checks the exported pack's `_meta` header (`head_hash` + `entries`) automatically, and accepts `expected_head=` / `expect_entries=` for raw logs (capture the new `AuditLog.head`). Truncating an evidence pack now fails verification instead of passing.
+
+### Added
+- `AuditLog.head` property (the current chain head) and `verify(..., expected_head=, expect_entries=)` params + `acttrace verify --expect-head/--expect-entries` CLI flags — completeness checks for logs without a `_meta` header.
+- `AuditLog` is now a context manager: `with AuditLog(...) as log:` auto-`detach()`es on exit, so a log created per request/test doesn't leak a bus subscription (which would double-log every later call).
+- Expanded `export(framework=...)` control mappings: the **EU AI Act** template now covers Art. 12/13/14 plus **Art. 19** (automatically generated logs), **Art. 26(5)** (deployer oversight), and **Art. 72** (post-market monitoring); added two new frameworks — **`iso_42001`** (ISO/IEC 42001:2023 Annex A.6.2.8 event logs, A.6.2.6 operation & monitoring, A.5.2 impact assessment, A.9 responsible use, Cl. 9.1 monitoring) and **`gdpr`** (Art. 22 automated decision-making, Art. 30 records of processing, Art. 5(2) accountability). Still starting templates referencing the public framework texts — evidence pointers, not certified mappings.
+- `AuditLog.flag(reason, action=…, severity=…, data=…)` (and `Decision.flag(...)`) — record a tamper-evident `policy_flag` entry when a guard decides input/usage should not be processed (`action="flagged"`/`"redacted"`/`"blocked"`); auto-tags the active `decision()` span. Closes the gap that a pre-flight guard which *raises* to block a call short-circuits bus emission, so the refusal would otherwise leave no audit trail. `policy_flag` maps to data-governance controls per framework (EU AI Act Art. 10/12, ISO/IEC 42001 A.7/A.6.2.8/A.9.2, GDPR Art. 9/5(1)(c)/30, NIST MANAGE/MEASURE). acttrace records the flag; deciding/enforcing the policy stays your guard's job.
+
+### Changed
+- `verify()` streams the file line-by-line instead of reading it whole — flat memory on large audit logs (still splits on the record separator only, preserving the U+2028/U+0085 handling from 0.4.1).
+- `detach()` uses the new `core.bus.unsubscribe()` (core ≥ 0.1.9) instead of reaching into the bus' internal subscriber list. Pins `cendor-core>=0.1.9`.
+- The I/O-bound chain property test sets `@settings(deadline=None)` so a loaded run no longer trips a spurious Hypothesis `DeadlineExceeded` (the invariant is timing-independent).
+
+## [0.5.1] — 2026-06-23
+### Changed
+- Packaging: `LICENSE` and `NOTICE` are now bundled in the distribution (`dist-info/licenses/`), so the Apache-2.0 terms — including the §7 warranty disclaimer and §8 liability limitation — travel inside every wheel/sdist. The README footer states the "as is" / no-warranty / use-at-your-own-risk terms. No code changes.
+
+## [0.5.0] — 2026-06-23
+### Added
+- Pluggable redaction: `AuditLog(redactor=callable)` swaps in your own `payload -> payload` scrubber (e.g. domain-specific PII rules) in place of the built-in email/key/token regex. The exported `default_redactor` lets you compose it (`redactor=lambda o: my_scrub(default_redactor(o))`). Still gated by `redact=True`; the chain stays consistent over scrubbed payloads.
+
+## [0.4.2] — 2026-06-23
+### Changed
+- Relicensed from MIT to Apache-2.0 — adds an explicit patent grant and contribution terms, a better fit for a public library suite.
+- README links to the docs page and CHANGELOG are now absolute GitHub URLs so they resolve on PyPI (they previously broke as repo-relative paths).
+
+## [0.4.1] — 2026-06-23
+### Fixed
+- `verify()` now splits the JSONL on the `\n` record separator only (not `str.splitlines()`), so a log whose payloads contain Unicode line separators (U+2028 / U+0085 / …) verifies correctly instead of failing to parse.
+
+## [0.4.0] — 2026-06-23
+### Added
+- Default-on PII/secret payload redaction (emails / `sk-` keys / bearer tokens) before entries are chained and written; the chain stays consistent over redacted payloads. Disable with `AuditLog(redact=False)`. Ids/hashes are never clobbered.
+
+## [0.3.0] — 2026-06-23
+### Added
+- HMAC-signed records: `AuditLog(signing_key=...)` signs each entry; `verify(path, key=...)` and `acttrace verify --key` check signatures in addition to the chain.
+
+## [0.2.0] — 2026-06-23
+### Added
+- EU AI Act + NIST RMF control-mapping templates for `export(framework=...)`, a `controls_covered` summary in the evidence-pack header, and `frameworks()`.
+
+## [0.1.0] — 2026-06-23
+### Added
+- Initial release: hash-chained, append-only JSONL audit log; auto-subscribes to core's bus; `decision()` / `human_oversight()` events; `export()` evidence pack; and the `acttrace verify` offline CLI.
+
+[0.6.0]: https://pypi.org/project/cendor-acttrace/0.6.0/
+[0.5.1]: https://pypi.org/project/cendor-acttrace/0.5.1/
+[0.5.0]: https://pypi.org/project/cendor-acttrace/0.5.0/
+[0.4.2]: https://pypi.org/project/cendor-acttrace/0.4.2/
+[0.4.1]: https://pypi.org/project/cendor-acttrace/0.4.1/
+[0.4.0]: https://pypi.org/project/cendor-acttrace/0.4.0/
+[0.3.0]: https://pypi.org/project/cendor-acttrace/0.3.0/
+[0.2.0]: https://pypi.org/project/cendor-acttrace/0.2.0/
+[0.1.0]: https://pypi.org/project/cendor-acttrace/0.1.0/

cendor_acttrace-0.7.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 Raghav Mishra (PowerAI Labs)
+
+   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.

cendor_acttrace-0.7.0/NOTICE

@@ -0,0 +1,7 @@
+PowerAI Labs
+Copyright 2026 Raghav Mishra (PowerAI Labs)
+
+This product includes software developed by Raghav Mishra (PowerAI Labs).
+
+Licensed under the Apache License, Version 2.0. See the LICENSE file for the
+full terms.

cendor_acttrace-0.7.0/PKG-INFO

@@ -0,0 +1,66 @@
+Metadata-Version: 2.4
+Name: cendor-acttrace
+Version: 0.7.0
+Summary: Audit: a tamper-evident, hash-chained, auto-populated record of every AI decision — verifiable offline. Evidence, not a compliance guarantee.
+Author: Raghav Mishra
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Requires-Python: >=3.11
+Requires-Dist: cendor-core<0.2,>=0.1.9
+Description-Content-Type: text/markdown
+
+# cendor-acttrace
+
+A tamper-evident, append-only record of every AI decision — what model, what context, what it
+cost, which tools, and who signed off — mapped to control templates and exportable as an evidence
+pack. No database, no infra: integrity comes from a hash chain, not a server.
+
+**Audit-ready evidence in 5 lines — and verifiable offline.**
+
+![PyPI](https://img.shields.io/pypi/v/cendor-acttrace) ![license](https://img.shields.io/badge/license-Apache_2.0-blue) · `pip install cendor-acttrace`
+
+```python
+from cendor.core import instrument
+from cendor.acttrace import AuditLog
+
+client = instrument(OpenAI())
+audit = AuditLog(system="loan_triage", risk_tier="high", signing_key="…")  # auto-subscribes
+
+with audit.decision(input=application, actor="agent") as d:
+    resp = client.chat.completions.create(model="gpt-4o", messages=msgs)  # auto-logged
+    d.record(model="gpt-4o", prompt_id="triage@v3")          # cost/context captured for free
+    d.human_oversight(reviewer="ops@bank", action="approved")
+
+audit.export("evidence_q3.jsonl", framework="eu_ai_act")     # evidence pack (also nist_rmf)
+```
+
+```bash
+acttrace verify evidence_q3.jsonl --key "…"   # re-walks the chain + checks signatures; non-zero if broken
+```
+
+## Highlights
+
+- **Auto-populating** — construct an `AuditLog` and it subscribes to the bus: every LLM/tool call, plus cost (`tokenguard`) and context decisions (`contextkit`) on the same stream, becomes an entry — no per-call wiring.
+- **Tamper-evident hash chain** — `verify()` catches edits, reordering, **and tail-truncation** (head + count travel in the evidence pack, or pass `expected_head=`); each entry optionally **HMAC-signed**.
+- **Decisions & oversight** — `decision()` groups a unit of work; `d.record(...)` and `d.human_oversight(reviewer, action)` capture Art. 14-style sign-off.
+- **Compliance evidence packs** — `export(framework=…)` annotates control IDs for **EU AI Act**, **ISO/IEC 42001**, **GDPR**, and **NIST AI RMF** (starting templates, not certified mappings), and a `_meta.summary` (counts of decisions, oversight, flags by action/severity) gives a reviewer the at-a-glance read first. PII redaction on by default (swap in `redactor=`).
+- **Auto-flag on redaction** — when the built-in redactor scrubs PII (`email`, `api_key`, `bearer_token`) from an auto-captured entry, acttrace appends a `policy_flag` recording *which category* was removed — so "we removed PII" is in the hash chain, not silent (`flag_on_redact=True` by default; a custom `redactor=` owns its own flagging).
+- **Policy flags (validation)** — `audit.flag(reason, action="blocked", …)` records a tamper-evident `policy_flag` (and **returns** the chained entry) when your pre-flight guard refuses input that shouldn't be processed — so the *refusal* is auditable, not just the calls that ran:
+
+```python
+from cendor.core.instrument import add_interceptor, MISS
+
+def guard(call):                                    # your pre-flight policy guard
+    if my_policy_disallows(call):                   # YOUR rule
+        audit.flag("special-category data", action="blocked")   # acttrace records the refusal
+        raise PolicyViolation("blocked")            # your guard enforces it
+    return MISS
+
+add_interceptor(guard)   # the blocked call never reaches the bus — flag() is its only record
+```
+
+> Produces **evidence to support** compliance — not legal advice, not a guarantee. Control
+> mappings are starting templates for your compliance team.
+
+See [`docs/acttrace.md`](https://github.com/PowerAI-Labs/Cendor/blob/main/docs/acttrace.md) · [CHANGELOG](https://github.com/PowerAI-Labs/Cendor/blob/main/packages/cendor-acttrace/CHANGELOG.md). *Part of the Cendor stack — [github.com/PowerAI-Labs/Cendor](https://github.com/PowerAI-Labs/Cendor). Powered by PowerAI Labs. Apache-2.0; provided "as is", without warranty — use at your own risk (LICENSE §7–8).*

cendor_acttrace-0.7.0/README.md

@@ -0,0 +1,54 @@
+# cendor-acttrace
+
+A tamper-evident, append-only record of every AI decision — what model, what context, what it
+cost, which tools, and who signed off — mapped to control templates and exportable as an evidence
+pack. No database, no infra: integrity comes from a hash chain, not a server.
+
+**Audit-ready evidence in 5 lines — and verifiable offline.**
+
+![PyPI](https://img.shields.io/pypi/v/cendor-acttrace) ![license](https://img.shields.io/badge/license-Apache_2.0-blue) · `pip install cendor-acttrace`
+
+```python
+from cendor.core import instrument
+from cendor.acttrace import AuditLog
+
+client = instrument(OpenAI())
+audit = AuditLog(system="loan_triage", risk_tier="high", signing_key="…")  # auto-subscribes
+
+with audit.decision(input=application, actor="agent") as d:
+    resp = client.chat.completions.create(model="gpt-4o", messages=msgs)  # auto-logged
+    d.record(model="gpt-4o", prompt_id="triage@v3")          # cost/context captured for free
+    d.human_oversight(reviewer="ops@bank", action="approved")
+
+audit.export("evidence_q3.jsonl", framework="eu_ai_act")     # evidence pack (also nist_rmf)
+```
+
+```bash
+acttrace verify evidence_q3.jsonl --key "…"   # re-walks the chain + checks signatures; non-zero if broken
+```
+
+## Highlights
+
+- **Auto-populating** — construct an `AuditLog` and it subscribes to the bus: every LLM/tool call, plus cost (`tokenguard`) and context decisions (`contextkit`) on the same stream, becomes an entry — no per-call wiring.
+- **Tamper-evident hash chain** — `verify()` catches edits, reordering, **and tail-truncation** (head + count travel in the evidence pack, or pass `expected_head=`); each entry optionally **HMAC-signed**.
+- **Decisions & oversight** — `decision()` groups a unit of work; `d.record(...)` and `d.human_oversight(reviewer, action)` capture Art. 14-style sign-off.
+- **Compliance evidence packs** — `export(framework=…)` annotates control IDs for **EU AI Act**, **ISO/IEC 42001**, **GDPR**, and **NIST AI RMF** (starting templates, not certified mappings), and a `_meta.summary` (counts of decisions, oversight, flags by action/severity) gives a reviewer the at-a-glance read first. PII redaction on by default (swap in `redactor=`).
+- **Auto-flag on redaction** — when the built-in redactor scrubs PII (`email`, `api_key`, `bearer_token`) from an auto-captured entry, acttrace appends a `policy_flag` recording *which category* was removed — so "we removed PII" is in the hash chain, not silent (`flag_on_redact=True` by default; a custom `redactor=` owns its own flagging).
+- **Policy flags (validation)** — `audit.flag(reason, action="blocked", …)` records a tamper-evident `policy_flag` (and **returns** the chained entry) when your pre-flight guard refuses input that shouldn't be processed — so the *refusal* is auditable, not just the calls that ran:
+
+```python
+from cendor.core.instrument import add_interceptor, MISS
+
+def guard(call):                                    # your pre-flight policy guard
+    if my_policy_disallows(call):                   # YOUR rule
+        audit.flag("special-category data", action="blocked")   # acttrace records the refusal
+        raise PolicyViolation("blocked")            # your guard enforces it
+    return MISS
+
+add_interceptor(guard)   # the blocked call never reaches the bus — flag() is its only record
+```
+
+> Produces **evidence to support** compliance — not legal advice, not a guarantee. Control
+> mappings are starting templates for your compliance team.
+
+See [`docs/acttrace.md`](https://github.com/PowerAI-Labs/Cendor/blob/main/docs/acttrace.md) · [CHANGELOG](https://github.com/PowerAI-Labs/Cendor/blob/main/packages/cendor-acttrace/CHANGELOG.md). *Part of the Cendor stack — [github.com/PowerAI-Labs/Cendor](https://github.com/PowerAI-Labs/Cendor). Powered by PowerAI Labs. Apache-2.0; provided "as is", without warranty — use at your own risk (LICENSE §7–8).*

cendor_acttrace-0.7.0/pyproject.toml

@@ -0,0 +1,19 @@
+[project]
+name = "cendor-acttrace"
+version = "0.7.0"
+description = "Audit: a tamper-evident, hash-chained, auto-populated record of every AI decision — verifiable offline. Evidence, not a compliance guarantee."
+requires-python = ">=3.11"
+license = "Apache-2.0"
+authors = [{ name = "Raghav Mishra" }]
+readme = "README.md"
+dependencies = ["cendor-core>=0.1.9,<0.2"]
+
+[project.scripts]
+acttrace = "cendor.acttrace.cli:main"
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/cendor"]     # contributes cendor/acttrace only — NEVER add src/cendor/__init__.py