> ## 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.
# Conformance vector sets
> 45 JCS conformance anchor sets covering the full receipt lifecycle: 374 vectors and 1226 byte for byte agreements across ten reference implementations.
The **AlgoVoi JCS Conformance Vectors** are the open, byte-for-byte conformance corpus for agentic-payment canonicalisation: 45 anchor sets and 374 vectors (corpus `manifest.json` v0.38.0) that pin the exact bytes and SHA-256 hashes of the receipt, mandate, and reference-chain lifecycle, cross-validated across ten independent language implementations at 1226/1226 agreements and reproducible offline with no AlgoVoi infrastructure.
*Last updated: 3 August 2026.*
The canonicalisation substrate is anchored by **45 conformance vector sets** totalling **374 vectors** (authoritative totals in the corpus `manifest.json`, v0.38.0, 2026-07-21). Sixteen sets were validated byte-for-byte across **ten independent reference implementations** (Python, TypeScript, Go, Rust, Java, PHP, .NET, Ruby, Elixir, Kotlin) at **1226/1226 directly-executed agreements** (cumulative through 2026-07-21); a further set (`zkp_receipt_v1`) was directly executed across five implementations on 2026-06-04, with the remaining three confirmed by transitivity. The newest sets, the open decision-chain lite family (`agent_passport_lite_v1`, `payment_mandate_lite_v1`, `compliance_gate_lite_v1`, `spend_guardrail_lite_v1`, `cancellation_receipt_lite_v1`, `refund_receipt_lite_v1`, `composite_trust_query_lite_v1`) plus `substrate_guard_v1`, are cross-validated Python and TypeScript byte-for-byte. They compose into one recomputable lifecycle, proven end to end by the `spend_decision_chain_v1` keystone (8/8 links).
**2026-07-09:** Elixir (`jcs`, pzingg/jcs on hex.pm) and Kotlin/JVM (`java-json-canonicalization`) were added and directly executed against all 11 of the previously-8-language sets (`retention_chain_v1`, `retention_chain_v0`, `compliance_receipt_v1`, `settlement_attestation_v1`, `cancellation_receipt_v1`, `refund_receipt_v1`, `composite_trust_query_v1`, `action_ref_exactly_once_v1`, `pef_v1`, `epi_interop_v0`, `epi_pqc_v0` JCS vectors), each independently byte-for-byte verified against the existing expected hashes -- see the corpus repo's `_attestations/2026-07-09-*.md` files. On 2026-07-19 Elixir and Kotlin were extended to the remaining 3 sets, and a new edge-case set (`jcs_edge_v1`: U+2028/U+2029 literal UTF-8, non-BMP key ordering by UTF-16 code units, 1.0 vs 1) was added across all ten implementations from inception -- which also caught and patched a U+2028/float gap in the corpus's own stdlib PHP serialiser, the PHP instance of the a2a-go#368 fix. Combined directly-executed total: 1226/1226.
The original four sets are published as standalone public gists under `gist.github.com/chopmob-cloud/`. All twenty-five sets - covering the full receipt lifecycle (compliance, settlement, cancellation, refund, composite-trust-query), the Payment Evidence Frame, the ZKP receipt, the exactly-once action lifecycle and adversarial isolation fixtures, RFC 9421 HTTP signatures (legacy algovoi-v0 base **and** the RFC 9421 §2.5-conformant `rfc9421_proxy_chain_v1`), and the Ed25519 multi-chain fixture - are published in the [`chopmob-cloud/algovoi-jcs-conformance-vectors`](https://github.com/chopmob-cloud/algovoi-jcs-conformance-vectors) corpus repo with per-set runners for ten language implementations. The repo `manifest.json` is the authoritative per-set inventory (counts + LF-pinned SHA-256). No login is required to view or reproduce any of them.
**L1 and L2.** These sets anchor AlgoVoi's authored **L1** in two parts - the RFC 8785 (JCS) canonicalisation substrate **and** the RFC 9421 §2.5 signing-base (`rfc9421_proxy_chain_v1`). Layers built on top are **L2** (e.g. `rfc9421_receipt_evidence_v0`): build them freely; the one ask is to **attribute the L1** you build on (keep the NOTICE, import by hash).
For the normative rules, the ten-implementation matrix, and how to validate against these sets, see [JCS Canonicalisation Substrate](/canonicalisation-substrate).
## The four anchor sets
7 vectors, 4 pair-invariants. Content-addressable mandate hash for AP2 payment mandates. Anchors AP2 issue #265.
14 vectors (4 CTEF + 10 APS), 10 pair-invariants. Composable trust-evidence and agent-passport receipt canonicalisation. Anchors the A2A #1734 v0.3.3 rows. Removed from the corpus 2026-06-23.
13 vectors, 12 pair-invariants. Settlement-plane visibility attestation canonicalisation. Anchors x402 PR #2334.
19 vectors across 7 chain families, 9 pair-invariants. Chain-native amount and address field canonicalisation.
The four original gist-based sets total 53 vectors. Five additional sets are published in the corpus repo:
| Set | Vectors | Coverage |
| -------------------------------------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `action_ref_namespace_v0` | 8 | Namespace-prefixed action\_ref canonicalisation |
| `action_ref_transactional_v0` | 8 | Transactional action chain + transition\_hash |
| `compliance_receipt_v1` | 8 | Full compliance receipt lifecycle (+5 pair / 3 chain invariants) |
| `settlement_attestation_v1` | 9 | Post-settlement attestation (SETTLED / PENDING\_FINALITY / REVERSED) |
| `cancellation_receipt_v1` | 8 | Mandate / checkout cancellation receipt |
| `refund_receipt_v1` | 8 | Post-settlement refund receipt (FULL / PARTIAL) |
| `composite_trust_query_v1` | 8 | Top-of-stack composite trust verdict |
| `pef_v1` | 8 | Payment Evidence Frame `frame_id` derivation + claim serialisation |
| `zkp_receipt_v1` | 8 | Zero-knowledge settlement receipt across 7 chains (ePrint 2026/109852) |
| `service_trust_v0` | 5 | Service-trust check envelope |
| `rfc9421_proxy_chain_v0` | 1 fixture | Legacy **algovoi-v0** signing-base HTTP signature survival - RFC 9530 + Ed25519 (8-impl, 24/24 checks) |
| `rfc9421_proxy_chain_v1` | 1 fixture | **RFC 9421 §2.5-conformant** HTTP signature survival - RFC 9530 + Ed25519 (8-impl, 8/8) |
| `multichain_ed25519_substrate_v0` | 3 | Ed25519 multi-chain signing over a shared canonical payload |
| `retention_chain_v0` | 3 | Retention Chain Substrate -- `chain_ref = sha256(JCS({chain_seq, issuer_id, prev_receipt_hash, receipt_hash}))` across genesis + 2 chain-link vectors. Normative spec: `draft-hopley-x402-retention-chain-05`. |
| `retention_chain_v1` | 14 | Retention Chain Substrate v1 -- extended conformance. Part A: 6-link extended chain (`algovoi:compliance`, seq 0-5). Part B: 4 multi-issuer isolation vectors (same receipt, different `issuer_id`, chain\_ref must differ). Part C: 4 seq-gap adversarial pair (proper `seq2` vs gap `seq2` -- same `receipt_hash`, wrong `prev_receipt_hash`, chain\_ref provably different). Normative spec: `draft-hopley-x402-retention-chain-05`. |
| `action_ref_exactly_once_v1` | 6 | Exactly-once `action_ref` lifecycle (`PENDING → COMMITTED → REVERSED`). Pins the SKIP-on-retry idempotency invariant (vector 005 == 003 byte-for-byte) and the `action_ref` replay-binding invariant (vector 006 ≠ 003). 5 pair invariants. Normative spec: `draft-hopley-x402-retention-chain-05` §7. |
| `adversarial_isolation_v1` | 12 | Failure-isolation adversarial set: 1 control + 11 isolated rejection vectors. Each mutates exactly one field to confirm a named substrate check rejects it. Claim 1 (input bytes): 8-lang byte-identical. Claim 2 (rejection): reference-impl PoR. Normative spec: `draft-hopley-x402-retention-chain-05` §7.5 + §8.8. |
| [`jcs_edge_v1`](/canonicalisation-substrate) | 10 | RFC 8785 edge classes an ad-hoc "sorted-keys JSON" gets wrong: U+2028 / U+2029 as literal UTF-8 (3.2.4), supplementary-plane key ordering by UTF-16 code units (3.2.3), and the 1.0-versus-1 number form (3.2.2.3). Validated across all ten implementations from inception. |
| [`jws_anchor_v1`](/signed-token-anchoring) | 6 | **Signed-token anchoring**: which bytes you hash. 5 of 6 vectors carry `anchor_rule: signed_bytes`, so the anchor is SHA-256 over the raw signed JWS / SD-JWT bytes, never a re-serialised object; 1 vector is the unsigned JCS case. 4 invariants. Cross-validated as two populations: ten implementations for its JCS-dependent points, eight crypto-capable ones for Ed25519. |
45 sets total, 374 vectors (authoritative totals in the corpus `manifest.json`, v0.38.0, 2026-07-21). A separate grammar set, `caip_edge_v1` (102 vectors), pins CAIP-2/10/19 identifier verdicts rather than canonical bytes and is deliberately NOT folded into these anchor-set totals. All sets are published under Apache 2.0 except `retention_chain_v0` and `retention_chain_v1`, which are published under the AlgoVoi Commercial Software Licence. The PQC signature-suite set (AP2 PQC v0, Falcon-1024 + ML-DSA-65 + ES256 + Ed25519) is documented separately on the [PQC substrate page](/pqc-substrate).
## Reproducing the matrix
All four sets are mirrored in three places so a reviewer can re-run the byte-for-byte matrix from any of them:
`chopmob-cloud/algovoi-jcs-conformance-vectors` -- AlgoVoi-authored standalone repo carrying all four anchor sets in `vectors/`, the JSON Schema for the compliance receipt in `schemas/`, and per-set Python / JS / Go / Java runner harnesses. The canonical citation surface for the matrix.
`x402#2412` places the full 53-vector set in `fixtures/canonicalisation-substrate/v0/` in the x402 Foundation repo, mirroring the gists by content hash.
`agentgraph-co/agentgraph#21` (merged) places the four single-file runners (Python / JS / Go / Java) plus all 53 vectors and 37 pair-invariants in `tests/cross-impl/`.
All sets are published under Apache 2.0, except `retention_chain_v0` and `retention_chain_v1` which are published under the AlgoVoi Commercial Software Licence.
## Reference implementations
The substrate primitives that consume these vectors are published as installable packages:
* [`algovoi-substrate`](https://pypi.org/project/algovoi-substrate/) (PyPI, Python) - wraps `rfc8785@0.1.4` with the discipline rules.
* [`@algovoi/substrate`](https://www.npmjs.com/package/@algovoi/substrate) (npm, TypeScript) - byte-for-byte parity with the Python sibling.
Either package validates an implementation against the full vector set with a few lines of code. For the complete ten-language runner harness (Python, TypeScript, Go, Rust, Java, PHP, .NET, Ruby, Elixir, Kotlin), see the per-set runners in the corpus repo. The 1226/1226 cumulative cross-implementation total:
| Attestation | Scope | Agreements |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [`2026-05-24-8-impl-cross-validation.md`](https://github.com/chopmob-cloud/algovoi-jcs-conformance-vectors/blob/main/_attestations/2026-05-24-8-impl-cross-validation.md) | JCS substrate primitives (action\_ref, namespace, transactional) | 192/192 |
| [`2026-05-25-8-impl-5-format-cross-validation.md`](https://github.com/chopmob-cloud/algovoi-jcs-conformance-vectors/blob/main/_attestations/2026-05-25-8-impl-5-format-cross-validation.md) | 5 receipt formats (compliance, settlement, cancellation, refund, composite-trust-query) | 320/320 |
| [`2026-05-30-8-impl-pef-v1.md`](https://github.com/chopmob-cloud/algovoi-jcs-conformance-vectors/blob/main/_attestations/2026-05-30-8-impl-pef-v1.md) | Payment Evidence Frame (frame\_id derivation + claim serialisation) | 64/64 |
| [`2026-06-09-action-ref-exactly-once-v1.md`](https://github.com/chopmob-cloud/algovoi-jcs-conformance-vectors/blob/main/_attestations/2026-06-09-action-ref-exactly-once-v1.md) | Exactly-once lifecycle (PENDING / COMMITTED / REVERSED, SKIP-on-retry, replay-binding) | 48/48 |
| [`2026-06-16-retention-chain-v0-cross-validation.md`](https://github.com/chopmob-cloud/algovoi-jcs-conformance-vectors/blob/main/_attestations/2026-06-16-retention-chain-v0-cross-validation.md) | Retention Chain Substrate (`chain_seq`, `issuer_id`, `prev_receipt_hash`, `receipt_hash`) | 24/24 |
| [`vectors/epi_interop_v0/`](https://github.com/chopmob-cloud/algovoi-jcs-conformance-vectors/tree/main/vectors/epi_interop_v0/) | EPI Recorder interop -- JCS + SHA-256 over EPI manifest payloads | 40/40 |
| [`vectors/epi_pqc_v0/`](https://github.com/chopmob-cloud/algovoi-jcs-conformance-vectors/tree/main/vectors/epi_pqc_v0/) | EPI PQC profile -- JCS + SHA-256 (Falcon-1024 + key-lineage: Python only) | 32/32 |
| [`2026-06-17-retention-chain-v1-cross-validation.md`](https://github.com/chopmob-cloud/algovoi-jcs-conformance-vectors/blob/main/_attestations/2026-06-17-retention-chain-v1-cross-validation.md) | Retention Chain Substrate v1 -- extended chain, multi-issuer isolation, seq-gap adversarial pair | 112/112 |
| [`2026-07-09-elixir-9th-language.md`](https://github.com/chopmob-cloud/algovoi-jcs-conformance-vectors/blob/main/_attestations/2026-07-09-elixir-9th-language.md), [`...kotlin-10th-language.md`](https://github.com/chopmob-cloud/algovoi-jcs-conformance-vectors/blob/main/_attestations/2026-07-09-kotlin-10th-language.md), [`...corpus-extension.md`](https://github.com/chopmob-cloud/algovoi-jcs-conformance-vectors/blob/main/_attestations/2026-07-09-elixir-kotlin-corpus-extension.md), [`...epi-elixir-kotlin.md`](https://github.com/chopmob-cloud/algovoi-jcs-conformance-vectors/blob/main/_attestations/2026-07-09-epi-elixir-kotlin.md) | Elixir + Kotlin added to all 11 previously-8-lang sets | 172/172, plus independent 3-way byte diff on every set |
| **Cumulative (directly executed, all ten implementations)** | 16 sets | **1226/1226** (880 eight-language base through 2026-06-18 + 172 on 2026-07-09 + 44 on 2026-07-19 + 100 jcs\_edge\_v1 across all ten + 30 jws\_anchor\_v1 across all ten on 2026-07-21) |
| [`2026-06-04-zkp-receipt-v1-cross-validation.md`](https://github.com/chopmob-cloud/algovoi-jcs-conformance-vectors/blob/main/_attestations/2026-06-04-zkp-receipt-v1-cross-validation.md) | ZKP receipt -- 5 impls directly executed, 3 by transitivity (primitive-only payload) | 40/40 direct (not folded into cumulative) |
## Proposal sets
Single-implementation AlgoVoi fixtures published for a standards discussion. Not
cross-validated and not folded into the anchor-set or vector totals.
Byte-pin conformance for the optional idempotent create-ATA at instruction index 2 in
the x402 exact SVM scheme. One positive plus three negatives; the accept fixture uses a
real derived ATA and the funder pin closes the rent-sponsorship griefing vector.
Published for x402 issue #2395 / PR #2798.
## Frequently asked questions
### How many JCS conformance vectors does the AlgoVoi corpus contain?
The corpus holds 45 anchor sets and 374 vectors (authoritative totals in
`manifest.json` v0.38.0). The vectors pin the exact canonical bytes and SHA-256
hashes for the receipt, mandate, and reference-chain lifecycle. Separate grammar
and proposal sets are tracked apart and deliberately not folded into the 374-vector
anchor total.
### Which languages are the conformance vectors cross-validated across?
Sixteen sets are directly executed across ten independent JCS implementations
(Python, JavaScript, Go, Rust, Java, PHP, C#/.NET, Ruby, Elixir, and Kotlin),
including the RFC 8785 author's own Java implementation, at 1226/1226 byte-for-byte
agreements cumulative through 2026-07-21. The ten implementations are
non-overlapping, so agreement is real independent corroboration.
### Are the AlgoVoi conformance vectors free to use?
Almost all sets are published under Apache 2.0 and need no login to view or
reproduce. The two exceptions, `retention_chain_v0` and `retention_chain_v1`, are
published under the AlgoVoi Commercial Software Licence. You keep the NOTICE
attribution and import by hash; everything you build on top is yours.
### How do I verify an implementation against the vectors?
Install `algovoi-substrate` (PyPI) or `@algovoi/substrate` (npm) and check your
output against the vector set in a few lines, or clone the corpus and run the
per-set runners for all ten languages. `composition/verify_corpus.py` reproduces
every set byte for byte with no AlgoVoi infrastructure involved.
## See also
* [JCS Canonicalisation Substrate](/canonicalisation-substrate) for the five normative rules and the five-implementation matrix.
* [Cell and KAF](/cell-kaf) for the hermetic runtime that reproduces these vectors and the sealed, offline-verifiable receipt chain over each run.
* [Audit verifier](/audit-verifier) for the hosted + installable verifier that consumes bundles built against this substrate.
* [Ecosystem contributions](/ecosystem-contributions) for the upstream PRs where these sets are referenced.