yuqiangJEP/JEP-EU-AI-Act-Mapping-Notes

JEP EU AI Act Mapping Notes

Exploratory / Not Legal Advice

This dataset contains exploratory EU AI Act mapping notes for JEP. It is not legal advice, not a compliance guarantee, and not part of JEP-Core.

Official EU AI Act materials, regulator guidance, and qualified legal counsel should always take precedence.

---

Purpose

This dataset explores how JEP-style judgment events may support auditability, traceability, transparency, documentation, and review workflows in selected EU AI Act-related scenarios.

It is intended for:

• research discussion;
• scenario analysis;
• compliance-mapping experiments;
• audit-trail design exploration;
• JEP profile and extension discussion.

It is not intended to certify or determine legal compliance.

---

Current Protocol Context

Current public version line:

JEP v0.6
JEP API v0.6
HJS v0.5
JAC v0.5

Current repositories:

Layer	Repository
JEP v0.6	https://github.com/hjs-spec/jep-v06
JEP API v0.6	https://github.com/hjs-spec/jep-api
HJS v0.5	https://github.com/hjs-spec/hjs-05
JAC v0.5	https://github.com/hjs-spec/jac-agent-02

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/
• HJS: https://datatracker.ietf.org/doc/draft-wang-hjs-accountability/
• JAC: https://datatracker.ietf.org/doc/draft-wang-jac/

---

Repository Role

This dataset is a supporting research and mapping resource.

It is not:

• the normative JEP specification;
• the JEP v0.6 conformance suite;
• a legal compliance product;
• a compliance certification;
• a regulatory filing;
• a legal opinion;
• a guarantee that any system complies with the EU AI Act.

The normative JEP materials are maintained in:

https://github.com/hjs-spec/jep-v06

The public conformance suite is maintained at:

https://huggingface.co/datasets/yuqiangJEP/jep-v06-conformance-suite

---

Core Principle

JEP-Core remains a neutral narrow-waist event layer.

JEP-Core = signed judgment events
EU mapping notes = optional external interpretation / deployment guidance

JEP can provide technical event records that may support auditability, traceability, transparency, documentation, and review workflows.

JEP does not itself determine legal compliance.

---

JEP v0.6 Extension Style

Examples in this dataset should use the JEP v0.6 extension structure:

{
  "ext": {
    "https://jep-eu-compliance.org/industry": "medical",
    "https://jep-eu-compliance.org/risk-class": "high",
    "https://jep-eu-compliance.org/art-ref": "Annex-III-1a"
  },
  "ext_crit": []
}

Older examples using:

{
  "extensions": {}
}

should be treated as historical and should be migrated to:

{
  "ext": {},
  "ext_crit": []
}

---

Dataset Structure

README.md
DISCLAIMER.md
LEGAL-STATUS.md
EU_AI_ACT_MAPPING.md
NOTICE.md
LICENSE
CHANGELOG.md
CONTRIBUTING.md

examples/
  automotive_j.json
  critical-infra_j.json
  fintech_j.json
  governance_j.json
  hr_j.json
  medical_j.json

extensions/
  critical-infra.md
  fintech.md
  governance.md
  hr.md
  medical.md

schemas/
  automotive.schema.json
  critical-infra.schema.json
  fintech.schema.json
  governance.schema.json
  hr.schema.json
  medical.schema.json

implementations/
  verify_jep_eu.py
  test_verify_jep_eu.py

---

Mapping Areas

This dataset includes exploratory notes for:

• medical and health-related contexts;
• fintech and credit-related contexts;
• automotive and transport contexts;
• human resources contexts;
• governance and public-service contexts;
• critical infrastructure contexts.

These are mapping notes only.

They do not determine whether a deployment is legally compliant.

---

What JEP May Support

JEP-style event records may support:

• traceability records;
• review logs;
• verification traces;
• delegation records;
• termination records;
• audit trail artifacts;
• evidence reference workflows;
• documentation support;
• incident review workflows.

---

What JEP Does Not Prove

A JEP event does not prove:

• the underlying claim is true;
• the system is legally compliant;
• human oversight was legally sufficient;
• documentation was complete;
• risk management was adequate;
• a legal obligation was satisfied;
• the system is safe;
• the model is correct;
• the log is complete;
• factual causality;
• legal liability.

A valid signature proves cryptographic integrity under a validation profile.

It does not prove the truth of the underlying claim.

---

Legal Status

See:

LEGAL-STATUS.md
DISCLAIMER.md

The EU AI Act has staged application dates and may be further interpreted by official guidance, implementing acts, delegated acts, harmonized standards, national authorities, notified bodies, courts, and other official sources.

This dataset may become outdated.

Always consult official sources and qualified legal counsel.

---

Related Resources

Resource	Link
JEP v0.6 Repository	https://github.com/hjs-spec/jep-v06
JEP API v0.6 Repository	https://github.com/hjs-spec/jep-api
HJS v0.5 Repository	https://github.com/hjs-spec/hjs-05
JAC v0.5 Repository	https://github.com/hjs-spec/jac-agent-02
JEP v0.6 Spec Demo	https://huggingface.co/spaces/yuqiangJEP/jep-v06-spec-demo
JEP API v0.6 Seed	https://huggingface.co/spaces/yuqiangJEP/jep-api
JEP v0.6 Conformance Suite	https://huggingface.co/datasets/yuqiangJEP/jep-v06-conformance-suite

---

License and Notice

Implementation examples, schemas, scripts, and mapping notes are provided under the repository license unless otherwise stated.

Internet-Draft text and excerpts, if present, are governed by the IETF Trust Legal Provisions and BCP 78 / BCP 79.

This dataset is not legal advice and does not provide a compliance guarantee.

See:

NOTICE.md
DISCLAIMER.md
LEGAL-STATUS.md