chokr-spec 0.0.1__tar.gz

chokr_spec-0.0.1/.gitignore

@@ -0,0 +1,23 @@
+# environments and caches
+.venv/
+__pycache__/
+*.py[cod]
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.import_linter_cache/
+
+# local tool settings
+.claude/
+.vs/
+
+# build and test output
+dist/
+build/
+*.egg-info/
+.coverage
+.coverage.*
+coverage.xml
+htmlcov/
+conformance-report.json
+requirements.audit.txt

chokr_spec-0.0.1/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

chokr_spec-0.0.1/NOTICE

@@ -0,0 +1,4 @@
+chokr-spec
+Copyright 2026 chokr-ai
+
+This product includes software developed by chokr-ai.

chokr_spec-0.0.1/PKG-INFO

@@ -0,0 +1,118 @@
+Metadata-Version: 2.5
+Name: chokr-spec
+Version: 0.0.1
+Summary: CHOKR protocol for AI agent governance: JSON Schemas, registries and conformance vectors, with a reference checker.
+Project-URL: Homepage, https://github.com/chokr-ai/chokr-spec
+Project-URL: Repository, https://github.com/chokr-ai/chokr-spec
+Project-URL: Issues, https://github.com/chokr-ai/chokr-spec/issues
+Author: Nitin Saxena
+Maintainer: chokr-ai
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: agent-governance,agent-security,agentic-ai,ai-agents,ai-governance,audit-ledger,audit-trail,canonical-json,chokr,conformance-tests,hash-chain,human-in-the-loop,json-schema,llm-guardrails,protocol,signed-verdict,specification,tamper-evident
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development :: Libraries
+Classifier: Typing :: Typed
+Requires-Python: >=3.14
+Requires-Dist: cryptography<51,>=43
+Requires-Dist: jsonschema<5,>=4.22
+Requires-Dist: rfc8785<0.2,>=0.1.4
+Description-Content-Type: text/markdown
+
+# chokr-spec: the CHOKR protocol for AI agent governance (JSON Schemas, registries, conformance vectors)
+
+[![PyPI](https://img.shields.io/pypi/v/chokr-spec)](https://pypi.org/project/chokr-spec/)
+[![Python](https://img.shields.io/pypi/pyversions/chokr-spec)](https://pypi.org/project/chokr-spec/)
+[![CI](https://github.com/chokr-ai/chokr-spec/actions/workflows/ci.yml/badge.svg)](https://github.com/chokr-ai/chokr-spec/actions/workflows/ci.yml)
+[![License](https://img.shields.io/pypi/l/chokr-spec)](https://github.com/chokr-ai/chokr-spec/blob/main/LICENSE)
+
+The CHOKR protocol as data: JSON Schemas for the documents that govern AI agents (envelope, signed verdict, tamper-evident
+audit ledger, approval, pack, plugin manifest and config), registries of standard names, and conformance vectors. The
+package also holds a reference checker that runs the vectors, so any implementation, in any language, can compare its
+results with the same inputs.
+
+The policy language has its own repository, `chokr-policy-language`. Its outcomes, standard reason codes and authoring
+error codes are defined there and are not repeated here.
+
+## Install
+
+```
+pip install chokr-spec
+```
+
+Python 3.14 or newer. Import name: `chokr_spec`.
+
+## Check the vectors
+
+```console
+$ chokr-spec check
+$ chokr-spec check --level core --report report.json
+```
+
+The command exits with `0` only when every vector passes. `--vectors DIR` runs a different folder of vectors, and
+`--json` prints the report.
+
+## Use from Python
+
+```python
+from chokr_spec import data_dir
+from chokr_spec.runner import run
+
+report = run("core")
+print(report.passed, report.failed, report.ok)
+print(data_dir() / "schemas")
+```
+
+`data_dir()` is the folder that holds `schemas/`, `registry/` and `vectors/`. Another implementation can load the same
+files and reproduce every vector's `expected` value.
+
+## What is inside
+
+```text
+schemas/    JSON Schemas of the documents: envelope, signal, verdict, ledger record, approval, budget event,
+            pack, plugin manifest, config and action mappings
+registry/   names CHOKR defines: kinds, signal codes, reason codes, evidence types, obligation types, error codes
+vectors/    core/ and connect/ conformance vectors, one folder per area
+src/        the reference checker and the `chokr-spec` command
+tools/      gen_vectors.py rewrites the vectors that need only a hash function; check_spec.py checks all the data
+```
+
+A vector is a JSON file with an `id`, a `level`, an `input` and an `expected` result. The `id` is `<area>/<file name>` and
+the `level` is the folder it sits in. The areas are `envelope` (canonical form and digest), `ledger` (the hash chain),
+`tamper` (a changed chain), `schema` (a document against a schema), `version` (version compatibility) and `verdict`
+(signature verification). The levels are `core` and `connect`; a `trust` level is reserved and has no vectors yet.
+
+## What is normative
+
+The JSON Schemas, the registries and the vectors define the protocol. The Python checker is a reference implementation
+of the vectors, not a second source of truth. When they disagree, the vectors win and the checker is wrong.
+
+- Each schema describes one minor version exactly. Inside that version an unknown field is invalid, and `ext` is the
+  place for extensions. A reader that supports `1.m` accepts documents from `1.0` to `1.m`, each against its own schema.
+- Patterns in the schemas must match the whole text, and a trailing newline never matches.
+- Signatures are strict unpadded base64url, and the checks run in a fixed order: unsigned, malformed signature, kid not
+  allowed, unknown kid, algorithm, then the signature itself. A kid that is both unknown and not allowed is reported as
+  not allowed.
+- A ledger chain verifies from `seq` 0 and reports the first problem as `<class> at seq <n>`. A chain cut short at the
+  end still verifies by itself, so a reader that must detect a cut keeps the head hash it last saw and passes it to
+  `verify_chain(..., expected_head=...)`.
+
+## Versioning
+
+- The package version is the protocol version. Before 1.0 every change is a patch.
+- A consumer accepts any minor version of its major version and ignores unknown `ext` names.
+- Optional fields are omitted, never `null`, so digests stay stable.
+- A published code never changes meaning.
+
+## Contributing and security
+
+See [CONTRIBUTING.md](https://github.com/chokr-ai/chokr-spec/blob/main/CONTRIBUTING.md). Report vulnerabilities privately as described in [SECURITY.md](https://github.com/chokr-ai/chokr-spec/blob/main/SECURITY.md), not in public issues.
+
+## License
+
+Apache License 2.0. Copyright 2026 chokr-ai. See [LICENSE](https://github.com/chokr-ai/chokr-spec/blob/main/LICENSE) and [NOTICE](https://github.com/chokr-ai/chokr-spec/blob/main/NOTICE).

chokr_spec-0.0.1/README.md

@@ -0,0 +1,92 @@
+# chokr-spec: the CHOKR protocol for AI agent governance (JSON Schemas, registries, conformance vectors)
+
+[![PyPI](https://img.shields.io/pypi/v/chokr-spec)](https://pypi.org/project/chokr-spec/)
+[![Python](https://img.shields.io/pypi/pyversions/chokr-spec)](https://pypi.org/project/chokr-spec/)
+[![CI](https://github.com/chokr-ai/chokr-spec/actions/workflows/ci.yml/badge.svg)](https://github.com/chokr-ai/chokr-spec/actions/workflows/ci.yml)
+[![License](https://img.shields.io/pypi/l/chokr-spec)](https://github.com/chokr-ai/chokr-spec/blob/main/LICENSE)
+
+The CHOKR protocol as data: JSON Schemas for the documents that govern AI agents (envelope, signed verdict, tamper-evident
+audit ledger, approval, pack, plugin manifest and config), registries of standard names, and conformance vectors. The
+package also holds a reference checker that runs the vectors, so any implementation, in any language, can compare its
+results with the same inputs.
+
+The policy language has its own repository, `chokr-policy-language`. Its outcomes, standard reason codes and authoring
+error codes are defined there and are not repeated here.
+
+## Install
+
+```
+pip install chokr-spec
+```
+
+Python 3.14 or newer. Import name: `chokr_spec`.
+
+## Check the vectors
+
+```console
+$ chokr-spec check
+$ chokr-spec check --level core --report report.json
+```
+
+The command exits with `0` only when every vector passes. `--vectors DIR` runs a different folder of vectors, and
+`--json` prints the report.
+
+## Use from Python
+
+```python
+from chokr_spec import data_dir
+from chokr_spec.runner import run
+
+report = run("core")
+print(report.passed, report.failed, report.ok)
+print(data_dir() / "schemas")
+```
+
+`data_dir()` is the folder that holds `schemas/`, `registry/` and `vectors/`. Another implementation can load the same
+files and reproduce every vector's `expected` value.
+
+## What is inside
+
+```text
+schemas/    JSON Schemas of the documents: envelope, signal, verdict, ledger record, approval, budget event,
+            pack, plugin manifest, config and action mappings
+registry/   names CHOKR defines: kinds, signal codes, reason codes, evidence types, obligation types, error codes
+vectors/    core/ and connect/ conformance vectors, one folder per area
+src/        the reference checker and the `chokr-spec` command
+tools/      gen_vectors.py rewrites the vectors that need only a hash function; check_spec.py checks all the data
+```
+
+A vector is a JSON file with an `id`, a `level`, an `input` and an `expected` result. The `id` is `<area>/<file name>` and
+the `level` is the folder it sits in. The areas are `envelope` (canonical form and digest), `ledger` (the hash chain),
+`tamper` (a changed chain), `schema` (a document against a schema), `version` (version compatibility) and `verdict`
+(signature verification). The levels are `core` and `connect`; a `trust` level is reserved and has no vectors yet.
+
+## What is normative
+
+The JSON Schemas, the registries and the vectors define the protocol. The Python checker is a reference implementation
+of the vectors, not a second source of truth. When they disagree, the vectors win and the checker is wrong.
+
+- Each schema describes one minor version exactly. Inside that version an unknown field is invalid, and `ext` is the
+  place for extensions. A reader that supports `1.m` accepts documents from `1.0` to `1.m`, each against its own schema.
+- Patterns in the schemas must match the whole text, and a trailing newline never matches.
+- Signatures are strict unpadded base64url, and the checks run in a fixed order: unsigned, malformed signature, kid not
+  allowed, unknown kid, algorithm, then the signature itself. A kid that is both unknown and not allowed is reported as
+  not allowed.
+- A ledger chain verifies from `seq` 0 and reports the first problem as `<class> at seq <n>`. A chain cut short at the
+  end still verifies by itself, so a reader that must detect a cut keeps the head hash it last saw and passes it to
+  `verify_chain(..., expected_head=...)`.
+
+## Versioning
+
+- The package version is the protocol version. Before 1.0 every change is a patch.
+- A consumer accepts any minor version of its major version and ignores unknown `ext` names.
+- Optional fields are omitted, never `null`, so digests stay stable.
+- A published code never changes meaning.
+
+## Contributing and security
+
+See [CONTRIBUTING.md](https://github.com/chokr-ai/chokr-spec/blob/main/CONTRIBUTING.md). Report vulnerabilities privately as described in [SECURITY.md](https://github.com/chokr-ai/chokr-spec/blob/main/SECURITY.md), not in public issues.
+
+## License
+
+Apache License 2.0. Copyright 2026 chokr-ai. See [LICENSE](https://github.com/chokr-ai/chokr-spec/blob/main/LICENSE) and [NOTICE](https://github.com/chokr-ai/chokr-spec/blob/main/NOTICE).

chokr_spec-0.0.1/pyproject.toml

@@ -0,0 +1,114 @@
+[build-system]
+requires = ["hatchling>=1.27"]
+build-backend = "hatchling.build"
+
+[project]
+name = "chokr-spec"
+dynamic = ["version"]
+readme = "README.md"
+description = "CHOKR protocol for AI agent governance: JSON Schemas, registries and conformance vectors, with a reference checker."
+requires-python = ">=3.14"
+license = "Apache-2.0"
+license-files = ["LICENSE", "NOTICE"]
+authors = [{ name = "Nitin Saxena" }]
+maintainers = [{ name = "chokr-ai" }]
+keywords = [
+  "chokr", "ai-governance", "agent-governance", "ai-agents", "agentic-ai", "agent-security", "llm-guardrails",
+  "protocol", "specification", "json-schema", "conformance-tests", "audit-trail", "audit-ledger", "tamper-evident",
+  "hash-chain", "canonical-json", "signed-verdict", "human-in-the-loop",
+]
+classifiers = [
+  "Development Status :: 3 - Alpha",
+  "Intended Audience :: Developers",
+  "Operating System :: OS Independent",
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3.14",
+  "Topic :: Software Development :: Libraries",
+  "Typing :: Typed",
+]
+dependencies = [
+  "jsonschema>=4.22,<5",
+  "rfc8785>=0.1.4,<0.2",
+  "cryptography>=43,<51",
+]
+
+[project.urls]
+Homepage = "https://github.com/chokr-ai/chokr-spec"
+Repository = "https://github.com/chokr-ai/chokr-spec"
+Issues = "https://github.com/chokr-ai/chokr-spec/issues"
+
+[project.scripts]
+chokr-spec = "chokr_spec.cli:main"
+
+[dependency-groups]
+dev = [
+  "pytest>=8",
+  "pytest-cov>=5",
+  "ruff>=0.6",
+  "mypy>=1.11",
+  "types-jsonschema>=4.22",
+  "ruamel.yaml>=0.18,<1",
+  "import-linter>=2.0",
+  "pip-audit>=2.7",
+]
+
+[tool.hatch.version]
+path = "src/chokr_spec/__init__.py"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/chokr_spec"]
+
+[tool.hatch.build.targets.wheel.force-include]
+"schemas" = "chokr_spec/data/schemas"
+"registry" = "chokr_spec/data/registry"
+"vectors" = "chokr_spec/data/vectors"
+
+[tool.hatch.build.targets.sdist]
+include = ["/src", "/tests", "/schemas", "/registry", "/vectors", "/tools", "/README.md", "/pyproject.toml"]
+
+[tool.ruff]
+line-length = 120
+target-version = "py314"
+src = ["src", "tests"]
+
+[tool.ruff.lint]
+select = ["E", "F", "I", "UP", "B", "SIM", "PT", "RUF", "S", "C4", "PIE", "PERF", "PTH", "T20", "W"]
+ignore = ["RUF012", "B905"]
+
+[tool.ruff.lint.per-file-ignores]
+"tests/**" = ["PT006", "PT011", "PT012", "PT018", "E501", "S101", "S105", "S106"]
+"tools/**" = ["T201"]
+"src/chokr_spec/cli.py" = ["T201"]
+
+[tool.mypy]
+python_version = "3.14"
+strict = true
+warn_unreachable = true
+files = ["src/chokr_spec"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+pythonpath = ["."]
+addopts = "-q -ra --strict-markers --strict-config"
+
+[tool.coverage.run]
+branch = true
+source = ["chokr_spec"]
+omit = ["*/__main__.py"]
+
+[tool.coverage.report]
+fail_under = 90
+show_missing = true
+skip_covered = true
+exclude_also = ["if TYPE_CHECKING:", "^\\s*\\.\\.\\.$", "if __name__ == .__main__.:"]
+
+[tool.importlinter]
+root_package = "chokr_spec"
+include_external_packages = true
+
+[[tool.importlinter.contracts]]
+name = "The protocol data imports no product and no network library"
+type = "forbidden"
+source_modules = ["chokr_spec"]
+forbidden_modules = ["chokr", "cplang", "pydantic", "httpx", "requests", "aiohttp", "urllib3", "fastapi"]
+allow_indirect_imports = true

chokr_spec-0.0.1/registry/error_codes.yaml

@@ -0,0 +1,27 @@
+# Names that CHOKR defines. The language's own names (outcomes, standard reason codes and authoring error codes)
+# live in the language registry. This file is edited by hand and kept sorted by tools/check_spec.py.
+schema_version: '1.0'
+entries:
+- code: CONNECT_API_KEY_MISSING
+- code: CONNECT_URL_MISSING
+- code: ENFORCEMENT_FAILURE
+- code: EXPORTER_UNAVAILABLE
+- code: GRANT_MISMATCH
+- code: KID_NOT_ALLOWED
+- code: LEDGER_UNAVAILABLE
+- code: PACK_DEPENDENCY_CONFLICT
+- code: PACK_DEPENDENCY_CYCLE
+- code: PACK_INVALID
+- code: PACK_IN_USE
+- code: PACK_NAMESPACE_VIOLATION
+- code: PACK_NOT_FOUND
+- code: PACK_REQUIRES_UNSATISFIED
+- code: PACK_SIGNATURE_INVALID
+- code: PACK_SIGNER_UNTRUSTED
+- code: PACK_TEST_FAILED
+- code: PACK_UNSIGNED
+- code: PLUGIN_NAMESPACE_VIOLATION
+- code: SIGNATURE_INVALID
+- code: UNKNOWN_KID
+- code: UNSUPPORTED_ALGORITHM
+- code: VERDICT_UNSIGNED

chokr_spec-0.0.1/registry/evidence_types.yaml

@@ -0,0 +1,17 @@
+# Names that CHOKR defines. The language's own names (outcomes, standard reason codes and authoring error codes)
+# live in the language registry. This file is edited by hand and kept sorted by tools/check_spec.py.
+schema_version: '1.0'
+entries:
+- name: BEHAVIORAL_TEST
+- name: BUILD_PROVENANCE
+- name: COMPLIANCE
+- name: HUMAN_APPROVAL
+- name: IDENTITY
+- name: MANIFEST_PIN
+- name: MODEL_PROFILE
+- name: MODEL_RUNTIME
+- name: OWNERSHIP
+- name: RUNTIME
+- name: SANDBOX_ATTESTATION
+- name: SECURITY_ASSESSMENT
+- name: SOFTWARE_ARTIFACT

chokr_spec-0.0.1/registry/kinds.yaml

@@ -0,0 +1,24 @@
+# Names that CHOKR defines. The language's own names (outcomes, standard reason codes and authoring error codes)
+# live in the language registry. This file is edited by hand and kept sorted by tools/check_spec.py.
+schema_version: '1.0'
+entries:
+- name: agent_message
+- name: context_compaction
+- name: db_query
+- name: file_op
+- name: http_call
+- name: mcp_call
+- name: mcp_result
+- name: memory_write
+- name: model_call
+- name: model_result
+- name: retrieval
+- name: session_end
+- name: session_start
+- name: shell_exec
+- name: skill_load
+- name: skill_register
+- name: subagent_spawn
+- name: subagent_stop
+- name: tool_call
+- name: tool_result

chokr_spec-0.0.1/registry/obligation_types.yaml

@@ -0,0 +1,12 @@
+# Names that CHOKR defines. The language's own names (outcomes, standard reason codes and authoring error codes)
+# live in the language registry. This file is edited by hand and kept sorted by tools/check_spec.py.
+schema_version: '1.0'
+entries:
+- name: human_approval
+  params: approval
+- name: provide_evidence
+  params: evidence type
+- name: refresh_evidence
+  params: evidence type
+- name: security_alert
+  params: signal, severity