JEP v0.6 Draft Set
This repository contains the JEP-Core -06 working draft, optional profile bindings, and the companion conformance seed.
Public mirrors
- Hugging Face Space: https://huggingface.co/spaces/yuqiangJEP/jep-v06-spec-demo/tree/main
- Hugging Face Conformance Dataset: https://huggingface.co/datasets/yuqiangJEP/jep-v06-conformance-suite
- IETF JEP-Core Draft: https://datatracker.ietf.org/doc/draft-wang-jep-judgment-event-protocol/
- IETF JEP-Conformance Draft: https://datatracker.ietf.org/doc/draft-wang-jep-conformance/
- IETF JEP-Profiles Draft: https://datatracker.ietf.org/doc/draft-wang-jep-profiles/
Drafts
draft-wang-jep-judgment-event-protocol-06.md— the neutral J/D/T/V event core.draft-wang-jep-profiles-00.md— optional trust and interoperability profiles.draft-wang-jep-conformance-00.md— conformance classes, schemas, vectors, and validator behavior.
The Internet-Drafts are normative for this package. The schemas and validators are executable conformance aids; they do not make legal, policy, factual, or external-target determinations.
Conformance implementations
| Implementation | Declared boundary |
|---|---|
reference-validator/ |
Python Level 0/1 baseline, optional local Level 2 binding, and seed Level 3 chain checks |
typescript-validator/ |
TypeScript Level 0/1 baseline plus optional local binding and acceptance replay/freshness checks |
go-validator/ |
Explicit Level 0 syntax verifier seed only; it does not claim signature verification or event hashing |
The Python and TypeScript Level 1 paths use RFC 8785 JCS and detached compact JWS/Ed25519 processing for the repository baseline. A validator reports only the highest validation level it actually completed.
Run
python -m pip install -e '.[test]'
make test
make conformance
make go
For TypeScript:
cd typescript-validator
npm install
npm run check
The manifest-driven suite checks exact validity, failure code, completed level, and selected event hashes. It must not treat an unrelated early failure as success for a later-stage test.
Scope discipline
This alignment pass does not change JEP's four verbs or expand JEP-Core into a legal-liability, authorization, policy, or external-truth engine. Profile-specific bindings remain outside the core.
Guides
Additional implementation and review guidance is under docs/.
IMPLEMENTER-GUIDE.mdPROFILE-AUTHOR-GUIDE.mdSECURITY-REVIEW-NOTES.mdPRIVACY-REVIEW-NOTES.mdONE-PAGE-OVERVIEW.mdEND-TO-END-DEMO.mdCONFORMANCE-LEVELS.mdINTEROPERABILITY-REPORT-TEMPLATE.md
JEP-TSTO Binding/01
The Binding/01 integration note declares the joint Schema, signature and immutable-reference validation path, historical compatibility, and algorithm boundaries without changing JEP-Core 0.6.
Runtime and verification notes
See HARDENING.md for supported behavior, regression checks, and compatibility boundaries.
Cross-repository hardening review map and verification evidence.
Metadata
Release files for jep-v06-conformance-seed 0.7.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| jep_v06_conformance_seed-0.7.0.tar.gz | 16.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jep_v06_conformance_seed-0.7.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 30.3 kB
Release files / jep_v06_conformance_seed-0.7.0.tar.gz
| Download URL | jep_v06_conformance_seed-0.7.0.tar.gz |
|---|---|
| Size | 16.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
37a08fc089c19b977cf4293e7159a0e8bce7ca109bc54ef9e42f6573e23866b2
|
|
BLAKE2b-256 checksum How to use checksums |
3dedd653b2505939a3f4e537f3590a9863beca6d0a4b886e43ec28c992544b3c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 13, 2026.
Transparency logRelease files / jep_v06_conformance_seed-0.7.0-py3-none-any.whl
| Download URL | jep_v06_conformance_seed-0.7.0-py3-none-any.whl |
|---|---|
| Size | 13.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3062e95599cf542bd99b7e253213efb8bfa7c2f33d149a69259289ff05cdba05
|
|
BLAKE2b-256 checksum How to use checksums |
00fd0ad9507bd652afec03d3e227d1458d381cd69643be7c889bf6fb2ca5f4e2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 13, 2026.
Transparency logSecurity for jep-v06-conformance-seed 0.7.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for jep_v06_conformance_seed-0.7.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 13, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.