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.

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.

Validate locally

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 · Delivery status

The repository was previously named jep-v06. Repository identity is now stable; protocol drafts and software packages have separate versions.