Substrate Authorship and Provenance

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.

​

The substrate, in one sentence

​

Authored artefacts at a glance

​

Temporal authorship timeline

​

What this substrate provides

+----------------------------------------------------------+
|  AlgoVoi-authored substrate                              |
+----------------------------------------------------------+
|                                                          |
|  Canonicalisation discipline                             |
|    (IETF I-D §4; published at /canonicalisation-substrate)|
|    - JCS RFC 8785 pin                                    |
|    - Substrate Rule 2: timestamp_ms MUST be integer      |
|    - Field-name + array-order + type-validation rules    |
|                                                          |
|  Primitives (in algovoi-substrate v0.3.0)                |
|    - canonicalize(obj) -> JCS canonical string           |
|    - action_ref(agent_id, action_type, scope, ts)        |
|        -> SHA-256 of the canonical preimage              |
|    - transition_hash + build_transactional_action_chain  |
|    - build_compliance_receipt + verify_audit_chain       |
|    - composite_trust_query_hash                          |
|                                                          |
|  Receipt format (draft-hopley-x402-compliance-receipt)|
|    - Closed enum {ALLOW, REFER, DENY}                    |
|    - payer_ref content-addressed reference               |
|    - integer screen_timestamp_ms                         |
|    - canon_version in-band pin                           |
|    - jurisdiction_flags ordered list                     |
|    - screen_provider_did DID URI                         |
|                                                          |
|  Audit chain                                             |
|    - content_hash per row                                |
|    - prev_hash linkage                                   |
|    - Object Lock COMPLIANCE 7y retention (S3)            |
|                                                          |
|  Conformance corpus (77 JCS vectors / 9 anchor sets)     |
|    - 8-impl byte-for-byte: 192/192 agreements            |
|                                                          |
+----------------------------------------------------------+

​

Contributions acknowledged (historical record)

​

What this substrate is NOT

• Not a closed-enum on every field. scope is a non-empty string, not a closed enum. The substrate publishes naming conventions (e.g. {emitter}:{scope} namespacing) as non-normative recommendations.
• Not a single-vendor lock-in. Five (now eight) independent JCS implementations produce byte-identical canonical bytes. A buyer can swap any one for another without changing the receipt format.
• Not a complete reputation system. The substrate produces evidence (compliance attestations, settlement receipts, audit chains); scoring layers like Verascore consume that evidence. AlgoVoi does not author Verascore.
• Not the only substrate in the space. Other independent authors have published related but separable receipt and settlement formats: Vauban Pay (STARK settlement proofs, in draft-vauban-x402-stark-receipts), Concordia (commitment receipts), nobulex (bilateral receipts), Agent OS (committed claims). These compose against the canonicalisation substrate without redefining it. AlgoVoi does not represent or speak for any of these parties.

​

Verifying the claims on this page independently

# 1. AlgoVoi substrate primitives (Python)
pip install algovoi-substrate==0.3.0
python -c "from algovoi_substrate import action_ref; print(action_ref('agent_alpha','payment','vauban:stark_settlement',1716494400000))"
# expects: 7528529a8be2044488e603b7913efaa4f83620dbcc63010d4a1478cf7e9a473c

# 2. AlgoVoi substrate primitives (TypeScript)
npm install @algovoi/substrate@^0.3.0
node -e "import('@algovoi/substrate').then(m => console.log(m.actionRef({agent_id:'agent_alpha',action_type:'payment',scope:'vauban:stark_settlement',timestamp_ms:1716494400000})))"
# expects the same digest

# 3. RFC 9421 HTTP signature verifier
pip install algovoi-rfc9421-verifier==0.1.0
# Then verify a captured request: see the package README

# 4. Full conformance corpus
git clone https://github.com/chopmob-cloud/algovoi-jcs-conformance-vectors
cd algovoi-jcs-conformance-vectors/vectors/compliance_receipt_v1
python runner_python.py   # expects: PASS 8 vectors + 5 pair invariants + 3 chain invariants
node runner_node.js       # expects: PASS

# 5a. JCS 8-implementation matrix
# See _attestations/2026-05-24-8-impl-cross-validation.md for the 8-language reproduction commands.

# 5b. RFC 9421 + Ed25519 + SHA-256 8-implementation matrix
cd algovoi-jcs-conformance-vectors/vectors/rfc9421_proxy_chain_v0
bash run_all.sh           # expects: 8/8 PASS (Python, Node, Go, Rust, Java, PHP, .NET, Ruby)

# 6. IETF Internet-Draft
curl -sL https://www.ietf.org/archive/id/draft-hopley-x402-compliance-receipt.txt | head -30

# 7. JSON Schema (auto-loaded by every JSON-aware IDE)
curl -s https://json.schemastore.org/algovoi-compliance-receipt-v1.json | head -20

# 8. Refund receipt format (standalone AlgoVoi-authored package)
npm install @algovoi/refund-receipt @algovoi/substrate
node -e "import('@algovoi/refund-receipt').then(m => import('@algovoi/substrate').then(s => { const r = m.buildRefundReceipt({original_payment_ref:'sha256:0dd5d0b76c9b9281fdeb2509ad38ab132b16a17385ca01d976ff9e6e12563a0f',refund_result:'FULL',refund_timestamp_ms:1716494400000,refund_provider_did:'did:example:refund-provider-1',refund_amount:{amount_minor:'100000',asset_id:'USDC.6'},jurisdiction_flags:['UK','EU']}); console.log(s.sha256Jcs(r)); }))"
# expects: 7fdd283c3a8abb14d893999d1d16e2f7697ad0539250f2e0fc3e31ce89943dcb

​

Coalition position

• Under AlgoVoi control: production endpoints (api.algovoi.co.uk, verify.algovoi.co.uk), Mintlify docs (docs.algovoi.co.uk), chopmob-cloud GitHub repos.
• Under neutral public registries: PyPI, npm, IETF datatracker, JSON SchemaStore, GitHub itself.

• IETF I-D + Mintlify page under sole AlgoVoi authorship. The first post-exit example is the refund receipt (algovoi-refund-receipt v0.1.0 published to npm 2026-05-24; live-tested 17/17 byte-identical against the conformance vector set; companion I-D draft-hopley-x402-refund-receipt and Mintlify page at /refund-receipt).

​

See also

• Canonicalisation substrate — the normative discipline + the 8-impl matrix
• x402 Document Index — neutral index of all IETF I-Ds and published specifications in the x402 receipt-format ecosystem, organised by author and by canonicalisation-anchor citation
• Substrate Adopters Registry — record of parties publishing artefacts under canon_version: jcs-rfc8785-v1
• Conformance vectors — the 7-set conformance corpus (512 byte-for-byte cross-impl agreements)
• Audit verifier — the productized verifier consuming substrate output
• Ecosystem contributions — full upstream PR list
• IETF I-D draft-hopley-x402-canonicalisation-jcs-v1 — the canonicalisation discipline itself and the URN registration (Section 10.1)
• IETF I-D draft-hopley-x402-compliance-receipt — admission-time compliance receipt format
• JCS 8-impl cross-validation attestation — 512/512 byte-for-byte agreements record
• RFC 9421 8-impl cross-validation attestation — 24/24 signing-base + content-digest + Ed25519 agreements

​

Provenance of this page

• 2026-05-24 ~10:30: Coalition exit recorded; refund receipt v0.1.0 added as the 12th artefact; surface count moved from 12 to 14 with the addition of refund receipt and its companion IETF I-D.
• 2026-05-24 ~11:20: Canonicalisation discipline I-D added as 14th artefact (recovers closed-PR-#2436 work under sole AlgoVoi authorship); surface count moved from 14 to 15. Future receipt I-Ds normatively reference this discipline I-D instead of redefining §4 inline.
• 2026-05-25 ~14:30: x402 Document Index published at /x402-document-index cataloguing all 13 IETF I-Ds in x402 namespace (6 AlgoVoi sole-authored + 6 Vauban + 1 Sato/Soos). The index records anchor-citation coverage: 7 of 12 in-scope receipt-format I-Ds cite urn:x402:canonicalisation:jcs-rfc8785-v1 explicitly; 5 reference the canonicalisation discipline by terminology and RFC 8785 only, without URN citation. The URN registration in Section 10.1 of draft-hopley-x402-canonicalisation-jcs-v1 is the authoritative registration; documents using the discipline are encouraged to cite the URN normatively so cross-spec verifiers can resolve the registration unambiguously.
• 2026-05-25 ~14:35: Acknowledgments revisions filed: draft-hopley-x402-canonicalisation-jcs-v1-02, draft-hopley-x402-compliance-receipt-02, and draft-hopley-x402-refund-receipt-02 filed on IETF datatracker with Andy Salvo (Crest Deployment Systems LLC) credited for the timestamp_ms epoch-integer canonical preimage convention (Substrate Rule 2 of the canonicalisation I-D). Acknowledgment is consistent with how FeedOracle is credited (specific substantive contribution to the discipline). Substrate-author position retains sole-AlgoVoi authorship of the discipline itself; specific contributions are credited at the appendix layer.