acdp-agent-hooks 0.1.0__tar.gz

acdp_agent_hooks-0.1.0/.gitignore

@@ -0,0 +1,11 @@
+.venv/
+__pycache__/
+*.egg-info/
+dist/
+build/
+.coverage
+.coverage.*
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+acdp-spec/

acdp_agent_hooks-0.1.0/CHANGELOG.md

@@ -0,0 +1,17 @@
+# Changelog
+
+## 0.1.0 — 2026-10-26
+
+First release.
+
+- `AcdpPublisher`: signs one body per tool result / final output with a
+  did:key or did:web Ed25519 producer key and publishes it, with retries under
+  a content-hash idempotency key.
+- Claude Agent SDK: `AcdpClaudeHooks` (`PostToolUse`, `PostToolUseFailure`,
+  `Stop`), appended to existing hooks via `attach` / `install` / `merge_hooks`.
+- OpenAI Agents SDK: `AcdpRunHooks` and `compose_run_hooks`.
+- `derived_from` from declared inputs, cited and observed ctx_ids, and the
+  run's own tool-result bodies.
+- OpenTelemetry `acdp.*` attributes from the spec registry (optional extra).
+- Fail-open by default; fail-closed opt-in.
+- `acdp-hooks keygen`.

acdp_agent_hooks-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.

acdp_agent_hooks-0.1.0/PKG-INFO

@@ -0,0 +1,317 @@
+Metadata-Version: 2.5
+Name: acdp-agent-hooks
+Version: 0.1.0
+Summary: Agent-framework hooks that sign tool results and final outputs and publish them to an ACDP registry, with derived_from lineage and OpenTelemetry attributes.
+Project-URL: Homepage, https://agentcontextdistributionprotocol.io
+Project-URL: Source, https://github.com/agentcontextdistributionprotocol/acdp-agent-hooks
+Project-URL: Issues, https://github.com/agentcontextdistributionprotocol/acdp-agent-hooks/issues
+Author: Agent Context Distribution Protocol
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: acdp,agents,claude-agent-sdk,openai-agents,opentelemetry,provenance
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Requires-Dist: acdp>=0.17.3
+Requires-Dist: httpx>=0.27
+Provides-Extra: claude
+Requires-Dist: claude-agent-sdk<0.3,>=0.2; extra == 'claude'
+Provides-Extra: dev
+Requires-Dist: coverage[toml]>=7.6; extra == 'dev'
+Requires-Dist: mypy>=1.13; extra == 'dev'
+Requires-Dist: opentelemetry-sdk>=1.27; extra == 'dev'
+Requires-Dist: pytest-asyncio>=0.24; extra == 'dev'
+Requires-Dist: pytest>=8.3; extra == 'dev'
+Requires-Dist: ruff==0.16.9; extra == 'dev'
+Provides-Extra: openai
+Requires-Dist: openai-agents>=0.24; extra == 'openai'
+Provides-Extra: otel
+Requires-Dist: opentelemetry-api>=1.27; extra == 'otel'
+Description-Content-Type: text/markdown
+
+# acdp-agent-hooks
+
+Hooks for agent frameworks that sign every tool result and every final output,
+publish each one to an [ACDP](https://agentcontextdistributionprotocol.io)
+registry, and link them together with `derived_from`. Each publish returns an
+`acdp://` link, and OpenTelemetry spans get the spec's `acdp.*` attributes.
+
+- **Claude Agent SDK**: `PostToolUse`, `PostToolUseFailure` and `Stop` hooks,
+  appended to whatever hooks you already have (seam's `SeamHooks`, for example).
+- **OpenAI Agents SDK**: a `RunHooks` (`on_tool_end`, `on_agent_end`) plus a
+  composer, so it runs alongside your own hooks.
+- **OpenTelemetry**: optional. Only the names in the spec's
+  [`registries/otel-attributes.md`](https://github.com/agentcontextdistributionprotocol/agentcontextdistributionprotocol/blob/main/registries/otel-attributes.md)
+  are emitted.
+
+```bash
+pip install "acdp-agent-hooks[claude]"   # or [openai]; add ,otel for spans
+```
+
+Python 3.10+. Depends on the [`acdp`](https://pypi.org/project/acdp/) SDK (≥ 0.17.3)
+for canonicalisation and signing, and on `httpx` for transport.
+
+## Configuration: two lines
+
+```bash
+ACDP_REGISTRY_URL=https://registry.agentcontextdistributionprotocol.io
+ACDP_PRODUCER_KEY=ed25519:<base64url seed>
+```
+
+`acdp-hooks keygen` prints a fresh `ACDP_PRODUCER_KEY` line. The key decides
+the producer DID:
+
+| `ACDP_PRODUCER_KEY` | Producer |
+|---|---|
+| `ed25519:<seed>` | `did:key`, derived from the key. Nothing to host; verifiers check it offline. A new key is a new identity. |
+| `ed25519:<seed>;did=did:web:agents.example.com:my-agent#key-1` | `did:web`. Publish the key in that DID document (`acdp-hooks keygen --did-web <key-id>` prints the public key). Use it for a long-lived identity that can rotate keys. |
+
+`<seed>` is the 32-byte Ed25519 seed as base64url or 64 hex characters. It is
+the private key. Keep it in your secret store.
+
+Keyless signing (RFC-ACDP-0021) is still a draft, so it is not supported yet.
+
+In code, `HooksConfig(registry_url, producer_key)` does the same job, and
+`HooksConfig.from_env()` reads the two variables. The other settings have
+defaults: `fail_policy` (`open`), `visibility` (`public`), `timeout_s` (10)
+and `retries` (2).
+
+## Claude Agent SDK
+
+```python
+from claude_agent_sdk import ClaudeAgentOptions, query
+from acdp_hooks import AcdpPublisher
+from acdp_hooks.claude_agent import AcdpClaudeHooks
+
+provenance = AcdpClaudeHooks(AcdpPublisher.from_env())
+options = ClaudeAgentOptions(hooks=provenance.attach())  # or provenance.attach(existing_hooks)
+
+async for message in query(prompt="...", options=options):
+    ...
+
+ledger = provenance.ledger(session_id)
+ledger.tool_links  # one Link per tool result
+ledger.output_link  # the final output's Link
+```
+
+- **Tool results** (`PostToolUse`, and `PostToolUseFailure` with
+  `is_error: true`). One body per call. Its `ctx_id` goes back to the model as
+  `additionalContext` (`ACDP provenance for this Read result: acdp://…`). Turn
+  that off with `inject_link=False`.
+- **Final output** (`Stop`). One body over `last_assistant_message`. To publish
+  `ResultMessage.result` yourself, use
+  `await provenance.publish_final_output(result, session_id)`, and pass
+  `publish_output_on_stop=False` so the output isn't published twice.
+- `attach(existing)` returns a new hooks map: `existing` with this package's
+  matchers **appended** to each event's list. It never removes, replaces or
+  reorders a matcher, and it does not mutate `existing`. `install(options)`
+  does the same in place on a `ClaudeAgentOptions`. `merge_hooks(a, b, …)`
+  concatenates any number of maps.
+- Each matcher's timeout (`hook_timeout_s`) is set longer than one publish
+  including all its retries. That way the fail policy settles a slow registry,
+  not the SDK's hook timeout.
+- Every hook body is sentineled. A malformed hook input or an unexpected error
+  is handled by the fail policy and never raised into the SDK.
+
+### With seam's `SeamHooks`
+
+seam's `SeamHooks` (package `seam-claude-agent`, from seam-adapters) gates
+tool calls with `PreToolUse` and audits them with
+`PostToolUse`/`PostToolUseFailure`. The two packages coexist on the same
+events:
+
+```python
+from seam_claude_agent import SeamHooks
+from acdp_hooks.claude_agent import AcdpClaudeHooks
+
+seam = SeamHooks(gate)
+provenance = AcdpClaudeHooks(AcdpPublisher.from_env())
+
+options = ClaudeAgentOptions(hooks=provenance.attach(seam.matchers()))
+```
+
+- **Order.** Seam's matchers come first in each list and ACDP's are appended
+  after them. Neither hook reads the other's output.
+- **Seam decides, ACDP records.** `PreToolUse` belongs to seam alone. A call
+  seam denies never runs, so it gets no `PostToolUse` and no ACDP body. A call
+  seam transforms is recorded with the `tool_input` the SDK reports to
+  `PostToolUse`.
+- **Both audit, independently.** Seam's `ToolUseAudit` and the ACDP ledger
+  both see the same `tool_response`. Seam's post hooks return `{}`. Under
+  fail-open, ACDP's return only `additionalContext`, so nothing collides.
+- **Fail-closed.** If you set ACDP to fail-closed, a failed publish replaces
+  the tool output that reaches the model (`updatedToolOutput` /
+  `updatedMCPToolOutput`). Seam's audit row still records the real result,
+  because the tool did run.
+- **Timeouts are per matcher.** Seam derives its timeout from its gate
+  deadline; ACDP derives its own from the publish deadline. Neither one
+  stretches the other.
+- **`can_use_tool`.** ACDP never sets it, so seam's escalation adjudicator
+  keeps working as before.
+
+## OpenAI Agents SDK
+
+```python
+from agents import Runner
+from acdp_hooks import AcdpPublisher
+from acdp_hooks.openai_agents import AcdpRunHooks, compose_run_hooks
+
+publisher = AcdpPublisher.from_env()  # reuse across runs
+provenance = AcdpRunHooks(publisher)  # one per run
+
+result = await Runner.run(agent, prompt, hooks=compose_run_hooks(my_hooks, provenance))
+provenance.ledger.output_link  # the final output's acdp:// link
+```
+
+- `on_tool_end` publishes one body per local tool call. For function tools the
+  arguments come from `ToolContext.tool_arguments`, and `on_tool_start` supplies
+  `started_at`. `on_agent_end` publishes the final output, with the agent's
+  `name` included.
+- `Runner.run` accepts a single `hooks` object, so `compose_run_hooks(a, b, …)`
+  forwards every `RunHooks` callback to each member in order.
+- The SDK gives a hook no way to change a tool result, so **fail-closed raises**
+  `PublishError` out of the hook. The SDK wraps it in `UserError` and the run
+  stops before the model sees the result.
+
+## What gets published
+
+Bodies never contain the result. Each one is a record of **salted hashes**,
+following the model of RFC-ACDP-0019 §4.3: `H(salt ‖ JCS(value))`, with a fresh
+32-byte salt for every body.
+
+| | Tool result | Final output |
+|---|---|---|
+| `type` | `agent_hooks:tool-result` | `agent_hooks:agent-output` |
+| `title` | `Tool result: <tool>` | `Agent output[: <agent>]` |
+| `metadata.record_version` | `acdp-agent-hooks-tool-result/1` | `acdp-agent-hooks-output/1` |
+| `metadata` | `framework`, `tool`, `arguments_hash`, `result_hash`, `is_error`, `salted`, `embedded`, `started_at`?, `completed_at` | `framework`, `agent`?, `output_hash`, `salted`, `embedded`, `completed_at` |
+| `tags` | `["acdp-agent-hooks"]` | same |
+
+The `Link` returned for each body (`ctx_id`, `lineage_id`, `version`,
+`content_hash`, `registry`, `producer`, `type`, `derived_from`, `salt`) is the
+only place the salt exists. Holding the result plus the link lets you prove the
+binding: fetch the body, verify it, then recompute the hash with
+`acdp_hooks.salted_hash(salt, result)`. Without the salt, the public body
+reveals nothing about the content. Treat the salt as carefully as the result.
+It is not in `repr(link)` and never goes into a span.
+
+These types are custom (`<namespace>:<type>`), not the RFC-ACDP-0019
+`acdp:mcp-tool-result`. That record describes an MCP proxy's view of an MCP
+server (`serverInfo`, transport, endpoint hash), and an in-process hook can't
+see any of it, especially for built-in tools.
+
+### `derived_from`
+
+Every body links to the `ctx_id`s the run consumed:
+
+- **Declared inputs**: `ledger.consume(ctx_id, verified=…)`, for example a
+  context your app placed in the prompt.
+- **Cited in a tool's arguments**: picked up by the RFC-ACDP-0019 §4.4 walk
+  (JCS order, whole-string matches only).
+- **Seen in a tool's result**: any `acdp://` id embedded in what a tool
+  returned. It counts as an input to everything the run does *afterwards*, not
+  to that tool's own body.
+- **The run's own tool results**: the final-output body also derives from every
+  tool-result body published during the run.
+
+The list keeps first occurrences in that order and is capped at 1000, the
+RFC-ACDP-0002 maximum.
+
+### Visibility
+
+The default is `public`. With salted hashes, a public body shows only *that*
+the producer called a named tool at a given time; it never shows what went in
+or came out. If even that is sensitive, set `visibility="private"`. In that
+case only callers the registry authorises can resolve the link.
+RFC-ACDP-0019 §8.3 reasons the same way. The configured value is used as is; a
+rejected publish is never retried with a wider visibility.
+
+## Publish failure policy
+
+**The default is fail-open.** A hook that can't publish lets the agent carry
+on, and the failure is recorded in three places: `ledger.failures`, the
+`acdp.publish.error` span attribute and a `WARNING` on the `acdp_hooks` logger.
+Provenance is an observer of the agent and shouldn't take production agents
+down when a registry is unreachable. RFC-ACDP-0019 §7 uses the same default.
+
+Set `fail_policy="closed"` when nothing should leave the run without
+provenance:
+
+| | Fail-open (default) | Fail-closed |
+|---|---|---|
+| Claude, tool result | result passes through unchanged | result replaced by a "withheld" message (`updatedToolOutput` / `updatedMCPToolOutput`, `decision: block`) |
+| Claude, `Stop` | nothing changes | `continue_: false` with a `stopReason` |
+| Claude, `publish_final_output` | returns `None` | raises `PublishError` |
+| OpenAI, any hook | the run continues | raises `PublishError`, which stops the run |
+
+A publish counts as failed when the registry returns an error, when the body
+can't be built (for example, metadata over 64 KB), or when retries run out:
+`retries` extra attempts with exponential backoff, each with a `timeout_s`
+limit. Retries resend the same bytes under
+`Idempotency-Key: acdp-hooks-<content hash>`, so a retry never publishes twice.
+`PublishError.code` holds the registry's RFC-ACDP-0007 error code, or
+`transport` when no ACDP error was returned.
+
+## OpenTelemetry
+
+Install the `otel` extra (`opentelemetry-api`) and configure a tracer provider
+as usual. Without the extra, every OTel call is a no-op.
+
+- **`acdp.publish` span.** Each publish opens a child span under the active
+  span. It gets `acdp.ctx_id`, `acdp.lineage_id`, `acdp.version`,
+  `acdp.content_hash`, `acdp.producer`, `acdp.registry`, `acdp.type` and
+  `acdp.derived_from`; on failure it gets `acdp.publish.error` instead of the
+  identifiers. Giving each body its own span keeps several tool results under
+  one agent span from overwriting each other's `acdp.ctx_id`.
+- **The active span** (the work that used the inputs) gets
+  `acdp.input.ctx_ids`. When you reported verification through
+  `consume(..., verified=…)`, it also gets `acdp.input.verified`, which is
+  `true` only if every input was reported verified.
+- `acdp_hooks.annotate_chain_verdict(verdict)` copies an RFC-ACDP-0017 chain
+  verdict's `chain.latest`, `chain.as_of` and `verdict_digest` onto the active
+  span (`acdp.input.chain_verdict*`, `acdp.input.verdict_digest`).
+
+Values are copied from the wire without changes. A name outside the registry
+raises an error instead of being emitted. Body content, arguments, results and
+salts never go into an attribute. CI checks the name list against the pinned
+spec checkout.
+
+## Development
+
+```bash
+uv venv && uv pip install -e ".[claude,openai,otel,dev]"
+ruff format --check . && ruff check . && mypy
+coverage run -m pytest && coverage report        # unit tests, coverage-gated
+
+# integration: a local acdp-registry-rs (docker) …
+docker compose -f tests/integration/compose.yml up -d --wait
+ACDP_IT_REGISTRY=http://localhost:8443 pytest -m integration
+# … or production (publishes public bodies under a throwaway did:key)
+ACDP_IT_REGISTRY=https://registry.agentcontextdistributionprotocol.io pytest -m integration
+```
+
+CI follows the [ACDP Delivery Standard](https://github.com/agentcontextdistributionprotocol/acdp-ci/blob/main/DELIVERY-STANDARD.md):
+format, lint, `mypy --strict`, a coverage gate, a no-extras install, a build
+with `twine check`, and the integration suite against a local registry
+container. `main` is protected by `acdp-ci/scripts/standardize.sh`.
+
+## Releasing
+
+Bump `version` in `pyproject.toml` and `__version__` in
+`src/acdp_hooks/__init__.py`, update `CHANGELOG.md`, merge, then push a
+`v<version>` tag. `release.yml` builds the package, attests provenance and
+publishes to PyPI through **Trusted Publishing**, so no token is stored. The
+PyPI trusted publisher names this repo, `release.yml` and the `pypi`
+environment.
+
+TypeScript packages will follow.
+
+## License
+
+Apache-2.0