urn:x402:canonicalisation:jcs-rfc8785-v1). Inclusion is informational; absence is not normative.
The index is organised three ways:
- By IETF posting status — what’s on the datatracker today.
- By author / publisher — who wrote what.
- By canonicalisation anchor — which documents share which canon pin.
Authoritative anchor
The canonicalisation discipline this ecosystem converges on is specified in:- IETF Internet-Draft:
draft-hopley-x402-canonicalisation-jcs-v1(Independent Submission, Informational; AlgoVoi sole authorship) - URN:
urn:x402:canonicalisation:jcs-rfc8785-v1 - Registration authority: Section 10.1 of the I-D above
By IETF posting status
POSTED on IETF datatracker
14 IETF Internet-Drafts in x402 namespace as of 2026-05-30.
- AlgoVoi-authored: 7 (canonicalisation discipline + 6 receipt/frame formats: compliance, settlement, cancellation, refund, composite-trust-query, payment-evidence-frame)
- Vauban-authored: 6 (STARK receipts + lifecycle FSM + claim algebra + Starknet anchor + delegation binding + PQC discipline)
- Sato/Soos-authored: 1 (MJWT, broader agentic-AI authorisation scope)
Canonicalisation anchor coverage
Of the 13 in-scope x402 receipt-format I-Ds (excludingdraft-sato-soos-mjwt):
- 8 of 13 cite
urn:x402:canonicalisation:jcs-rfc8785-v1explicitly (all 7 AlgoVoi I-Ds +draft-vauban-x402-stark-receipts) - 5 of 13 reference “JCS canonical preimage discipline” terminology and RFC 8785 directly, without citing the URN registration registered in §10.1 of
draft-hopley-x402-canonicalisation-jcs-v1(all the post-2026-05-25 Vauban revisions: lifecycle-fsm, vpsf-algebra, starknet-anchor, delegation-binding, pqc-receipts)
canon_version pin) that extend beyond RFC 8785 alone. A normative reference to draft-hopley-x402-canonicalisation-jcs-v1 or the urn:x402:canonicalisation:jcs-rfc8785-v1 URN in next revisions of those I-Ds would make the anchor citation unambiguous; this is observed as an anchor-citation gap at the time of revision below, not as a substrate fork.
The substrate is uni-anchor in implementation (both AlgoVoi and Vauban encode JCS RFC 8785 with the same schema-normalisation rules) and uni-anchor in URN-registration authority (only urn:x402:canonicalisation:jcs-rfc8785-v1 is defined in this namespace). The gap is at the citation layer only.
Published specifications (not yet at IETF)
By author / publisher
AlgoVoi (substrate author)
Vauban Pay (seritalien, egoriklok)
Sato / Soos
Crest Deployment Systems LLC (Andy Salvo)
PEAC Protocol
By canonicalisation anchor
No document published in x402 namespace pins a different canonicalisation URN; the substrate is uni-anchor in URN registration as of the registry revision below.
The 5 Vauban I-Ds in the second row use the discipline as encoded by
draft-hopley-x402-canonicalisation-jcs-v1 (including the schema-normalisation rules extending RFC 8785 — integer-millisecond timestamps, ordered arrays as significant, in-band canon_version pin) but cite only RFC 8785 in Normative References, not the AlgoVoi-authored I-D where the discipline is registered. A normative reference to draft-hopley-x402-canonicalisation-jcs-v1 or the urn:x402:canonicalisation:jcs-rfc8785-v1 URN in next revisions would make the citation unambiguous and consistent with draft-vauban-x402-stark-receipts, which already cites it explicitly.
Any future document publishing a different canonicalisation URN would create a substrate fork; the substrate-author position is committed to maintaining a single canonical anchor and welcomes substrate-layer alignment proposals before any divergence.
Cross-reference: Adopters Registry
Parties publishing artefacts underurn:x402:canonicalisation:jcs-rfc8785-v1 are listed in the Substrate Adopters Registry. The Adopters Registry is the operational record of observed adoption; this Document Index is the bibliographic record of documents in the namespace.
Both surfaces are maintained by AlgoVoi as the substrate author. Authorship of artefacts and authorship of the canonicalisation discipline are separate facts; both surfaces record both.
Cross-impl validation
The 8-implementation cross-validation matrix is the operational evidence of canonicalisation-discipline interop. As of 2026-05-25:
Attestation:
_attestations/2026-05-25-8-impl-5-format-cross-validation.md (JCS); _attestations/2026-05-30-8-impl-cross-validation.md (PEF).
Any new document anchoring to this URN inherits the same cross-impl validation discipline by construction; vector sets for the new document slot into the 8-impl runner suite mechanically.
Maintenance
This index is observed at the time of the most recent revision below. New entries are added via:- Pull request against
chopmob-cloud/docs, editing this page (x402-document-index.mdx). - GitHub issue at
chopmob-cloud/algovoi-jcs-conformance-vectors/issuestitledx402 document index submission: {document identifier}. - Email to [email protected] with subject
x402 document index submission.
- Anchor to
urn:x402:canonicalisation:jcs-rfc8785-v1in-band (viacanon_versionfield, normative reference, or equivalent unambiguous citation). - Be published in a publicly-citable surface (IETF datatracker, package registry, GitHub repository, hosted endpoint, or DID-anchored URL).