Add AlgoVoi Compliance Receipt v1 schema#5726
Merged
madskristensen merged 2 commits intoMay 23, 2026
Merged
Conversation
The AlgoVoi compliance receipt is the categorical screening decision record emitted by an AlgoVoi-discipline screening provider at admission time (ALLOW / REFER / DENY) and retained as part of an audit chain under framework-bound retention obligations (UK MLR 2017 reg 40, EU AMLD5/6, MiCA Art 80, AMLR Art 56, DORA Art 14). The categorical outcome is load-bearing for downstream regulatory obligations -- under UK POCA 2002 s 330 a REFER carries a mandatory SAR obligation that a DENY does not -- so the schema enforces a closed enum on screen_result rather than a score/tier projection. Substrate references: - x402-foundation/x402 PR SchemaStore#2436 (canonicalisation discipline) - x402-foundation/x402 PR SchemaStore#2434 (compliance-receipt-fixture) - chopmob-cloud/algovoi-substrate (reference implementations in Python + TypeScript that produce schema-valid receipts) - chopmob-cloud/algovoi-jcs-conformance-vectors (the canonical home of this schema with examples and per-anchor-set conformance vectors) Includes 3 positive test cases (ALLOW UK+EU, REFER UK with SAR obligation, DENY across UK/EU/US sanctions) and 7 negative cases (missing required field, invalid screen_result, float timestamp, empty jurisdiction_flags, invalid DID format, unknown canon_version, extra field).
chopmob-cloud
requested review from
hyperupcall and
madskristensen
as code owners
Contributor
|
Thanks for the PR! This section of the codebase is owned by @madskristensen and |
chopmob-cloud
added a commit
to chopmob-cloud/algovoi-jcs-conformance-vectors
that referenced
this pull request
May 23, 2026
The schemastore.org submission required draft-07 for broader IDE coverage. All features used by the schema work in draft-07 (closed enum, additional- Properties: false, pattern, minimum, type integer). No functional change to the schema; only the $schema meta-version moves from draft 2020-12 to draft-07. Examples revalidated; algovoi-substrate output revalidated. Schemastore PR: SchemaStore/schemastore#5726
for more information, see https://pre-commit.ci
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a new JSON Schema (
algovoi-compliance-receipt-v1.json) for the AlgoVoi compliance receipt -- a categorical screening decision record emitted at agentic-payment admission time and retained under framework-bound retention obligations (UK MLR 2017, EU AMLD5/6, MiCA Art 80, AMLR Art 56, DORA Art 14).The schema enforces:
screen_result(ALLOW/REFER/DENY). The categorical outcome is load-bearing for downstream regulatory obligations -- under UK POCA 2002 s 330 aREFERcarries a mandatory SAR obligation that aDENYdoes not. A score / tier projection would lose this distinction and break year-five auditability.screen_timestamp_ms(Substrate Rule 1 fromx402-foundation/x402PR Add New Horizons Schemas #2436).screen_provider_did.canon_versionpinned tojcs-rfc8785-v1(canonicalisation discipline pin).additionalProperties: false) so retained bytes are unambiguous.Files added
src/schemas/json/algovoi-compliance-receipt-v1.json-- the schema itself (draft-07).src/test/algovoi-compliance-receipt-v1/-- 3 positive tests:receipt-allow-uk-eu.json(ALLOW under UK + EU joint jurisdiction)receipt-refer-uk-sar-obligation.json(REFER under UK, mandatory SAR)receipt-deny-sanctions.json(DENY across UK + EU + US sanctions)src/negative_test/algovoi-compliance-receipt-v1/-- 7 negative tests:missing-payer-ref.json,invalid-screen-result.json,float-timestamp.json,empty-jurisdiction-flags.json,invalid-did-format.json,unknown-canon-version.json,extra-field-score.jsonsrc/api/json/catalog.json-- new catalog entry.Validation
node cli.js check --SchemaName algovoi-compliance-receipt-v1passes all pre-checks and Ajv validation.Context
The substrate underneath this receipt is formalised in
x402-foundation/x402PR #2436 (three-voice coalition co-signed) and pinned tourn:x402:canonicalisation:jcs-rfc8785-v1. Reference implementations in Python (algovoi-substrate) and TypeScript (@algovoi/substrate) produce schema-valid receipts viabuild_compliance_receipt(...)/buildComplianceReceipt(...).The canonical home of the schema with examples and per-anchor-set conformance vectors is at https://github.com/chopmob-cloud/algovoi-jcs-conformance-vectors.
Test plan
node cli.js check --SchemaName algovoi-compliance-receipt-v1passeshttps://www.schemastore.org/...), specific (non-generic)fileMatchpatterns