JEP Core

The canonical source for Judgment Event Protocol: signed statements of Judgment (J), Delegation (D), Termination (T) and Verification (V).

Core defines event structure and observable checks. It does not decide truth, authority, legal effect, causality, policy or external consequences. JEP is an individual Internet-Draft, not an IETF-endorsed standard.

Install the validator

In a fresh Python environment:

python -m pip install jep-core-conformance==0.7.6
jep-validate --help
jep-validate validate event.json --keys keys.json

event.json must be the actual event and keys.json the verifier's key map; use the local create/export/verify example to generate synthetic sample files. Demo-supplied public keys establish signature consistency, not independently trusted actor identity. No hosted API or account is required.

Do not install historical jep-v06-conformance-seed alongside this package: they share the jep_conformance import namespace. The current package already includes the explicit jep-validate-06 compatibility command. Existing old environments and signed archives are not silently migrated.

Start here

Current contract

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

• 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.

The published -07 snapshot is immutable. Its exact RFCXML and SHA-256 are recorded in the freeze record. Later changes belong to the Editor's Copy and a subsequent draft. Datatracker is the external publication record.

Develop and test from source

Clone this repository before using the source-only commands below:

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

The default Python validator, schemas and manifest target Core 0.7. Validator usage explains keys and acceptance storage.

Current and historical assets

Schemas and tools are implementation aids; the applicable specification controls normative requirements. Use make conformance-legacy only for known 0.6 artifacts. Never select a legacy decoder because current validation failed, or rewrite a historical signed artifact.

Documentation index · Versioning · Logging comparison · Current delivery status

The repository was previously named jep-v06. Repository identity is now stable; protocol drafts and software packages have separate versions. Maintainer-operated production API hosting is deferred; self-hosting remains optional.

External implementation testing

Software 0.7.6 includes the BYOI runner. It exports a self-contained signed suite and runs a producer, verifier or acceptance adapter without companion repositories. Reports disclose actual coverage and do not claim certification. See the installation and adapter contract.

Licensing

Original implementation code and implementation aids use BSD-3-Clause. Internet-Draft text, extracted Code Components and third-party material retain their applicable terms. Read the licensing scope before reuse.