JEP API 0.7 (JEP-Core-0.6)

FastAPI event creation and verification for JEP-Core-0.6, with PostgreSQL multi-host state, external Ed25519 signing providers and explicit historical-format verification.

This repository upgrades the earlier JEP-04 API demo into a JEP v0.6-style API seed aligned with:

• draft-wang-jep-judgment-event-protocol-06
• draft-wang-jep-profiles-00
• draft-wang-jep-conformance-00

Status

This is an implementation seed, not a production security service.

It demonstrates:

• J/D/T/V event creation
• JEP wire version "1"
• JEP-Core-0.6 profile labels
• JCS-compatible seed canonicalization
• algorithm-tagged event hashes
• detached JWS Compact Serialization shape
• Ed25519 signing and verification
• ext / ext_crit extension framework
• TTL and digest-only privacy extensions
• JEP-style validation result object
• separated event storage and nonce consumption

Endpoints

Endpoint	Purpose
GET /	API metadata and demo public key
GET /health	Health check
POST /events/create	Create and sign a JEP-style event
POST /events/verify	Verify a JEP-style event

Run locally

pip install -r requirements.txt
uvicorn main:app --reload

Open:

http://127.0.0.1:8000/docs

Example create request

{
  "verb": "J",
  "who": "did:example:agent-789",
  "what": {
    "claim": "approve",
    "subject": "demo"
  },
  "aud": "https://api.example.org",
  "ttl_minutes": 30,
  "digest_only_who": false
}

Validation result shape

{
  "valid": true,
  "level": 1,
  "mode": "archival",
  "profile": "jep-core-0.6",
  "scopes": ["syntax", "cryptographic"],
  "event_hash": "sha256:...",
  "warnings": [],
  "errors": []
}

Boundary

This API does not determine:

• external truth;
• legal liability;
• regulatory compliance;
• authorization validity;
• complete-log availability;
• model correctness.

A valid signature proves protocol-level integrity under the API seed's demo trust context.

Public drafts

• JEP-Core: https://datatracker.ietf.org/doc/draft-wang-jep-judgment-event-protocol/
• JEP-Profiles: https://datatracker.ietf.org/doc/draft-wang-jep-profiles/
• JEP-Conformance: https://datatracker.ietf.org/doc/draft-wang-jep-conformance/

Related resources

• JEP v0.6 Repository: https://github.com/hjs-spec/jep-v06
• JEP v0.6 Spec Demo: https://huggingface.co/spaces/yuqiangJEP/jep-v06-spec-demo/tree/main
• JEP v0.6 Conformance Suite: https://huggingface.co/datasets/yuqiangJEP/jep-v06-conformance-suite

Runtime and verification notes

See HARDENING.md for supported behavior, regression checks, and compatibility boundaries.

Production configuration and migration

The current release is 0.7.2. See DEPLOYMENT.md for PostgreSQL, keyring/Vault configuration, authenticated signing, rotation, SQLite migration and the existing Hugging Face target. Container: ghcr.io/hjs-spec/jep-api:0.7.2. Publishing this image does not update an existing service automatically.

Additional endpoints: GET /.well-known/jwks.json, GET /live, and archival-only POST /events/verify-legacy. Production creation requires Bearer authentication; the SDKs/CLI accept their existing API-key options, and GitHub Action 0.6.2 accepts jep_api_token.