JEP Core

Create portable signed event records and verify their structure and signatures.

Judgment Event Protocol defines signed statements of Judgment (J), Delegation (D), Termination (T) and Verification (V). Start with the packaged sample below.

Website · Getting started

Verify your first event

Use Python 3.10 or later in a fresh environment. These commands work without a repository checkout, account, hosted API or another SDK:

python -m pip install jep-core-conformance==0.7.7
jep-byoi export jep-example
jep-validate validate jep-example/vectors/J-basic.json --keys jep-example/keys.json

Look for status: "valid" and checks.cryptographic: "pass". The keys are public synthetic fixtures: this verifies the sample's structure and signature, not trust in a real actor. Use a new export directory; an existing directory is not overwritten.

Continue from here

I want to…	Entry
Record my own events locally	Agent SDK example: create, export and verify a signed event
Use an HTTP service	HTTP Quickstart: start a local API, then create and verify through a client
Build an independent implementation	One-page overview → Implementer guide → BYOI tests
Submit reproducible results	Report guide

For setup questions, bugs, documentation fixes and implementation reports, use the contribution routes.

Current contract

Core 0.7 · wire major jep: "1" · published 2026-09-26.

JEP is an individual Internet-Draft, not an IETF-endorsed standard.

• Event Identity (who,id) identifies an event; Event Hash identifies an exact signed artifact.
• Acceptance is idempotent per Event Identity within an acceptance domain.
• Validation reports independent checks and valid, invalid or indeterminate.
• Freshness mechanisms belong to profiles; Core does not require a nonce.
• Chain reconstruction, delegation enforcement and termination cascade belong to companion/application layers.

Core checks event structure and signatures. Apply your own trust and authorization rules before acting on a record; see the validation checks.

The published -07 snapshot is immutable. Its checksum and the current Profiles -01 and Conformance -02 publications are listed in the source map.

Develop and test from source

For repository development, clone this repository first:

git clone https://github.com/hjs-spec/jep-core.git
cd jep-core
python -m pip install -e '.[test]'
make validate conformance repository-check
python -m pytest

Validator usage explains keys, validation results and acceptance storage.

More documentation

Use the documentation index for profile authoring, validator configuration and optional integrations. For an existing 0.6 integration, use the migration guide. Current ecosystem delivery tracks separately released components.

Licensing and security

Original implementation code and implementation aids use BSD-3-Clause. Internet-Draft text, extracted Code Components and third-party material retain their applicable terms; see licensing scope. Report security-sensitive findings through SECURITY.md.