> ## Documentation Index > Fetch the complete documentation index at: https://docs.algovoi.co.uk/llms.txt > Use this file to discover all available pages before exploring further. # Substrate Adopters Registry > Public registry of parties publishing artefacts under the jcs-rfc8785-v1 canonicalisation discipline: a neutral record of adoption, not an endorsement. New to the substrate? Start with [Adopt the substrate](/canonicalisation-substrate#adopt-the-substrate), the open, Apache-2.0 foundation that is free to build on. This page is the record of who already has. This page is the public registry of parties publishing artefacts under the AlgoVoi-authored canonicalisation discipline [`urn:x402:canonicalisation:jcs-rfc8785-v1`](https://datatracker.ietf.org/doc/draft-hopley-x402-canonicalisation-jcs-v1/), normatively specified in IETF Internet-Draft [`draft-hopley-x402-canonicalisation-jcs-v1`](https://datatracker.ietf.org/doc/draft-hopley-x402-canonicalisation-jcs-v1/) (Independent Submission, Informational; AlgoVoi-authored). The registry is maintained by AlgoVoi as a neutral record of observed adoption. Inclusion is informational and reflects public adoption only; it does not imply endorsement or normative authority from the listed party. Absence from the registry is not normative. It records adoption of **either** L1 substrate — the JCS canonicalisation discipline (`urn:x402:canonicalisation:jcs-rfc8785-v1`) **and** the RFC 9421 §2.5 signing-base (`rfc9421_proxy_chain_v1`, `draft-hopley-x402-rfc9421-binding`). Building an L2 layer on top is free; what is recorded — and the one ask — is **attribution of the L1** you import (keep the NOTICE, import by hash). The registry parallels the Appendix C "Known Adopters" section maintained in the IETF I-D revisions. The registry is the canonical web-accessible record between I-D revisions. ## Why a public registry Adoption of a canonicalisation discipline is the load-bearing evidence that the discipline works across independent implementations and use cases. A retained byte-deterministic record of who has adopted, when, and against which `canon_version` pin is itself audit-grade evidence: * For year-N auditability: a verifier reading retained receipts can confirm the adopters that were emitting under the same canonicalisation pin at the time of emission. * For ecosystem clarity: downstream parties evaluating whether to adopt benefit from observing existing adopter surfaces and their interoperability records. * For authorship attribution: the registry records each adopter's own authorship of the artefacts they publish, alongside their dependence on the underlying canonicalisation discipline. Authorship of artefacts and authorship of the discipline are separate facts; the registry records both cleanly. ## Registry | Adopter | Identifier | Surface | Anchor | First observed | Evidence | | ----------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **AlgoVoi** (substrate author) | [`api.algovoi.co.uk`](https://api.algovoi.co.uk) · [`docs.algovoi.co.uk`](https://docs.algovoi.co.uk) · [`chopmob-cloud` GitHub org](https://github.com/chopmob-cloud) | Production gateway emitting all 5 AlgoVoi-authored receipt and response formats; 5 reference implementations on PyPI and npm; 10-implementation cross-validation matrix (Python, TypeScript, Go, Rust, Java, PHP, .NET, Ruby, Elixir, Kotlin) | `canon_version: jcs-rfc8785-v1` across compliance, settlement, cancellation, refund receipts and composite-trust-query responses | 2026-04-12 (first production commit on `compliance.py`) | All AlgoVoi-authored I-Ds and reference implementations linked from [Substrate Authorship and Provenance](/substrate-authorship-provenance) | | **Supership / Crest Deployment Systems** (Andy Salvo) | [`andysalvo`](https://github.com/andysalvo) · [`verify.crestsystems.ai`](https://verify.crestsystems.ai) · [`supership.crestsystems.ai`](https://supership.crestsystems.ai) | Three URN extensions under the Crest namespace anchored to the canonicalisation discipline: (1) `service_trust_v0` conformance vector set; (2) `urn:crest:trust-check-v1` general-service-trust envelope (JCS RFC 8785 + Ed25519 + content-addressed `query_ref`/`response_ref` + typed evidence array + informative-null taxonomy, hosted at supership.crestsystems.ai indexing 47K+ services); (3) `transactional-claim-type-draft-00` vector set (14 vectors: 5 positive + 1 stability + 8 adversarial) submitted to A2A v0.4 evidence-envelope review | `canon_version: jcs-rfc8785-v1` | 2026-05-23 (service\_trust\_v0 vectors merged into AlgoVoi corpus); 2026-05-25 (`urn:crest:trust-check-v1` adopter-acknowledged); 2026-05-25 (`transactional-claim-type-draft-00` published with canon\_version pin) | [PR #1 in chopmob-cloud/algovoi-jcs-conformance-vectors](https://github.com/chopmob-cloud/algovoi-jcs-conformance-vectors/pull/1) · [x402#2299 trust-check-v1 envelope](https://github.com/x402-foundation/x402/issues/2299#issuecomment-4534631244) · [action-ref-verify repo](https://github.com/andysalvo/action-ref-verify) · [transactional-draft-00.json](https://github.com/andysalvo/action-ref-verify/blob/main/a2a-interop/transactional-draft-00/transactional-draft-00.json) | | **PEAC Protocol** | [`peacprotocol/peac`](https://github.com/peacprotocol/peac) | `ap2-open-mandate-hash` fixture set -- three positive scenario-shaped cases (baseline / budget-bound / expiry-bound) plus two composition-failure cases (non-SHA-256 digest, non-JCS canonicalisation). Consumes the AlgoVoi-authored `open_mandate_hash` v0 derivation; records mandate references in signed interaction records without modifying AP2 semantics. | `canon_version: jcs-rfc8785-v1` (via the AP2 OMH v0 derivation it anchors against) | 2026-05-25 (fixtures observed and self-declared as downstream adoption on [google-agentic-commerce/AP2#265](https://github.com/google-agentic-commerce/AP2/issues/265)) | [`specs/conformance/interop/ap2-open-mandate-hash/`](https://github.com/peacprotocol/peac/tree/main/specs/conformance/interop/ap2-open-mandate-hash) | | **AlgoVoi** (substrate author, v2) | [`chopmob-cloud/algovoi-substrate-pqc`](https://github.com/chopmob-cloud/algovoi-substrate-pqc) · [`pypi.org/project/algovoi-substrate-pqc`](https://pypi.org/project/algovoi-substrate-pqc/) · [`npmjs.com/package/@algovoi/substrate-pqc`](https://www.npmjs.com/package/@algovoi/substrate-pqc) | `algovoi-substrate-pqc` (Python + npm) reference implementation emitting under v2; implements the `signature_algorithm` open-enum registry, fail-closed verifier discipline, and PQC algorithm coverage (ES256, Ed25519, Falcon-1024, ML-DSA-65). Cross-validated byte-for-byte across three audit-grade PQC implementations (PQClean via `pqcrypto`, `@noble/post-quantum`, Bouncy Castle 1.84 with `MLDSASigner`). | `canon_version: jcs-rfc8785-v2` | 2026-05-26 (v2 discipline published on `docs.algovoi.co.uk/canonicalisation-substrate-v2`; `algovoi-substrate-pqc@0.1.0` released to PyPI and npm same day) | [Canonicalisation discipline v2](/canonicalisation-substrate-v2) · [Cross-product matrix attestation](https://github.com/chopmob-cloud/algovoi-substrate-pqc/blob/main/_attestations/2026-05-26-cross-product-matrix.md) (24/24 cells PASS) | | **Nobulex** (arian-gogani) | [`arian-gogani/nobulex`](https://github.com/arian-gogani/nobulex) · GitHub handle [`arian-gogani`](https://github.com/arian-gogani) | Bilateral-receipt vector set ([`fixtures/bilateral-receipt/v0/vectors.json`](https://github.com/arian-gogani/nobulex/blob/main/fixtures/bilateral-receipt/v0/vectors.json)) under the schema identifier `nobulex-bilateral-receipt-test-vectors-v0.1`. Carries the AlgoVoi `action_ref = SHA-256(JCS({agent_id, action_type, scope, timestamp_ms}))` derivation for the receipt-identity primitive across the ALLOW / DENY / REFER / dual-timestamp policy-version vectors. | `canon_version: jcs-rfc8785-v1` (pinned in-band in `vectors.json`, AlgoVoi-validated) | 2026-05-22 (vectors published); 2026-05-26 (observed-adoption validated by AlgoVoi against canonical bytes per the registry's submission validation process) | Vector set + canon\_version pin verified in [`vectors.json`](https://github.com/arian-gogani/nobulex/blob/main/fixtures/bilateral-receipt/v0/vectors.json) · AlgoVoi 4-impl cross-validation (16/16 byte-for-byte) recorded on [x402#2322 thread comments](https://github.com/x402-foundation/x402/pull/2322) | | **Vauban Pay** (Vauban Research) | [`vauban-org/x402-stark-receipts-conformance`](https://github.com/vauban-org/x402-stark-receipts-conformance) · [`pay.vauban.tech`](https://pay.vauban.tech) · [`pypi.org/project/vauban-x402-stark-receipt`](https://pypi.org/project/vauban-x402-stark-receipt/) · 3 Rust crates on crates.io (`vauban-x402-jcs-conformance`, `vauban-x402-canonical`, `vauban-x402-wire`) | x402 STARK Receipts production deployment under Vauban-authored IETF I-D family `draft-vauban-x402-stark-receipts-01` + 4 companion drafts. PaymentDemoEmitter contract on Starknet Sepolia (`0x044dd87a…19ff`) emits receipts pinned to `canon_version: jcs-rfc8785-v1`. JCS library: `serde_jcs@0.2.0` (also the 5th-impl Rust validator in the AlgoVoi cross-validation matrix). | `canon_version: jcs-rfc8785-v1` (self-declared by Vauban in their own [ADOPTERS.md](https://github.com/vauban-org/x402-stark-receipts-conformance/blob/main/ADOPTERS.md)) | 2026-05-22 (Vauban-authored IETF I-D `draft-vauban-x402-stark-receipts-00` submitted to datatracker); 2026-05-26 (registered in AlgoVoi Substrate Adopters Registry per Vauban-side self-declared canon\_version emission) | [Vauban ADOPTERS.md](https://github.com/vauban-org/x402-stark-receipts-conformance/blob/main/ADOPTERS.md) (self-declared `canon_version: jcs-rfc8785-v1` emission) · [`draft-vauban-x402-stark-receipts`](https://datatracker.ietf.org/doc/draft-vauban-x402-stark-receipts/) (Vauban-authored receipt format anchoring to AlgoVoi canonicalisation discipline) · [PaymentDemoEmitter on Starknet Sepolia](https://sepolia.voyager.online/contract/0x044dd87a94a801cf775d4c5e4b6703102d4e97e1cd1d0a8879341219ae4f19ff) | | **SchemaStore** | [`SchemaStore/schemastore`](https://github.com/SchemaStore/schemastore) | The AlgoVoi compliance-receipt JSON Schema (`algovoi-compliance-receipt-v1.json`) is published in the canonical SchemaStore registry, consumed by VS Code, JetBrains, and other editors. The schema's `canon_version` documentation pins the discipline and cites x402 PR #2436. | `jcs-rfc8785-v1` | 2026-07-11 (observed via marker sweep) | [`algovoi-compliance-receipt-v1.json`](https://github.com/SchemaStore/schemastore/blob/master/src/schemas/json/algovoi-compliance-receipt-v1.json) | | **EPI Recorder** (EPI Labs) | [`mohdibrahimaiml/epi-recorder`](https://github.com/mohdibrahimaiml/epi-recorder) · [pypi `epi-recorder`](https://pypi.org/project/epi-recorder/) | EPI manifest content-addressable identity `canonical_hash = SHA-256(JCS(model_dump))`; the interop doc cites the AlgoVoi corpus, canonicalisation-substrate, and authorship-provenance as normative references, with byte-identical canonical bytes cross-tested against the published corpus. | `jcs-rfc8785-v1` | 2026-06-22 | [`EPI-ALGOVOI-INTEROP.md`](https://github.com/mohdibrahimaiml/epi-recorder/blob/main/docs/EPI-ALGOVOI-INTEROP.md) | | **Vaara** | [`vaaraio/vaara`](https://github.com/vaaraio/vaara) | `vaara.receipt/v1`: `receipt_hash = sha256(JCS(...))` with `signature`/`frame_id` excluded from the preimage; the SEP-2828 conformance corpus recomputes byte-for-byte under `algovoi-substrate`. | `jcs-rfc8785-v1` | 2026-06-22 | [`SPEC.md`](https://github.com/vaaraio/vaara/blob/main/SPEC.md) | | **Verifiable Agent Trust Envelope** (VATE) | [`Poke-nushi/Verifiable-Agent-Trust-Envelope`](https://github.com/Poke-nushi/Verifiable-Agent-Trust-Envelope) | External evidence vectors pin `canon_pin = urn:x402:canonicalisation:jcs-rfc8785-v1`; pins a slice of the AlgoVoi conformance corpus by commit (`pef_v1`, `execution_ref_v1`, `ap2_omh_v0`). | `jcs-rfc8785-v1` | 2026-06-26 | [`external-evidence-vector-pins.md`](https://github.com/Poke-nushi/Verifiable-Agent-Trust-Envelope/blob/main/docs/interop/external-evidence-vector-pins.md) | | **Aura** (Naridon-Inc) | [`Naridon-Inc/aura`](https://github.com/Naridon-Inc/aura) | Rust attestation crate carrying the `jcs-rfc8785-v1` canonicalisation version pin, with the v2 pin also present. | `jcs-rfc8785-v1`, `jcs-rfc8785-v2` | 2026-06-22 | [`aura-attestation/src/lib.rs`](https://github.com/Naridon-Inc/aura/blob/master/crates/aura-attestation/src/lib.rs) | | **Faramesh** | [`faramesh/faramesh-core`](https://github.com/faramesh/faramesh-core) | `record.go` exposes `jcs-rfc8785-v1` as a canonicalisation mode alongside `legacy-json-v1`. | `jcs-rfc8785-v1` | 2026-06-22 | [`record.go`](https://github.com/faramesh/faramesh-core/blob/main/internal/core/dpr/record.go) | | **AgentGraph** | [`agentgraph-co/agentgraph`](https://github.com/agentgraph-co/agentgraph) | Maintains a `docs/conformance/algovoi-jcs-v1` conformance set pinned to the AlgoVoi corpus and emits trust-score-envelope canonicalization `jcs-rfc8785-v1`. | `jcs-rfc8785-v1` | 2026-06-22 | [`conformance/algovoi-jcs-v1/README.md`](https://github.com/agentgraph-co/agentgraph/blob/main/docs/conformance/algovoi-jcs-v1/README.md) | | **SafeAgent** | [`azender1/SafeAgent`](https://github.com/azender1/SafeAgent) | Conformance fixtures (`exactly-once-v1`, `attestation-gate`) declare `preimage_format jcs-rfc8785-v1`. | `jcs-rfc8785-v1` | 2026-06-22 | [`exactly-once-v1.json`](https://github.com/azender1/SafeAgent/blob/main/docs/conformance/exactly-once-v1.json) | | **agent-governance-vocabulary** (aeoess) | [`aeoess/agent-governance-vocabulary`](https://github.com/aeoess/agent-governance-vocabulary) | Trust-evidence-format synthesis matrix referencing the `canon_version` mechanism and `algovoi-substrate-pqc`. | `jcs-rfc8785-v1` / `v2` (referenced) | 2026-07-11 (observed via marker sweep) | [`a2a-1734-trust-evidence-format-matrix-v1.md`](https://github.com/aeoess/agent-governance-vocabulary/blob/main/docs/synthesis/a2a-1734-trust-evidence-format-matrix-v1.md) | | **moltrust-api** (MoltyCel) | [`MoltyCel/moltrust-api`](https://github.com/MoltyCel/moltrust-api) | Backlog referencing the `algovoi-substrate` JCS / RFC 8785 + SHA-256 + Ed25519 receipt cluster. | `algovoi-substrate` (referenced) | 2026-07-11 (observed via marker sweep) | [`BACKLOG.md`](https://github.com/MoltyCel/moltrust-api/blob/main/docs/BACKLOG.md) | | **Universal Commerce Protocol** (UCP) | [`Universal-Commerce-Protocol/ucp`](https://github.com/Universal-Commerce-Protocol/ucp) | Mandate-evaluation-and-receipts builds mandate receipts on JCS (RFC 8785) then SHA-256 for unsigned recomputable content with integer-epoch fields; PR co-attributes to `@chopmob-cloud`. | `jcs-rfc8785-v1` (model) | 2026-06-19 | [`ucp PR #540`](https://github.com/Universal-Commerce-Protocol/ucp/pull/540) | | **NautilusOSS** | [`NautilusOSS/cashstash`](https://github.com/NautilusOSS/cashstash) | Aligns its canonical `voiAddress` derivation to the AlgoVoi canonicalisation, with prose attribution. | `jcs-rfc8785-v1` (model) | 2026-06-22 | [`cashstash`](https://github.com/NautilusOSS/cashstash) | The registry is observed at the time of the most recent revision below. Adopters present at observation but not listed above are invited to submit an entry via the process in the next section. ## Ecosystem and distribution Beyond parties that pin the canonicalisation version directly, the substrate is carried in ecosystem and bibliographic datasets. These are recorded here as distribution surfaces, distinct from the discipline adopters above: * **IETF Relaton** ([`ietf-tools/relaton-data-ids`](https://github.com/ietf-tools/relaton-data-ids), mirrored at [`relaton/relaton-data-ids`](https://github.com/relaton/relaton-data-ids)) -- the IETF Relaton bibliographic dataset carries metadata records for the `draft-hopley-x402-*` Internet-Draft family (canonicalisation-jcs, rfc9421-binding, refund-receipt, cancellation-receipt, settlement-attestation, composite-trust-query, retention-chain, payment-evidence-frame, pqc-credential-binding), each with datatracker source links. * **Electric Capital** ([`electric-capital/open-dev-data`](https://github.com/electric-capital/open-dev-data)) -- the Electric Capital open-dev-data ecosystem dataset lists the `algovoi-mcp` package within its mapped developer ecosystem. ## Convergent implementations (code users) Distinct from the adopters above, these projects were created after the 2026-05-24 publication of the canonicalisation discipline and independently implement the same JCS (RFC 8785) plus SHA-256 content-addressed receipt construction. They are recorded here as a **convergence signal, not as substrate adopters**: each was verified by direct file read to use the construction, but none carries the distinctive tells (integer-millisecond `*_at_ms` timestamps, integer minor-unit `*_minor` amounts) or an attribution reference, so derivation from the AlgoVoi substrate is not established. Inclusion records observed use of the construction pattern; it does not imply the project derives from or endorses AlgoVoi, nor the reverse. | Project | Created | Construction observed | Evidence | | ------------------------------------------------------------------------------------------------------------------------- | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [`halvrenofviryel/ai-runtime-evidence-protocol`](https://github.com/halvrenofviryel/ai-runtime-evidence-protocol) (AIREP) | 2026-05-31 | RFC 8785 JCS + `sha256:` prefix + `*_ref` content-addresses (3 of 4 tells; RFC-3339 timestamps, no attribution) | [`spec/airep/v0.1/SPEC.md`](https://github.com/halvrenofviryel/ai-runtime-evidence-protocol/blob/main/spec/airep/v0.1/SPEC.md) | | [`agentrust-io/cmcp`](https://github.com/agentrust-io/cmcp) | 2026-06-03 | RFC 8785 JCS + `sha256:` prefix + an `action_ref` over `{agent_id, action_type, scope, timestamp}` (3 of 4 tells; RFC-3339 timestamps, no attribution) | [`docs/spec/embodied-action-evidence.md`](https://github.com/agentrust-io/cmcp/blob/main/docs/spec/embodied-action-evidence.md) | | [`lattice-substrate/gev-canonical`](https://github.com/lattice-substrate/gev-canonical) | 2026-05-31 | Formally-verified (Lean) RFC 8785 JCS canonicalizer with a `sha256:` digest prefix | [`lean/Lattice/Substrate/Spec/Sha256.lean`](https://github.com/lattice-substrate/gev-canonical/blob/main/lean/Lattice/Substrate/Spec/Sha256.lean) | | [`cullenmeyers/BoundaryAttest`](https://github.com/cullenmeyers/BoundaryAttest) | 2026-05-25 | RFC 8785 JCS + `sha256:`-prefixed artifact hashes | [`docs/schemas/interop-receipt-v0.1.schema.json`](https://github.com/cullenmeyers/BoundaryAttest/blob/main/docs/schemas/interop-receipt-v0.1.schema.json) | | [`A-Comm-Tech/a-comm-evidence-protocol`](https://github.com/A-Comm-Tech/a-comm-evidence-protocol) | 2026-07-02 | RFC 8785 JCS + `sha256:` prefix (RFC-3339 timestamps hashed verbatim, own copyright) | [`vectors/v1.0.3-rc.2/h-canonicalization.json`](https://github.com/A-Comm-Tech/a-comm-evidence-protocol/blob/main/vectors/v1.0.3-rc.2/h-canonicalization.json) | | [`hassard0/vcp`](https://github.com/hassard0/vcp) | 2026-06-13 | `sha256(JCS(...))` capability and invocation hashing with `sha256:` prefix | [`schemas/invocation.schema.json`](https://github.com/hassard0/vcp/blob/main/schemas/invocation.schema.json) | | [`danielmalka/chainbind-go`](https://github.com/danielmalka/chainbind-go) | 2026-07-09 | RFC 8785 JCS (`gowebpki/jcs`) within a sealed-intent scheme (own copyright) | [`cmd/chainbind/seal.go`](https://github.com/danielmalka/chainbind-go/blob/main/cmd/chainbind/seal.go) | ## Adopter authorship principle Adopters publishing vector sets, receipt-format extensions, or production artefacts under the canonicalisation discipline retain authorship of their own work. The registry records the adoption fact, not co-authorship of the underlying discipline. The discipline itself is AlgoVoi-authored under sole authorship. Substrate authorship history is catalogued at [Substrate Authorship and Provenance](/substrate-authorship-provenance). This separation is deliberate. An adopter publishing (say) a new vector set anchored to `canon_version: jcs-rfc8785-v1` is the author of that vector set; AlgoVoi is the author of the canonicalisation discipline the vector set anchors to. Both facts are recorded; neither displaces the other. ## Citation discipline Adopters listed in this registry typically surface the canonicalisation discipline they anchor to in their own public artefacts. The following citation patterns make the substrate-author lineage traceable across downstream surfaces -- useful both for year-N audit reconstruction and for ecosystem clarity about which discipline a particular artefact anchors to: * **In adopter spec text or normative documentation:** the URN `urn:x402:canonicalisation:jcs-rfc8785-v1` and the IETF Internet-Draft [`draft-hopley-x402-canonicalisation-jcs-v1`](https://datatracker.ietf.org/doc/draft-hopley-x402-canonicalisation-jcs-v1/) cited as the normative reference. * **In adopter package READMEs, API docs, or developer-facing surfaces:** a link to this registry entry (`https://docs.algovoi.co.uk/adopters`) alongside the package's own documentation. * **In adopter conformance vector sets or reference implementations:** the `canon_version: jcs-rfc8785-v1` value in-band, byte-stable across the artefact. Where an adopter publishes derivative or extension artefacts (new URNs under their own namespace, sub-type registries, applied-domain extensions), the underlying canonicalisation discipline is the load-bearing dependency. Citing it at the point where the substrate composition makes the dependency normative preserves the lineage for downstream consumers. The registry records observed adoption regardless of citation completeness. The patterns above describe the typical citation shape; they are not gating conditions for inclusion. ## Attribution badge Adopters who want a one-step way to surface the substrate they build on can drop this badge into a README or a docs page. It names the discipline and links back to this registry, so downstream consumers can trace the lineage. Attribution is welcomed, not required (see Citation discipline above). **Markdown (for a README):** ```md theme={null} [![Built on the AlgoVoi JCS substrate](https://img.shields.io/badge/substrate-jcs--rfc8785--v1-00C8FF)](https://docs.algovoi.co.uk/adopters) ``` **HTML:** ```html theme={null} Built on the AlgoVoi JCS substrate ``` **Plain text (for a NOTICE file or a spec acknowledgement):** ```text theme={null} Built on the AlgoVoi JCS canonicalisation substrate (urn:x402:canonicalisation:jcs-rfc8785-v1) https://docs.algovoi.co.uk/adopters ``` The badge renders as: **Built on the AlgoVoi JCS substrate** linking to this page. It uses a static shields.io image (no hosting required on the adopter side). ## How to submit an adoption entry To be listed in the registry, an adopter MUST publish at least one artefact that pins `canon_version: jcs-rfc8785-v1` in-band, in a publicly-citable surface (GitHub repository, package registry, IETF I-D, hosted public endpoint). Once published, submit via one of the following paths: 1. **Pull request** against [`chopmob-cloud/docs`](https://github.com/chopmob-cloud/docs), editing this page (`adopters.mdx`) to add a row. 2. **GitHub issue** at [`chopmob-cloud/algovoi-jcs-conformance-vectors/issues`](https://github.com/chopmob-cloud/algovoi-jcs-conformance-vectors/issues/new) titled `Adopter registry submission: {your-identifier}`. 3. **Email** to [hello@algovoi.co.uk](mailto:hello@algovoi.co.uk) with subject `Adopter registry submission` and the row fields below. Required fields: * **Adopter**: human-readable name of the publishing party. * **Identifier**: a stable public identifier (DNS name, GitHub handle/org, DID URI, IETF author surname). * **Surface**: what is published (vector set, reference implementation, hosted endpoint, I-D, production service). * **Anchor**: the specific `canon_version` value pinned by the surface (currently `jcs-rfc8785-v1`). * **First observed**: ISO-8601 date the surface first published the anchor. * **Evidence**: at least one URL pointing to the publicly-citable artefact. Submissions are validated by AlgoVoi against the artefact's canonical bytes. The registry records whatever the artefact emits in-band; in particular, the registry does NOT validate the artefact's correctness against any vector set or specification, only that it pins the canonicalisation discipline. ## Withdrawal An adopter MAY request removal at any time by the same submission paths. Withdrawn entries are not deleted but moved to a "Withdrawn (historical record)" section below to preserve the year-N audit history of the registry itself. The audit-chain of registry edits is recorded in the git history of [`chopmob-cloud/docs`](https://github.com/chopmob-cloud/docs). ## Withdrawn (historical record) *None at this revision.* ## Machine-readable mirror A machine-readable JSON-LD mirror of the registry is maintained alongside this page at [`docs.algovoi.co.uk/adopters.json`](/adopters.json) for automated consumption by composite-trust-query verifiers and downstream tooling. ## See also * [Canonicalisation substrate](/canonicalisation-substrate) -- the JCS discipline * [Substrate Authorship and Provenance](/substrate-authorship-provenance) -- authorship record * [Conformance vectors](/conformance-vectors) -- vector corpus the registry refers to * [Agent Passport](/agent-passport) -- post-quantum identity credentials for AI agents built on the substrate * IETF Internet-Draft [`draft-hopley-x402-canonicalisation-jcs-v1`](https://datatracker.ietf.org/doc/draft-hopley-x402-canonicalisation-jcs-v1/) Appendix C "Known Adopters"