aitp-verifier 0.1.0__tar.gz

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

aitp_verifier-0.1.0/PKG-INFO

@@ -0,0 +1,251 @@
+Metadata-Version: 2.4
+Name: aitp-verifier
+Version: 0.1.0
+Summary: Independent Python implementation of the AITP verification core (second, spec-only implementation that cross-checks the reference one)
+Author: AITP contributors
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/agentidentitytrustprotocol/aitp-verifier-py
+Project-URL: Source, https://github.com/agentidentitytrustprotocol/aitp-verifier-py
+Project-URL: Issues, https://github.com/agentidentitytrustprotocol/aitp-verifier-py/issues
+Project-URL: Changelog, https://github.com/agentidentitytrustprotocol/aitp-verifier-py/blob/main/CHANGELOG.md
+Project-URL: Specification, https://github.com/agentidentitytrustprotocol/agentidentitytrustprotocol
+Keywords: aitp,agent-identity,verifier,conformance,jws
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Security :: Cryptography
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: cryptography>=50.0
+Provides-Extra: dev
+Requires-Dist: pytest>=9.0.3; extra == "dev"
+Requires-Dist: mypy>=1.18.1; extra == "dev"
+Dynamic: license-file
+
+# aitp-verifier-py
+
+An **independent Python implementation of the AITP verification core** — a
+second implementation, written from the spec alone, that cross-checks the
+reference one. The first implementation is
+[`aitp-rs`](https://github.com/agentidentitytrustprotocol/aitp-rs); its
+Python/Node bindings wrap the same Rust core and therefore do **not** count as
+independent. How implementations feed RFC promotion is defined by the spec, not
+here: see [`governance/RFC-PROCESS.md`](https://github.com/agentidentitytrustprotocol/agentidentitytrustprotocol/blob/main/governance/RFC-PROCESS.md)
+and [`VERSIONING.md`](https://github.com/agentidentitytrustprotocol/agentidentitytrustprotocol/blob/main/VERSIONING.md).
+Status of each RFC: [`rfcs/README.md`](https://github.com/agentidentitytrustprotocol/agentidentitytrustprotocol/blob/main/rfcs/README.md).
+
+**Wire freeze:** the `aitp/0.3` wire is frozen until 1.0, except for security fixes
+([what is frozen](https://github.com/agentidentitytrustprotocol/agentidentitytrustprotocol/blob/main/VERSIONING.md#what-is-frozen-aitp03-line)).
+This verifier tracks that one wire. The conformance claim it passes is `AITP v0.3` (with
+`AITP v0.3 self-attestation`) at the spec commit in [`SPEC_VERSION`](SPEC_VERSION); see
+[Conformance coverage](#conformance-coverage).
+
+## Install
+
+```
+pip install aitp-verifier
+```
+
+The distribution is `aitp-verifier`, the import package is `aitp_verifier`, and the
+console script is `aitp-verifier-adapter`. Its version numbers are its own. They do not
+follow aitp-rs's lockstep releases, and the spec commit a release passes is the one in
+`SPEC_VERSION`. Releases go out from a `v*` tag through PyPI trusted publishing
+([`release.yml`](.github/workflows/release.yml)). The tag must equal the `pyproject.toml`
+version, or nothing is published.
+
+## Independence claim
+
+This codebase was implemented **from the RFC-AITP texts and JSON schemas only**
+([RFC-AITP-0001…0013](https://github.com/agentidentitytrustprotocol/agentidentitytrustprotocol/tree/main/rfcs),
+`schemas/json/*`, and the conformance pack's pinned
+*expectations* under `schemas/conformance/`). No algorithmic code was read
+from, ported from, or shared with `aitp-rs`, and nothing shells out to any Rust
+binary. The two implementations meet only at the conformance pack's byte-pinned
+golden vectors (`known-answer/`) — which is the point: cross-verifying the same
+vectors from two independently written codebases is what makes the check
+meaningful.
+
+## Scope
+
+A **verification library plus a conformance-fixture runner** — not an agent, not
+an HTTP client, not a registry. No network I/O exists anywhere in this codebase.
+
+Implemented: RFC-AITP-0001–0006, 0008, 0010, 0011. RFC-AITP-0007 (key resolution)
+is covered only as far as verifying with caller-supplied keys (`jwk`, `identity`) —
+nothing is fetched. RFC-AITP-0009 is a
+[security RFC](https://github.com/agentidentitytrustprotocol/agentidentitytrustprotocol/blob/main/rfcs/RFC-AITP-0009-security.md)
+and has no module of its own. RFC-AITP-0012 (extensions) is honored only as the
+opaque `extensions` slot (`fields`); RFC-AITP-0013 (TCT renewal) is not implemented.
+
+| Module | Covers |
+|---|---|
+| `aitp_verifier.jcs` | RFC 8785 JSON canonicalization (own implementation) |
+| `aitp_verifier.crypto` | Ed25519 + ECDSA-P256, the JCS-profile vs JOSE signing split (RFC-AITP-0001 §5.4) |
+| `aitp_verifier.aid` | AID parsing + self-certifying key derivation (§5.3), incl. the `p256` tag |
+| `aitp_verifier.jwk` | RFC 7638 JWK thumbprints for the `cnf.jkt` binding (§5.4.4) |
+| `aitp_verifier.jws` | Strict compact-JWS profile: `typ`/`alg` pinning, no `alg:none`, exact-bytes verify (§5.4.5) |
+| `aitp_verifier.envelope` | Envelope check order (version → member set → signature), `aitp-envelope-v2` signing input, replay controls (§5.4/§5.5) |
+| `aitp_verifier.manifest` | Agent Manifest: version, expiry, PoP, signature (RFC-AITP-0003) |
+| `aitp_verifier.tct` | Trust Context Token verification incl. §10.4 Manifest-expiry bound + revocation ordering (RFC-AITP-0005) |
+| `aitp_verifier.voucher` | Grant-voucher verification (RFC-AITP-0005 §8) |
+| `aitp_verifier.delegation` | Single-hop delegation + the multi-hop chain (hop limit, chain-hash commitment, transitive scope, per-hop revocation) (RFC-AITP-0006 / RFC-AITP-0011) |
+| `aitp_verifier.revocation` | Revocation-snapshot freshness / signature / fail-mode (RFC-AITP-0008) |
+| `aitp_verifier.identity` | OIDC + pinned-key identity bindings, incl. the five-field pinned-key proof (RFC-AITP-0002) |
+| `aitp_verifier.handshake` | Mutual-handshake payload verification: Manifest, identity, nonce echo, round-2 PoP, embedded TCT (RFC-AITP-0004) |
+| `aitp_verifier.fields` | Closed-field-set enforcement: unknown fields → `UNKNOWN_FIELD`; `extensions` contents are never inspected (RFC-AITP-0012 §1) |
+| `aitp_verifier.sigfield` | Algorithm-tagged (`ed25519.`/`p256.`) JCS-profile signature fields (RFC-AITP-0001 §5.4.3) |
+| `aitp_verifier.keys` | Loads the pinned known-answer keypairs for the minter / runner |
+| `aitp_verifier.errors` | `AitpError` and the typed error-code vocabulary |
+| `aitp_verifier.verify` | Operation registry: maps a fixture `input.operation` to its verifier |
+| `aitp_verifier.minter` | Conformance-fixture minter: fills `__PLACEHOLDER__` values with the pinned KAT keys (signs; the verification core never does) |
+| `aitp_verifier.b64`, `aitp_verifier.timeutil` | base64url helpers; the reference-clock constant |
+| `aitp_verifier.version` | `PROTOCOL_VERSION` (`aitp/0.3`), the one revision accepted under the strict cutover |
+| `aitp_verifier.sessionbundle` | Session Trust Bundle: envelope shape, expiry-before-signature, expiry-window invariant, coordinator signature, per-participant TCT, self-membership (RFC-AITP-0010) |
+
+## Conformance coverage
+
+`run_conformance.py` re-derives every in-scope fixture from the pinned KAT
+keypairs and runs it against this implementation:
+
+```
+python run_conformance.py --spec-dir ../agentidentitytrustprotocol [--claim "AITP v0.3"]
+```
+
+The run exits nonzero on any FAIL. `--claim` names one of the RFC-AITP-0001 §10 claim
+strings, gated as the spec's
+[conformance badge rules](https://github.com/agentidentitytrustprotocol/agentidentitytrustprotocol/blob/main/docs/conformance-badge.md#claims)
+define them, and a SKIP of any fixture behind the claim fails the run too:
+
+| `--claim` | Gated on | Here |
+|---|---|---|
+| `AITP v0.3` (default) | every `status: core` fixture with `required_for_core` (a missing flag counts as required) | passes |
+| `AITP v0.3 self-attestation` | every fixture with `feature: aitp-self-attestation` | passes |
+| `AITP v0.3 pinned-admission` | every fixture with `feature: aitp-pinned-admission` | fails: not implemented |
+
+There are no other claims and no named profiles. Core fixtures run with no draft feature
+opted in, so `del-007`, which expects `DELEGATION_MULTIHOP_NOT_SUPPORTED`, is executed even
+though this verifier implements multi-hop delegation.
+
+Current status at the pinned spec commit (`SPEC_VERSION`, `ddec9f1`, `aitp/0.3`; the runner
+prints the live number): **118 fixtures pass, 0 fail, 15 skipped**. All 94 core fixtures
+pass. So do the three Draft opt-ins (`experimental-multihop-delegation`,
+`experimental-session-bundle`, `experimental-spiffe-identity`), the `aitp-self-attestation` extension, and all multi-step
+sequences (PoP challenge/response `tct-006`/`tct-007`, issuer-side PoP enforcement `tct-026`,
+handshake replay `mh-001`). The surface — envelope, TCT (incl. `alg:none`, alg-confusion,
+`typ`-confusion, expiry-after-Manifest, revocation-ordering, no revocation source, and the
+issuer-side check of RFC-AITP-0005 §10.5), grant voucher, single- **and multi-hop**
+delegation, Manifest, revocation snapshots, session bundles, and the full mutual-handshake /
+identity family (OIDC and pinned-key bindings, the receiver's identity-type policy, nonce
+echo, round-2 PoP, embedded peer-issued TCT) — is validated byte-for-byte against
+`known-answer/keypairs.json`, `jwk-thumbprints.json`, `jcs-sha256.json`, the
+`signed-examples/` artifacts (including both envelope KATs, `kat-envelope-001-p256` and
+`kat-envelope-002-ed25519`), and the id-007 pinned-key proof vector.
+
+The skips are reported explicitly, never as a silent pass (PLACEHOLDERS.md §"Operation key"):
+
+- **`del-004`** — frozen in the retired v0.1 object wire shape
+  (`required_for_v0_1` only); a current implementation legitimately does not run it.
+- **`id-013`…`id-016`, `id-019`…`id-022`** — the optional pinned-admission profile
+  (RFC-AITP-0002 §3.4, `feature: aitp-pinned-admission`), which this verifier does not
+  claim.
+- **`a2a-001`…`a2a-006`** — the Draft A2A Agent Card binding (RFC-AITP-0014,
+  `feature: aitp-a2a-agent-card`), not implemented.
+
+## Running under aitp-conformance
+
+The same verifier also runs behind aitp-rs's
+[`aitp-conformance`](https://github.com/agentidentitytrustprotocol/aitp-rs/blob/main/docs/conformance.md)
+runner. `aitp-verifier-adapter` is its NDJSON subprocess adapter: one request per line on
+stdin, one response per line on stdout, logs on stderr only, exit 0 on EOF. aitp-rs
+publishes no runner binary, so build it from an aitp-rs checkout:
+
+```
+cargo build -p aitp-conformance --bin aitp-conformance      # in aitp-rs
+AITP_SPEC=../agentidentitytrustprotocol \
+  target/debug/aitp-conformance run \
+    --target "$(command -v aitp-verifier-adapter)" \
+    --fixtures-dir ../agentidentitytrustprotocol/schemas/conformance \
+    --feature aitp-self-attestation --report adapter.json
+```
+
+`AITP_SPEC` names the spec checkout. The adapter reads two key files from it. It needs the
+KAT keys to sign the per-issuer "not revoked" snapshots of a delegation fixture
+(conformance README, "Revocation inputs"). Its OIDC issuer resolver needs
+`known-answer/oidc-test-issuers.json`: it resolves `https://auth.openai.com` and no other
+issuer.
+
+`run_conformance.py --report native.json` writes the same report from this repo's own
+runner. The `adapter-parity` CI job (aitp-rs pinned by `AITP_RS_SHA` in `ci.yml`) produces
+both reports. It validates them against the spec's report schema and checker, then runs
+[`scripts/parity-diff.py`](scripts/parity-diff.py), which requires the two to agree
+fixture for fixture. The diff lists its allowed exceptions by name:
+
+- `del-007` runner policy: aitp-conformance skips it once the multi-hop draft feature is
+  on.
+- runner defects reported upstream and not yet fixed at the aitp-rs pin. A listed entry
+  that starts agreeing fails the diff, so the list cannot go stale.
+
+A run with a draft feature enabled cannot pass the `AITP v0.3` gate, because the
+feature-negation skip of `del-007` blocks it. For a core claim, enable extension features
+only.
+
+## CI and the spec pin
+
+The required checks in `ci.yml` run against the spec commit pinned in
+[`SPEC_VERSION`](SPEC_VERSION), never the spec's moving `main`. A spec merge therefore
+cannot turn this repo red without a PR here. On a conformance-relevant spec push, the
+spec's `notify-spec-consumers.yml` dispatches `spec-released`, and
+[`bump-spec.yml`](.github/workflows/bump-spec.yml) calls `aitp-ci`'s `bump-spec-ref` to
+open a PR that moves the pin. The PR is held for review and its own CI runs the new
+fixtures.
+
+[`spec-canary.yml`](.github/workflows/spec-canary.yml) is the wire canary. It runs daily,
+and on demand, against the spec's floating `main`. It is not a required check. When it fails
+it comments on one tracking issue ("Spec canary: conformance fails against spec main"),
+opening it if none is open, and a green run closes that issue.
+
+## Usage and error contract
+
+Every verifier entry point returns normally on success and raises `AitpError`
+(`aitp_verifier.errors`) on rejection; malformed remote input never escapes as a
+raw `KeyError`/`TypeError`/`RecursionError`. Caller bugs are the exception: a
+missing revocation `policy` (on `verify_tct`, also no `issuer_revocation_list.fail_mode`
+fallback) or a missing required argument raises a plain `KeyError`
+(see [CHANGELOG.md](CHANGELOG.md)).
+`jcs` raises `JcsError` and `minter` raises `MinterError` — they are not
+verifier entry points. Error codes and their meaning are defined by the spec's
+[error-code registry](https://github.com/agentidentitytrustprotocol/agentidentitytrustprotocol/blob/main/registries/error-codes.md),
+not restated here. Security-relevant behavior changes are tracked in
+[CHANGELOG.md](CHANGELOG.md).
+
+## Cross-implementation checks
+
+`aitp-rs` mints artifacts that this repo verifies, and verifies a session bundle
+this repo minted (committed in aitp-rs's `tests/xcheck-fixtures/`) — see aitp-rs
+[testing § cross-implementation acceptance](https://github.com/agentidentitytrustprotocol/aitp-rs/blob/main/docs/testing.md#cross-implementation-acceptance-xcheck)
+and [conformance](https://github.com/agentidentitytrustprotocol/aitp-rs/blob/main/docs/conformance.md).
+That job pins this repo at a specific commit (`tests/AITP_VERIFIER_PY_VERSION` in
+aitp-rs), so it does not track `main` here.
+
+## Development
+
+```
+pip install -e ".[dev]"
+pytest          # KAT re-derivation, signed-example verify, full pack has no FAIL
+mypy            # --strict, clean
+```
+
+Requires Python ≥ 3.11 and `cryptography`. The runner takes `--spec-dir`; `pytest` resolves the spec checkout from
+`$AITP_SPEC`, then a sibling `agentidentitytrustprotocol/` directory, and fails
+loudly if neither exists (set `AITP_SPEC=none` to deliberately run only the
+spec-independent subset instead).
+
+## License
+
+Apache-2.0.