jep-core-conformance 0.7.4__tar.gz

jep_core_conformance-0.7.4/PKG-INFO

@@ -0,0 +1,65 @@
+Metadata-Version: 2.4
+Name: jep-core-conformance
+Version: 0.7.4
+Summary: JEP Core 0.7 conformance tools with explicit legacy 0.6 compatibility
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+Requires-Dist: PyNaCl<2,>=1.6.2
+Requires-Dist: cryptography>=42
+Requires-Dist: rfc8785==0.1.4
+Provides-Extra: test
+Requires-Dist: pytest>=8; extra == "test"
+Requires-Dist: jsonschema>=4.18; extra == "test"
+
+# 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
+
+| Task | Entry |
+|---|---|
+| Read the published protocol | [Frozen Internet-Draft -07](releases/draft-07/) |
+| Read the working source | [Editor's Copy](draft-wang-jep-judgment-event-protocol.md) |
+| Implement or migrate | [Implementer guide](docs/IMPLEMENTER-GUIDE.md) · [0.7 migration](docs/MIGRATION-0.7.md) |
+| Run a signed example | [Quickstart](https://github.com/hjs-spec/jep-quickstart) |
+| Choose a client or recorder | [Integration directory](https://github.com/hjs-spec/.github/blob/main/PROJECTS.md#integrate) |
+| Understand component boundaries | [Architecture](docs/architecture/README.md) |
+
+## 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](releases/draft-07/README.md). Later changes belong to the Editor's Copy and a subsequent draft. [Datatracker](https://datatracker.ietf.org/doc/draft-wang-jep-judgment-event-protocol/) is the external publication record.
+
+## Validate locally
+
+```sh
+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](reference-validator/README.md) explains keys and acceptance storage.
+
+## Current and historical assets
+
+| Current | Historical compatibility |
+|---|---|
+| Core `-07`; profiles/conformance `-01` | Core `-06`; profiles/conformance `-00` |
+| `test-manifest-0.7.json`, Python `jep_validate_07.py` | `test-manifest-0.6.json`, Python `jep_validate.py` |
+| Versioned 0.7 schemas and vectors | Go and TypeScript validators currently support **0.6 only** |
+
+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](docs/README.md) · [Versioning](docs/VERSIONING.md) · [Logging comparison](docs/comparisons/logging.md) · [Delivery status](https://github.com/hjs-spec/.github/blob/main/DELIVERY-2026-09-26.md)
+
+The repository was previously named `jep-v06`. Repository identity is now stable; protocol drafts and software packages have separate versions.

jep_core_conformance-0.7.4/README.md

@@ -0,0 +1,52 @@
+# 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
+
+| Task | Entry |
+|---|---|
+| Read the published protocol | [Frozen Internet-Draft -07](releases/draft-07/) |
+| Read the working source | [Editor's Copy](draft-wang-jep-judgment-event-protocol.md) |
+| Implement or migrate | [Implementer guide](docs/IMPLEMENTER-GUIDE.md) · [0.7 migration](docs/MIGRATION-0.7.md) |
+| Run a signed example | [Quickstart](https://github.com/hjs-spec/jep-quickstart) |
+| Choose a client or recorder | [Integration directory](https://github.com/hjs-spec/.github/blob/main/PROJECTS.md#integrate) |
+| Understand component boundaries | [Architecture](docs/architecture/README.md) |
+
+## 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](releases/draft-07/README.md). Later changes belong to the Editor's Copy and a subsequent draft. [Datatracker](https://datatracker.ietf.org/doc/draft-wang-jep-judgment-event-protocol/) is the external publication record.
+
+## Validate locally
+
+```sh
+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](reference-validator/README.md) explains keys and acceptance storage.
+
+## Current and historical assets
+
+| Current | Historical compatibility |
+|---|---|
+| Core `-07`; profiles/conformance `-01` | Core `-06`; profiles/conformance `-00` |
+| `test-manifest-0.7.json`, Python `jep_validate_07.py` | `test-manifest-0.6.json`, Python `jep_validate.py` |
+| Versioned 0.7 schemas and vectors | Go and TypeScript validators currently support **0.6 only** |
+
+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](docs/README.md) · [Versioning](docs/VERSIONING.md) · [Logging comparison](docs/comparisons/logging.md) · [Delivery status](https://github.com/hjs-spec/.github/blob/main/DELIVERY-2026-09-26.md)
+
+The repository was previously named `jep-v06`. Repository identity is now stable; protocol drafts and software packages have separate versions.

jep_core_conformance-0.7.4/jep_core_conformance.egg-info/PKG-INFO

@@ -0,0 +1,65 @@
+Metadata-Version: 2.4
+Name: jep-core-conformance
+Version: 0.7.4
+Summary: JEP Core 0.7 conformance tools with explicit legacy 0.6 compatibility
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+Requires-Dist: PyNaCl<2,>=1.6.2
+Requires-Dist: cryptography>=42
+Requires-Dist: rfc8785==0.1.4
+Provides-Extra: test
+Requires-Dist: pytest>=8; extra == "test"
+Requires-Dist: jsonschema>=4.18; extra == "test"
+
+# 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
+
+| Task | Entry |
+|---|---|
+| Read the published protocol | [Frozen Internet-Draft -07](releases/draft-07/) |
+| Read the working source | [Editor's Copy](draft-wang-jep-judgment-event-protocol.md) |
+| Implement or migrate | [Implementer guide](docs/IMPLEMENTER-GUIDE.md) · [0.7 migration](docs/MIGRATION-0.7.md) |
+| Run a signed example | [Quickstart](https://github.com/hjs-spec/jep-quickstart) |
+| Choose a client or recorder | [Integration directory](https://github.com/hjs-spec/.github/blob/main/PROJECTS.md#integrate) |
+| Understand component boundaries | [Architecture](docs/architecture/README.md) |
+
+## 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](releases/draft-07/README.md). Later changes belong to the Editor's Copy and a subsequent draft. [Datatracker](https://datatracker.ietf.org/doc/draft-wang-jep-judgment-event-protocol/) is the external publication record.
+
+## Validate locally
+
+```sh
+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](reference-validator/README.md) explains keys and acceptance storage.
+
+## Current and historical assets
+
+| Current | Historical compatibility |
+|---|---|
+| Core `-07`; profiles/conformance `-01` | Core `-06`; profiles/conformance `-00` |
+| `test-manifest-0.7.json`, Python `jep_validate_07.py` | `test-manifest-0.6.json`, Python `jep_validate.py` |
+| Versioned 0.7 schemas and vectors | Go and TypeScript validators currently support **0.6 only** |
+
+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](docs/README.md) · [Versioning](docs/VERSIONING.md) · [Logging comparison](docs/comparisons/logging.md) · [Delivery status](https://github.com/hjs-spec/.github/blob/main/DELIVERY-2026-09-26.md)
+
+The repository was previously named `jep-v06`. Repository identity is now stable; protocol drafts and software packages have separate versions.

jep_core_conformance-0.7.4/jep_core_conformance.egg-info/SOURCES.txt

@@ -0,0 +1,16 @@
+README.md
+pyproject.toml
+jep_core_conformance.egg-info/PKG-INFO
+jep_core_conformance.egg-info/SOURCES.txt
+jep_core_conformance.egg-info/dependency_links.txt
+jep_core_conformance.egg-info/entry_points.txt
+jep_core_conformance.egg-info/requires.txt
+jep_core_conformance.egg-info/top_level.txt
+reference-validator/__init__.py
+reference-validator/jep_validate.py
+reference-validator/jep_validate_07.py
+tests/test_core07_boundaries.py
+tests/test_reference_validator.py
+tests/test_reference_validator_07.py
+tests/test_replay_concurrency.py
+tests/test_replay_context.py

jep_core_conformance-0.7.4/jep_core_conformance.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

jep_core_conformance-0.7.4/jep_core_conformance.egg-info/entry_points.txt

@@ -0,0 +1,4 @@
+[console_scripts]
+jep-validate = jep_conformance.jep_validate_07:main
+jep-validate-06 = jep_conformance.jep_validate:main
+jep-validate-07 = jep_conformance.jep_validate_07:main

jep_core_conformance-0.7.4/jep_core_conformance.egg-info/requires.txt

@@ -0,0 +1,7 @@
+PyNaCl<2,>=1.6.2
+cryptography>=42
+rfc8785==0.1.4
+
+[test]
+pytest>=8
+jsonschema>=4.18

jep_core_conformance-0.7.4/jep_core_conformance.egg-info/top_level.txt

@@ -0,0 +1 @@
+jep_conformance

jep_core_conformance-0.7.4/pyproject.toml

@@ -0,0 +1,31 @@
+[build-system]
+requires = ["setuptools>=68"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "jep-core-conformance"
+version = "0.7.4"
+readme = "README.md"
+description = "JEP Core 0.7 conformance tools with explicit legacy 0.6 compatibility"
+requires-python = ">=3.10"
+dependencies = [
+    "PyNaCl>=1.6.2,<2",
+  "cryptography>=42",
+  "rfc8785==0.1.4"
+]
+
+[project.optional-dependencies]
+test = ["pytest>=8", "jsonschema>=4.18"]
+
+[tool.setuptools]
+packages = ["jep_conformance"]
+package-dir = {jep_conformance = "reference-validator"}
+
+[project.scripts]
+jep-validate = "jep_conformance.jep_validate_07:main"
+jep-validate-07 = "jep_conformance.jep_validate_07:main"
+jep-validate-06 = "jep_conformance.jep_validate:main"
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+addopts = "-q"

jep_core_conformance-0.7.4/reference-validator/__init__.py

@@ -0,0 +1 @@
+__version__ = "0.7.2"