integrations: xChk registry, a Trust Record per run (record-producer, Level 0)

.github/workflows/xchk-registry-conformance.yml

@@ -0,0 +1,55 @@
+# xChk registry integration workflow.
+#
+# floating  installs the latest released agentrust-trace and agentrust-trace-tests, unpinned on purpose, as drift detection.
+# fixed     installs the versions named in integration.yaml tested_against.
+# Both verify the committed Trust Record with the pinned key and run the Level 0 conformance suite on it. Neither
+# reaches the registry: the one live check (the published key) is opt-in with REGISTRY_LIVE=1.
+name: xchk-registry conformance
+on:
+  push:
+    paths:
+      - "integrations/xchk-registry/**"
+      - ".github/workflows/xchk-registry-conformance.yml"
+  pull_request:
+    paths:
+      - "integrations/xchk-registry/**"
+      - ".github/workflows/xchk-registry-conformance.yml"
+  schedule:
+    - cron: "0 6 * * 1"
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  check:
+    name: ${{ matrix.mode }} (py${{ matrix.python }})
+    strategy:
+      fail-fast: false
+      matrix:
+        python: ["3.11", "3.12", "3.13"]
+        mode: [floating, fixed]
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
+        with:
+          persist-credentials: false
+      - uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97  # v7.0.0
+        with:
+          python-version: ${{ matrix.python }}
+      - name: Install agentrust-trace and agentrust-trace-tests (latest release)
+        if: matrix.mode == 'floating'
+        run: pip install agentrust-trace agentrust-trace-tests
+      - name: Install agentrust-trace and agentrust-trace-tests (tested_against)
+        if: matrix.mode == 'fixed'
+        run: |
+          v=$(sed -n 's/^  agentrust-trace: "\(.*\)"$/\1/p' integrations/xchk-registry/integration.yaml)
+          t=$(sed -n 's/^  agentrust-trace-tests: "\(.*\)"$/\1/p' integrations/xchk-registry/integration.yaml)
+          test -n "$v" && test -n "$t"
+          pip install "agentrust-trace==$v" "agentrust-trace-tests==$t"
+      - name: Install this integration
+        run: pip install -e "integrations/xchk-registry[test]"
+      - name: Integration tests (offline)
+        run: pytest integrations/xchk-registry/tests -q
+      - name: Level 0 conformance on the committed Trust Record
+        run: trace-tests verify --record integrations/xchk-registry/examples/01-trust-record.json --level 0 --max-age 315360000

README.md

@@ -93,6 +93,7 @@ TRACE only works as a standard if it is genuinely neutral. Integrations are list
 | [WCM Key Release to TRACE](integrations/wcm-trace/) | agentrust-io | wcm, trace | community |
 | [WCM Triton Repository Staging](integrations/wcm-triton/) | agentrust-io | wcm | verified |
 | [WCM Serving Guard for vLLM](integrations/wcm-vllm/) | agentrust-io | wcm | verified |
+| [xChk registry](integrations/xchk-registry/) | xChk | trace | community |
 | [agentrust-codex](plugins/agentrust-codex/) | agentrust-io | agent-manifest, trace | community |
 | [scheduled-agents](scheduled-agents/) | agentrust-io | trace | community |
 <!-- integration-index:end -->

integrations/xchk-registry/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.

integrations/xchk-registry/NOTICE

@@ -0,0 +1,6 @@
+xchk-registry integration: Apache-2.0, copyright (c) 2026 Sean MacGuire.
+
+examples/01-trust-record.json: a Trust Record minted and signed by the registry at https://in.xchk.io for plate
+ENG-WNP3, run 3057 (18 October 2026), cut to one approval-outcome reference. examples/expected.json pins the
+registry's seal key, as published at https://in.xchk.io/.well-known/xchk-keys.json, so the test runs offline. The
+record carries the plate owner's identifiers; he chose to publish it.

integrations/xchk-registry/README.md

@@ -0,0 +1,73 @@
+# xChk registry: a Trust Record per run
+
+An xChk registry licenses AI agents under a verified person and gates each act. This integration covers one thing:
+the Trust Record the registry mints for each run, and how a relying party verifies it against the key the registry
+publishes.
+
+## What the registry produces
+
+A software-only TRACE v0.2 Trust Record per run, Level 0:
+- `subject`: the plate as a `did:web` identifier under the registry's origin.
+- `origin` absent (the gate is in the execution path, not a copy of someone else's telemetry);
+  `runtime.platform: software-only`; `appraisal.status: none`.
+- `tool_transcript`, `policy`, `model`, `data_class`, `build_provenance` as the registry recorded them for the run.
+- `references`: one `approval-outcome` entry per act a person was asked about (approved or not), with `id` and
+  `digest` the registry's record hash and `resolver` the registry origin.
+- `cnf.jwk`: the registry's seal key, Ed25519, with `kid` the key id the registry publishes.
+
+Route: `GET /api/agents/<id>/runs/<runSeq>/trace-record` with the plate owner's token. The signing key is published
+at `https://in.xchk.io/.well-known/xchk-keys.json`.
+
+## What this code does
+
+```
+python xchk_trace_record.py record.json --registry https://in.xchk.io   # verifies with the key that registry publishes under the record's kid
+python xchk_trace_record.py record.json --jwk examples/expected.json     # offline, with a pinned key
+```
+
+It verifies the record with released `agentrust-trace` against a pinned key, or against the key published under the
+record's `kid` at `<origin>/.well-known/xchk-keys.json`, where the origin is the registry the relying party trusts,
+given out of band with `--registry`. Nothing in the record supplies the origin: not its `resolver` and not its
+`did:web` subject, because a record signed under a publisher of its own choosing names that publisher in both,
+and agreeing with itself is not a trust anchor. The record's subject and resolver must agree with the origin given.
+Without `--registry` or `--jwk` the answer is `no-key`. It never verifies against the key the record itself carries,
+for the same reason. `--registry` must be an https origin and nothing more (no credentials, path, query or
+fragment; an explicit port 443 is the same origin as none). When `--registry` is given beside `--jwk`, both are enforced: the
+pinned key verifies the signature, and the record's subject and every `approval-outcome` resolver must be under
+the origin, compared as origins. The fetch is https only, follows no redirect, reads at most 256 KB, and a key document of the wrong
+shape is no key, never a crash; the same holds for a record file or pinned-key file of the wrong shape, and for any
+field of the record: every input ends in a JSON verdict and an exit code. A verified result carries the verified
+`profile` and the complete `accepted_profiles` set (section 3.3), the thumbprint of the key actually used, `kid`
+(the key the record names) and `pinned_kid` when a pinned key named one, the key source and the trusted origin, and
+lists the `approval-outcome` references as they appear; it does not resolve them.
+
+The record's age is bounded: `iat` may be at most `--max-age` seconds old, default 86400 (24 hours, the library's
+default and section 3.2.2's), and the bound cannot be switched off. A retained record is re-verified at its own time
+with `--now <epoch seconds>` rather than by widening the bound; every verdict carries `verified_at`, the instant it
+was made against, and `verified_at_overridden`, so a historical verdict is never the same JSON as a current one. The output carries `revocation` as the library
+reported it; this tool passes no revocation bundle or store, so it reports `no_check_performed`, which is not an
+affirming appraisal (section 3.2.3). A stale or tampered record is `invalid`, with the reason.
+
+## Run it
+
+```
+pip install -e "integrations/xchk-registry[test]" agentrust-trace-tests
+pytest integrations/xchk-registry/tests -q                          # offline; REGISTRY_LIVE=1 adds one live key fetch
+trace-tests verify --record integrations/xchk-registry/examples/01-trust-record.json --level 0 --max-age 315360000
+```
+
+The example record was minted on 17 Oct 2026, so the conformance command above carries an explicit `--max-age`
+(ten years, the same as the workflow), as a historical fixture must; the verifier's own default stays 24 hours.
+
+## What it does not claim
+
+- **Nothing about what a reference resolves to.** An `approval-outcome` reference is a pointer the registry is
+  obliged to keep resolvable (spec section 3.1.2); what the referenced receipt establishes, and how to check it, is a
+  separate integration, not this one.
+- **No hardware.** The record is software-only and unappraised, and says so in its own fields.
+- **No ordering claim.** A Trust Record is issued per execution; it does not carry a commitment that an approval was
+  checked before the act ran.
+- The registry's server code is not public. What is public is the record route, the key document and this
+  example.
+
+Maintained by the registry operator (see `integration.yaml`). Personal research project.