cait-certificate-schema 0.2.0__tar.gz

cait_certificate_schema-0.2.0/.gitignore

@@ -0,0 +1,44 @@
+# Python
+__pycache__/
+*.py[cod]
+*.pyo
+*.pyd
+.pytest_cache/
+.coverage
+htmlcov/
+build/
+dist/
+*.egg-info/
+
+# uv / environments
+.venv/
+venv/
+env/
+.python-version
+
+# Local environment and secrets
+.env
+.env.*
+*.pem
+*.key
+*.p12
+*.pfx
+
+# OS / editor
+.DS_Store
+Thumbs.db
+desktop.ini
+.idea/
+.vscode/
+*.swp
+*.swo
+
+# Local scratch
+tmp/
+scratch/
+.hypothesis/
+.mypy_cache/
+.ruff_cache/
+coverage.json
+fault-results.json
+site/

cait_certificate_schema-0.2.0/AGENTS.md

@@ -0,0 +1,14 @@
+# CAIT development instructions
+
+Preserve `schemas/cait`, legacy fixtures, public imports and `cait-validate` meanings.
+Read `docs/accounting.md`, `docs/reproduction.md` and `docs/interchange.md` before changing
+computed evidence. Accounting origin is not causal identification; hashes are not authentication.
+No computed result grants execution authority. Never turn missing negative evidence into zero.
+
+Keep changes in CAIT. Companion interfaces are pinned read-only JSON, with manifest hashes.
+Use the independent checker and original source bytes. Do not make it call the production reducer.
+Run the commands in `docs/release.md`, including separate >=90% statement and branch coverage
+on the complete new core, selected fault checks, legacy identity and built-wheel checks.
+Generated schema/example/reference edits must originate in their generator inputs.
+Do not bypass reviews, quality gates, environments or immutable artifact identity checks.
+Agent-facing operational guide: `docs/cli.md`. Analysis is local and read-only; output is a new derived file.

cait_certificate_schema-0.2.0/CHANGELOG.md

@@ -0,0 +1,14 @@
+# Changelog
+
+## 0.2.0
+
+- Add closed source-bound accounting records, exact joint-scenario replay and an independent checker.
+- Derive unique stock/service credit, receiver reuse, physical costs, lifecycle, corrections and origin partitions.
+- Check supplied conditional reproduction bounds with exact positive-vector witnesses.
+- Add `cait-analyze`, offline examples, pinned VEK/CCR interchange and explicit claim layers.
+- Preserve all legacy schemas/fixtures and `cait-validate` meanings.
+- Add reproducible Python/OS quality gates and artifact-identical Trusted Publishing.
+
+## 0.1.0
+
+Initial language-neutral schema set and lightweight local semantic validator.

cait_certificate_schema-0.2.0/CITATION.cff

@@ -0,0 +1,19 @@
+cff-version: 1.2.0
+message: "If you use this schema package, please cite both this repository and the related CAIT manuscript."
+title: "CAIT Certificate Schema"
+authors:
+  - family-names: "Takahashi"
+    given-names: "K."
+license: "Apache-2.0"
+repository-code: "https://github.com/kadubon/cait-certificate-schema"
+version: "0.2.0"
+date-released: "2026-09-13"
+references:
+  - type: "article"
+    title: "Certified Autocatalytic Intelligence Theory: Net-Growth Certificate Algebra for Verified Capability Capital"
+    authors:
+      - family-names: "Takahashi"
+        given-names: "K."
+    year: 2026
+    doi: "10.5281/zenodo.20061296"
+    url: "https://doi.org/10.5281/zenodo.20061296"

cait_certificate_schema-0.2.0/LICENSE

@@ -0,0 +1,176 @@
+                                 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

cait_certificate_schema-0.2.0/NOTICE

@@ -0,0 +1,9 @@
+CAIT Certificate Schema
+
+This repository provides JSON Schemas and local validation tooling derived from:
+
+Takahashi, K. (2026). Certified Autocatalytic Intelligence Theory:
+Net-Growth Certificate Algebra for Verified Capability Capital. Zenodo.
+https://doi.org/10.5281/zenodo.20061296
+
+The repository is distributed under the Apache License, Version 2.0.

cait_certificate_schema-0.2.0/PKG-INFO

@@ -0,0 +1,270 @@
+Metadata-Version: 2.5
+Name: cait-certificate-schema
+Version: 0.2.0
+Summary: JSON Schemas and local validation tooling for CAIT-style certified AI R&D capability-capital records.
+Author: K. Takahashi
+License: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: AI R&D validation,CAIT,JSON Schema,certificate records,verified capability capital
+Requires-Python: >=3.11
+Requires-Dist: jsonschema>=4.23.0
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0.0; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# CAIT Certificate Schema
+
+JSON Schemas for CAIT-style records: certificates, tokens, defeaters, transfer/evaluation boundaries, window balances, and arrival records.
+Deterministic local validation checks record shape plus lightweight fail-closed semantics.
+This is not an AGI detector, model evaluator, deployment authorization system, or safety guarantee.
+
+Version 0.2.0 additionally provides an opt-in **experimental finite accounting kernel**:
+`cait-analyze example interchange` runs source-bound replay, exact balances, conditional
+reproduction witnesses, an independent report checker and pinned released VEK/CCR adapters.
+Read [accounting semantics](docs/accounting.md), [CLI/API](docs/cli.md),
+[mathematical boundaries](docs/reproduction.md) and [release evidence](docs/release.md).
+The established schemas and `cait-validate` retain their original meanings.
+
+## Start Here
+
+If you are new to the project, read these files in order:
+
+1. `schemas/cait/schema_index.json`: maps each `record_type` to its schema file and semantic profile.
+2. `schemas/cait/semantic_rules.json`: lists portable fail-closed rule IDs and logic.
+3. `examples/valid/arrival_record.json`: shows a complete synthetic arrival record accepted by the local validator.
+
+Minimal adoption path:
+
+1. Use `schema_index.json` to choose the schema for each `record_type`.
+2. Run JSON Schema Draft 2020-12 structural validation.
+3. Implement the rule IDs in `semantic_rules.json` that apply to your record types.
+4. Keep local registry thresholds, evidence rules, and evaluation boundaries explicit in your own records.
+
+This repository is based on:
+
+Takahashi, K. (2026). *Certified Autocatalytic Intelligence Theory: Net-Growth Certificate Algebra for Verified Capability Capital*. Zenodo. https://doi.org/10.5281/zenodo.20061296
+
+## What This Project Is
+
+This project provides a small, auditable schema layer for machine-readable CAIT records:
+
+- registry records;
+- certificate records;
+- domain witnesses;
+- token records;
+- operator bundle records;
+- defeater records;
+- evidence budget ledgers;
+- assurance cases;
+- transfer, evaluation, and controller certificates;
+- window balance certificates;
+- arrival records.
+
+It also includes a deterministic local validator for basic structural and semantic checks.
+
+The language-neutral interface is the schema directory itself: `schemas/cait/*.schema.json`, `schemas/cait/schema_index.json`, and `schemas/cait/semantic_rules.json`.
+
+## What This Project Is Not
+
+This project is not:
+
+- an AGI detector;
+- a frontier model evaluator;
+- a deployment authorization system;
+- a safety guarantee;
+- an autonomous agent system;
+- a database, server, dashboard, or workflow engine;
+- a complete implementation of the CAIT paper.
+
+The schemas support machine-readable records. They do not certify AGI, ASI, deployment readiness, or real-world safety by themselves.
+
+## Limitations
+
+- The legacy schema/validator surface provides JSON Schema plus lightweight local semantic validation.
+- JSON Schema validates record shape, not scientific truth.
+- The validator performs lightweight local checks only.
+- The legacy validator does not replay source evidence. The new opt-in kernel replays finite declared histories and checks exact mathematical witnesses; neither surface establishes scientific truth, causal inference, AGI/ASI, safety guarantees or deployment approval.
+- It is not a frontier model evaluator, risk-governance process, autonomous agent system, or complete CAIT implementation.
+- Users must add registry-specific thresholds, evidence rules, evaluation boundaries, and policy semantics for their own setting.
+- The included thresholds and examples are synthetic and illustrative.
+- A passing validation result means a record is structurally and minimally semantically consistent with this schema package. It does not mean the underlying claim is true.
+
+## Why It Exists
+
+CAIT treats acceleration as certified net reproduction of verified capability capital, not as raw benchmark gain or candidate volume. The schemas in this repository make CAIT-style records easier for engineers, researchers, auditors, and AI agents to inspect, exchange, validate, and reuse.
+
+The fail-closed principle is central: if a positive claim depends on missing evidence, missing scope, unresolved severe defeaters, invalid lifecycle status, invalid transfer/evaluation boundary, or non-positive endogenous net growth, the local validator reports that the record cannot support a positive CAIT-style claim.
+
+## Quick Start
+
+```bash
+uv sync
+uv run cait-validate examples/valid/arrival_record.json
+uv run pytest
+```
+
+Validate a specific schema:
+
+```bash
+uv run cait-validate examples/valid/minimal_certificate_record.json --schema certificate_record
+```
+
+If `--schema` is omitted, the validator infers the schema from the top-level `record_type` field.
+
+## For Non-Python Users
+
+Python is only a reference validator. It is not the only specification. Other implementations can use the language-neutral files directly:
+
+- `schemas/cait/schema_index.json` to map `record_type` values to schema files;
+- `schemas/cait/*.schema.json` for Draft 2020-12 structural validation;
+- `schemas/cait/semantic_rules.json` for portable fail-closed semantic checks.
+
+Minimal implementation steps in another language:
+
+1. Read the top-level `record_type` key.
+2. Load the matching schema file from `schema_index.json`.
+3. Validate structure with any JSON Schema Draft 2020-12 implementation.
+4. Apply each relevant rule from `semantic_rules.json`.
+5. Report the same `rule_id` values where feasible.
+
+The semantic rules manifest contains stable rule IDs, severity, affected record types, primary JSON paths, portable logic, and human-readable descriptions.
+The `portable_logic` fields are JSONPath-like pseudocode for implementers. They are intended to make the rule semantics clear across languages, not to require a specific JSONPath library.
+
+## Core Concepts
+
+- `registry_record`: declares the coordinate dictionary, lifecycle table, evidence modes, external-input boundary, evaluator boundary, service graph, transfer boundary, and acceptance rule.
+- `certificate_record`: carries a lower/upper interval, evidence mode, lifecycle status, dependency support, defeaters, freshness, and provenance links.
+- `domain_witness`: records whether certificate composition predicates are satisfied, including compatible scope, accepted dependencies, valid budget, fresh evidence, no open blocking defeater, and disjoint support.
+- `token_record`: represents a content-addressed capability artifact with lifecycle status, evidence links, lineage, transfer/evaluation boundary links, and resource charges.
+- `defeater_record`: records a possible blocker or downgrader, including severity, affected scope, and resolution status.
+- `arrival_record`: reports whether a target profile satisfies the registered CAIT-style arrival decision rule.
+- `endogenous_net_growth_interval`: lower/upper interval for net endogenous growth after losses and resource/risk charges.
+- `external_injection_share`: share of reported production attributable to logged external injection.
+- `unresolved_attribution_share`: share of reported production that remains unresolved.
+- `transfer_coverage`: fraction of target coordinates covered by accepted transfer evidence.
+- `queue_margin`: lower service capacity minus arrival demand.
+- `safety_control_status`: whether service and safety-control constraints pass, fail, or remain conditional.
+
+## Minimal Example
+
+```json
+{
+  "record_type": "arrival_record",
+  "arrival_id": "arr_demo_001",
+  "target_profile_id": "synthetic_target_profile",
+  "final_decision": "pass",
+  "mandatory_subcertificates_status": "accepted",
+  "mandatory_subcertificate_ids": [
+    "cert_window_balance_demo",
+    "cert_transfer_demo",
+    "cert_evaluation_demo",
+    "cert_controller_demo"
+  ],
+  "endogenous_net_growth_interval": {
+    "lower": 1.25,
+    "upper": 2.0,
+    "unit": "capability_tokens_per_window",
+    "confidence": 0.95
+  },
+  "queue_margin": {
+    "lower": 0.4,
+    "upper": 1.1,
+    "unit": "verified_tokens_per_day"
+  },
+  "external_injection_share": 0.1,
+  "unresolved_attribution_share": 0.0,
+  "transfer_coverage": 1.0,
+  "acceptance_thresholds": {
+    "max_external_injection_share": 0.2,
+    "max_unresolved_attribution_share": 0.05,
+    "min_transfer_coverage": 0.9,
+    "max_residual_risk_upper": 0.1
+  },
+  "target_coordinate_statuses": [
+    {
+      "coordinate": "synthetic_code_repair",
+      "status": "accepted",
+      "within_boundary": true
+    }
+  ],
+  "target_defeaters": [],
+  "safety_control_status": "pass",
+  "transfer_status": "pass",
+  "evaluation_status": "pass",
+  "window_balance_status": "pass",
+  "operational_metrics": {
+    "external_injection_share": 0.1,
+    "unresolved_attribution_share": 0.0,
+    "transfer_coverage": 1.0,
+    "audit_freshness": "pass",
+    "residual_risk": {
+      "lower": 0.0,
+      "upper": 0.05,
+      "unit": "risk_score"
+    }
+  }
+}
+```
+
+All examples in this repository are synthetic and illustrative.
+
+## Schema List
+
+Schemas are in `schemas/cait/`.
+
+- `schema_index.json`
+- `semantic_rules.json`
+- `cait.schema.json`
+- `common.schema.json`
+- `registry_record.schema.json`
+- `certificate_record.schema.json`
+- `domain_witness.schema.json`
+- `token_record.schema.json`
+- `operator_bundle_record.schema.json`
+- `defeater_record.schema.json`
+- `evidence_budget_ledger.schema.json`
+- `assurance_case.schema.json`
+- `transfer_certificate.schema.json`
+- `evaluation_certificate.schema.json`
+- `controller_certificate.schema.json`
+- `window_balance_certificate.schema.json`
+- `arrival_record.schema.json`
+
+## Validation Semantics
+
+JSON Schema validates record structure. The Python validator adds lightweight semantic checks:
+
+- every interval must satisfy `lower <= upper`;
+- passing arrival records require `endogenous_net_growth_interval.lower > 0`;
+- passing arrival records require `queue_margin.lower > 0`;
+- passing arrival records cannot contain unresolved high or blocking target defeaters;
+- passing arrival records must have accepted mandatory subcertificates;
+- passing arrival records must list at least one mandatory subcertificate ID;
+- passing arrival records must have pass status for safety-control, transfer, evaluation, and window-balance subcertificates;
+- passing arrival records must keep `external_injection_share` at or below the registered threshold;
+- passing arrival records must keep `unresolved_attribution_share` at or below the registered threshold;
+- passing arrival records must meet or exceed the registered `transfer_coverage` threshold;
+- passing arrival records must have `operational_metrics.audit_freshness = "pass"`;
+- passing arrival records must keep `operational_metrics.residual_risk.upper` at or below the registered threshold;
+- top-level attribution/coverage shares must match the corresponding `operational_metrics` values;
+- lifecycle statuses other than `accepted` cannot claim `positive_capital_effect = "full"`;
+- evidence mode strengthening must include an explicit witness;
+- a positive claim that requires a domain witness fails if the witness is missing or invalid;
+- target coordinates outside the transfer/evaluation boundary must be `abstained_or_uncertified`.
+
+These checks are intentionally limited. They are meant to catch obvious schema-level misuse, not to establish scientific truth.
+
+## Local-Only Behavior
+
+The validator reads local files and local schemas. It does not send data anywhere, call external services, download runtime resources, or collect telemetry.
+
+## Citation
+
+If you use this repository, cite the related manuscript:
+
+Takahashi, K. (2026). *Certified Autocatalytic Intelligence Theory: Net-Growth Certificate Algebra for Verified Capability Capital*. Zenodo. https://doi.org/10.5281/zenodo.20061296
+
+## License
+
+Apache License 2.0. See `LICENSE`.