JEP CLI — JEP Core 0.7
Command-line client for creating and verifying current JEP Core 0.7 events through the JEP API.
Default endpoints:
POST /v0.7/events/create
POST /v0.7/events/verify
GET /health
Historical pre-0.7 handling is explicit through --legacy; the CLI never
retries a failed 0.7 event with a legacy decoder.
Status
Experimental reference client. It does not define Core semantics or determine truth, authorization validity, legal effect, causality, or policy outcome.
Installation
pip install jep-cli
Configuration
export JEP_API_URL=http://127.0.0.1:8000
export JEP_API_KEY=
Create
Judgment:
jep create \
--verb J \
--who did:example:agent-789 \
--what '{"claim":"approve","subject":"demo"}'
Delegation:
jep create \
--verb D \
--who did:example:principal \
--what '{"delegatee":"did:example:agent","scope":{"actions":["read"]}}'
Termination and Verification require --ref. Pass a typed reference as
JSON when the target is another JEP event.
Verify
jep verify event.json --mode archival
0.7 validation returns status plus independent checks, not a cumulative
Validation Level.
Explicit legacy verification
jep verify old-event.json \
--legacy \
--legacy-format json-sorted-v1
Legacy selection must come from known artifact context. Do not use a failed 0.7 validation as evidence that an event should be treated as 0.6.
JEP Core 0.7 model
- Event Identity is
(who,id). - Event Hash identifies an exact signed artifact.
- Core does not require a top-level nonce.
- D requires
delegatee + scope. - T requires target
ref + termination_scope. - V requires target
ref + verification_scope + result. - chain and policy semantics remain outside Core.
Related repositories
- JEP Core: https://github.com/hjs-spec/jep-core
- JEP API: https://github.com/hjs-spec/jep-api
- Python SDK: https://github.com/hjs-spec/sdk-py
- JavaScript SDK: https://github.com/hjs-spec/sdk-js
- Go SDK: https://github.com/hjs-spec/sdk-go
Public draft
License
MIT
Metadata
Release files for jep-cli 0.7.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| jep_cli-0.7.1.tar.gz | 8.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jep_cli-0.7.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 16.1 kB
Release files / jep_cli-0.7.1.tar.gz
| Download URL | jep_cli-0.7.1.tar.gz |
|---|---|
| Size | 8.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e5885e6ec0be1268ae22e0e15c6ab158acd63526579f0195ebbcf783660439aa
|
|
BLAKE2b-256 checksum How to use checksums |
5d0dec782958dd0c5ed1807d12b41cc710c201fe4645e73f2a4ea656a418b71d
|
| 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 26, 2026.
Transparency logRelease files / jep_cli-0.7.1-py3-none-any.whl
| Download URL | jep_cli-0.7.1-py3-none-any.whl |
|---|---|
| Size | 7.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
72f00005bc9e015193e8226f13d2a909cecf2802d90ad5479e589e642fc2b1d3
|
|
BLAKE2b-256 checksum How to use checksums |
662798a1b42bdd365062ca3c96ab554892fa367d231def26aff766218911454c
|
| 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 26, 2026.
Transparency log